agentleFS
aaronreneaaronrene/knowtation/.cursor/rules/governance-sync.mdc

knowtation / rules

Cursor rule1 starsChanged 2 months agoMITView on GitHub

Mandatory governance sync before session end (SD-17)

  • Commits and pushes

The file

We split this governance-sync.mdc into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before closing any work session in {{repo.name}}, update both governance docs together:

    line 8
  2. Very specific:

    After writing both docs, print the CURRENT NEXT block via ok next (or equivalent Read from disk) under ## CURRENT NEXT — paste this in the …

    line 23
  3. Very specific:

    Every NEXT block and paste-ready prompt must include Model: per policy/model-labels.yaml.

    line 45

≈ “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
governance-sync.mdc
---
description: Mandatory governance sync before session end (SD-17)
alwaysApply: true
---

# Governance sync — hard prerequisite (SD-17)

Before closing any work session in **{{repo.name}}**, update both governance docs together:

1. `{{docs.roadmap_path}}` — phase/build status reflects reality
2. `{{docs.handover_path}}` — NEXT SESSION block regenerated from those docs (docs-first; never from memory)

## Closing commit rule

The session-ending commit on the current feature branch **must bundle**:

- code and/or tests touched this session
- `{{docs.roadmap_path}}`
- `{{docs.handover_path}}`

A commit that omits either governance doc is **incomplete**.

After writing both docs, print the CURRENT NEXT block via `ok next` (or equivalent Read
from disk) under `## CURRENT NEXT — paste this` in the final reply.

## Tier 1 — do without asking

| Action | Authority |
| --- | --- |
| Muse or Git commit on feature branch | SD-1, SD-17 |
| `git push` to feature branch | SD-17 |
| Open PR from feature branch | SD-17 |
| Run test suite | always |
| Regenerate handover from updated roadmap | SD-17 |

## Tier 3 — always stop

- Merge to `{{vcs.git.main_branch}}` (Muse or GitHub)
- `muse push {{vcs.muse.staging_remote}}` (when regime includes Muse staging)
- Live capability / posture gate flips
- Real payments, secrets, data deletion

## Model label

Every NEXT block and paste-ready prompt **must** include **`Model:`** per `policy/model-labels.yaml`.

## VCS regime

This repo: **`{{vcs.regime}}`** (canonical: **`{{vcs.canonical}}`**). See `policy/tiers.yaml` for regime-specific mirror rules.

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.