refactor(hygiene 4/5): Suite 6 → L9 rebrand + rewrite CANONICAL_LAW#9
Conversation
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
|
Remediation pass (9faddfa): Verified: this PR's
Confirmed no PR #5 collision remains (PR #5's diff no longer touches |
- Replaced all 'Suite 6' / 'Cursor Governance Suite 6' references with 'L9 Governance' - Updated session YAML headers to L9 Governance Runtime v10.0.0 - Removed component_id numbering (Suite 6 artifact) - Updated data_sources from GlobalCommands to Cursor-Governance - 47 files updated across all layers
…nance - Removed all Suite 6 ceremony references - Added IDE Adapter Model section (IDE-agnostic runtime) - Replaced GlobalCommands terminology with governance root - Documented Graphiti-native memory layer as primary - Listed deprecated/archived components explicitly - Added intelligence signal mining section (permanent corpus) - Added governance enforcement flags table - Removed Dropbox legacy fallback reference
…n HTML/JSON - Removed all __pycache__/ directories from git tracking - Added __pycache__/ and *.pyc to .gitignore - Fixed Suite 6 references in governance-dashboard.html and rule-registry.json
Carries the ORG_INVARIANTS registration that PR #5 originally placed in the old CANONICAL_LAW.md table, re-expressed in this PR's rewritten table format. This resolves the CANONICAL_LAW.md collision between the hygiene pack and PR #5 so the two land without conflict (PR #5 no longer touches this file). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Rr6wpk9eehnJdRmh5BwWGG
…rational-oversight.py This PR already did a real (non-cosmetic) rewrite of CANONICAL_LAW.md for post-Suite-6/Graphiti-native governance, but README.md only got a string swap (Suite 6 -> L9 Governance) while keeping the pre-migration 2025-01-27 directory tree, @.GlobalCommands/ access paths, and "GlobalCommands Directory" framing. Rewrote it to match CANONICAL_LAW.md's corrected model and the actual current top-level structure of the repo. Also fixed two dangling references inside operational-oversight.py (touched by this PR's rebrand pass, but not by its content) that TODO.md flags as broken-if-invoked: - _check_workflow_readiness() checked startup/REASONING_STACK.yaml (deleted); now checks skills/l9-structured-reasoning/SKILL.md per TODO.md's supersession table. - _run_verification() called ops/scripts/verify-startup-files.sh (archived in the sibling hygiene-3 PR, and itself broken -- checks deleted startup/* paths); now calls verify-setup-alignment.sh, the current active alignment-verification script. No behavior change to the governance-monitor import guard, the learning processor SSOT-path resolution (already correct), or any other file. Co-authored-by: Cursor <cursoragent@cursor.com>
…tion Root-caused why main's CANONICAL_LAW.md kept reverting to the stale Dropbox-SSOT content this PR fixes: resolve_governance_paths.sh fell back to $HOME/Dropbox/Cursor Governance/GlobalCommands whenever the local ~/.cursor-governance clone was momentarily absent/incomplete, and backup_to_github.sh then copied that Dropbox copy over the repo's CANONICAL_LAW.md and committed+pushed the result straight to main on every sessionEnd -- bypassing PR review entirely. This is exactly what happened in f572fb6 on main just now, and is why this branch now conflicts with main on CANONICAL_LAW.md. Per explicit direction: Dropbox is no longer the SSOT for this repo. The GitHub clone at $HOME/.cursor-governance is cloned once and kept fast-forward-synced by governance_sync.sh (already GitHub-only, unaffected by this bug). resolve_governance_paths.sh now resolves *only* $HOME/.cursor-governance; if it's missing, the fix is to (re-)clone it, not fall back to Dropbox. backup_to_github.sh's now-meaningless Dropbox->repo CANONICAL_LAW.md copy step is removed -- the file already lives in the repo and needs no external source. session_init.sh and tenx_status.sh already check ~/.cursor-governance before any Dropbox path, so they were not implicated in this bug and are left as-is; both are otherwise pre-Graphiti learning-system scripts, flagged separately in TODO.md. Co-authored-by: Cursor <cursoragent@cursor.com>
9faddfa to
f97c554
Compare
|
Critical finding + fix (f97c554), rebased onto main: This PR went Per explicit direction from the repo owner: Dropbox is no longer the SSOT for this repo. The GitHub clone at Rebased this branch onto current |
|
2 participants
Part 4 of 5 — scoped split of the Cursor-Governance Hygiene Commit Pack.
What
CANONICAL_LAW.mdfor post-Suite-6, Graphiti-native governance.__pycache__from tracking and adds the ignore.Collision resolution — PR #5 (
CANONICAL_LAW.md)This PR owns
CANONICAL_LAW.md. PR #5 (ORG_INVARIANTS canonical) was amended to no longer touch this file, and its ORG_INVARIANTS registration is carried here as a row in the rewritten SSOT table (final commit). So PR #4-hygiene and PR #5 no longer collide and can merge in any order.Honest note
A few residual "Suite 6" strings remain (e.g. intentional "post-Suite-6" history in
CANONICAL_LAW.md, andTODO.md) — the plan's "0 references" target is not literally met; the remaining ones are historical/contextual. Flag if you want them scrubbed too.Split context
1 of 5 independent, disjoint PRs — any merge order. Applies cleanly on
main(git amverified).🤖 Generated with Claude Code
https://claude.ai/code/session_01Rr6wpk9eehnJdRmh5BwWGG
Generated by Claude Code