agentleFS
Sign inStart free
sagarithmsagarithm/sagarithm-kit/.cursor/rules/delivery-shipping-and-launch.mdc

sagarithm-kit / rules

Cursor rule17 starsChanged 12 days agoApache-2.0View on GitHub

"Shipping is not just pushing a git tag; it is an irrevocable contract with users and downstream dependencies. A release must carry empirical proof of correctness." Releasing software without systematic verification leads to registry rollback panics, broken client lockfiles, and reputational damage. This skill ensures that every release candidate passes through strict pre-flight gates before touching production or public registries. Every production release candidate must pass all four gates sequentially:

The file

We split this delivery-shipping-and-launch.mdc into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every production release candidate must pass all four gates sequentially:

    line 20
  2. Very specific:

    All 5 vectors must return ✅ PASS:

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
delivery-shipping-and-launch.mdc
<!-- SAGARITHM:START - DO NOT EDIT DIRECTLY -->
---
description: "Governs production deployments, releases, and distribution. Enforces formal verification gates, SemVer versioning, changelog synchronization, and multi-platform CI/CD attestation."
globs: ["**/*"]
alwaysApply: false
---

# Production Shipping & Release Governance

# 🚢 Production Shipping & Release Governance

> **"Shipping is not just pushing a git tag; it is an irrevocable contract with users and downstream dependencies. A release must carry empirical proof of correctness."**

Releasing software without systematic verification leads to registry rollback panics, broken client lockfiles, and reputational damage. This skill ensures that every release candidate passes through strict pre-flight gates before touching production or public registries.

---

## 🔒 The 4 Pre-Release Verification Gates

Every production release candidate must pass all four gates sequentially:

1. **Gate 1: Verification Gate Attestation**:
   - Execute `sagarithm verify` in strict mode.
   - All 5 vectors must return `✅ PASS`:
     - `STATIC`: Clean compilation and zero lint errors.
     - `SECURITY`: 0 issues detected, Shannon entropy scan clean.
     - `ARCHITECTURE`: Dependency graph verified acyclic, zero directory anti-patterns.
     - `BEHAVIORAL`: Automated test suite passed with 100% green exit code.
     - `DOCUMENTATION`: Project topology manifest (`sagarithm.manifest.json`) synchronized.
2. **Gate 2: Strict SemVer Evaluation**:
   - **Patch (`x.y.Z`)**: Backward-compatible bug fixes or packaging updates.
   - **Minor (`x.Y.z`)**: Backward-compatible new features, skills, or CLI commands.
   - **Major (`X.y.z`)**: Any breaking change to public APIs, configuration schemas, or CLI behavior.
3. **Gate 3: Changelog Synchronization**:
   - `CHANGELOG.md` updated under Keep a Changelog standards.
   - Changes categorized into `Added`, `Changed`, `Deprecated`, `Removed`, `Fixed`, or `Security`.
4. **Gate 4: Clean Git Tree & Tagging**:
   - Working tree strictly clean (`git status` returns nothing to commit).
   - Annotated signed tag created: `git tag -a vX.Y.Z -m "Release vX.Y.Z - <summary>"`.

---

## 🛑 Anti-Rationalization Matrix

| Agent Excuse / Shortcut | Architectural Reality | Mandatory Action |
|---|---|---|
| *"Tests passed locally yesterday, so we can skip running them."* | Uncommitted changes or environment drift frequently break builds silently. | Run full test and verification suite immediately prior to release tagging. |
| *"It's just a tiny internal fix; we can overwrite the existing version."* | Registry versions on npm, crates.io, and PyPI are immutable. Overwrites cause severe caching collisions. | Always bump the patch version strictly according to SemVer. |
| *"We can update the CHANGELOG after pushing the release."* | Post-release changelog edits get forgotten, leaving users with mystery versions. | Changelog updates must be committed in the exact release commit. |
| *"CI failed on only 1 OS, but it passed on Windows so it's probably fine."* | Multi-OS failures indicate hidden path separator or runtime incompatibilities. | Release is blocked until all CI matrix runners (Ubuntu, macOS, Windows) are 100% green. |
<!-- SAGARITHM:END -->

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free