workspace-authority.mdc
sha256:a78e7e5a8740e03315f325d19edeb3aa1b306b3337d04abbaa9a9e0f3bbeb7a1
docs: MuseHub-first before ISR #74 — staging solidify NEXT
Human
2 days ago
| 1 | # Workspace authority — multi-root tab is not PRIMARY |
| 2 | |
| 3 | In a multi-root Cursor / IDE workspace, **never** treat a non-`product_order` handover as |
| 4 | product sequencing PRIMARY without running: |
| 5 | |
| 6 | ```bash |
| 7 | ok workspace status |
| 8 | # or |
| 9 | ok workspace check-next |
| 10 | ``` |
| 11 | |
| 12 | The focused editor tab is **not** authority. Prefer basenames |
| 13 | `{REPO_SLUG}-OVERSEER-HANDOVER.md` / `{REPO_SLUG}-ROADMAP.md` so tabs are distinguishable |
| 14 | (§MR.6.5). Bare `OVERSEER-HANDOVER.md` across members is a `board_name_violation` under |
| 15 | `strict_board_names` (doctor warning; check-next still keys on tip freshness only). |
| 16 | |
| 17 | When `workspace:` is configured and this session advanced product_order PRIMARY, multi-repo |
| 18 | SD-17 close-out requires refreshing each `relay: true` member’s product tip |
| 19 | (`role=relay` or `role=product_relay`) until `ok workspace check-next` exits `0`. |
| 20 | Single-repo `ok governance-sync` remains required and does **not** write peer repos. |
File History
1 commit
sha256:a78e7e5a8740e03315f325d19edeb3aa1b306b3337d04abbaa9a9e0f3bbeb7a1
docs: MuseHub-first before ISR #74 — staging solidify NEXT
Human
2 days ago