agentleFS
aaronreneaaronrene/knowtation/.cursor/rules/workspace-authority.mdc

knowtation / rules

Cursor rule1 starsChanged 2 months agoMITView on GitHub

In a multi-root Cursor / IDE workspace, never treat a non-product_order handover as product sequencing PRIMARY without running: The focused editor tab is not authority. Prefer basenames {REPO_SLUG}-OVERSEER-HANDOVER.md / {REPO_SLUG}-ROADMAP.md so tabs are distinguishable (§MR.6.5). Bare OVERSEER-HANDOVER.md across members is a board_name_violation under strict_board_names (doctor warning; check-next still keys on tip freshness only). When workspace: is configured and this session advanced product_order PRIMARY, multi-repo SD-17 close-out requires refreshing each relay: true member’s product tip (role=relay or role=product_relay) until ok workspace…

The file

We split this workspace-authority.mdc into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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. Very specific:

    When workspace: is configured and this session advanced product_order PRIMARY, multi-repo SD-17 close-out requires refreshing each relay: …

    line 17

≈ “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
workspace-authority.mdc
# Workspace authority — multi-root tab is not PRIMARY

In a multi-root Cursor / IDE workspace, **never** treat a non-`product_order` handover as
product sequencing PRIMARY without running:

```bash
ok workspace status
# or
ok workspace check-next
```

The focused editor tab is **not** authority. Prefer basenames
`{REPO_SLUG}-OVERSEER-HANDOVER.md` / `{REPO_SLUG}-ROADMAP.md` so tabs are distinguishable
(§MR.6.5). Bare `OVERSEER-HANDOVER.md` across members is a `board_name_violation` under
`strict_board_names` (doctor warning; check-next still keys on tip freshness only).

When `workspace:` is configured and this session advanced product_order PRIMARY, multi-repo
SD-17 close-out requires refreshing each `relay: true` member’s product tip
(`role=relay` or `role=product_relay`) until `ok workspace check-next` exits `0`.
Single-repo `ok governance-sync` remains required and does **not** write peer repos.

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.