refactor(design-docs): dissolve product/ into agent/ — agent behavior & lifecycle records (RIG-2577 T8) - #821
Closed
rigel-mintaka wants to merge 2 commits into
Closed
refactor(design-docs): dissolve product/ into agent/ — agent behavior & lifecycle records (RIG-2577 T8)#821rigel-mintaka wants to merge 2 commits into
rigel-mintaka wants to merge 2 commits into
Conversation
…records (RIG-2577 T8) Move the four process/method records that govern the corpus and the product's engineering posture out of the dissolving product/ bucket into the ruled top-level meta/ bucket (RIG-2577 §Approach 2): - compass-architecture-lineage/ - compass-design-ledger/ - compass-test-strategy/ - compass-tier3-scope-gate/ meta/ is already a governed root (tools/design-ledger-gate GOVERNED_ROOTS), so the records stay governed across the move; no Status normalization is needed (product records already carry gate-grammar headers). Same-PR link integrity (RIG-2577 Global Constraints): - 40 DECISIONS.md Record cells re-pointed product/<r>/ -> meta/<r>/ (row count unchanged at 277; pure relocation, no decision changed). - 2 inbound cross-bucket body links from product/ records re-pointed to the stable ../../meta/compass-architecture-lineage/design.md form. - External citation sweep: gate header/message strings (tools/design-ledger-gate), 2 UI test comment/message strings, and 3 other-bucket record prose citations (infra/runtime, observability, product) re-pointed to meta/. Verified: design-ledger-gate OK (277 rows, 119 headers); eng-docs gather 73/73; UI design-citations + identity tests 14/14; no dangling product/ refs to moved records remain. Ledger-impact: records relocated within governance, no decision changed Co-authored-by: Matt Wilkinson <matt@rigel.build>
… & lifecycle records (RIG-2577 T8) Move the agent-behavior/lifecycle/comms/tools/ask records out of the dissolving product/ bucket into the ruled top-level agent/ bucket (RIG-2577 §Approach 2). 25 records: the frozen roster's 19 agent-block records plus the 6 post-freeze drift records Matt ratified into agent/ on 2026-08-31 (compass-agent-forge-tools, compass-agent-org-mgmt-tools, compass-agent-peer-dm, compass-ask-answer-recovery, compass-manager-role-taxonomy, compass-per-agent-overrides). agent/ is already a governed root; records stay governed across the move, no Status normalization needed. The two former-platform strays (compass-forks-reversal, compass-initial-prompt-removal) already landed in agent/ via the #797 platform drain. Same-PR link integrity (RIG-2577 Global Constraints): - DECISIONS.md Record cells re-pointed product/<r>/ -> agent/<r>/ (284 rows unchanged; pure relocation, no decision changed). - 3 outbound cross-bucket body links (to server-bound records still in product/) re-pointed to their current ../../product/<r>/design.md location. - External citation sweep: proto sources (agent.proto, agent_gateway.proto) and their generated pb.go/pb.ts comments, Go runner/store comments, compass-agent TS comments, and 3 other-bucket record prose citations re-pointed to agent/. Verified: design-ledger-gate OK (284 rows, 120 headers); eng-docs gather 73/73; UI design-citations 2/2; no dangling product/ refs to moved records; proto swept so buf regen introduces no drift. Ledger-impact: records relocated within governance, no decision changed Co-authored-by: Matt Wilkinson <matt@rigel.build>
mattwilkinsonn
approved these changes
Sep 1, 2026
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR is part of a stack containing 4 PRs:
mainMove the agent-behavior/lifecycle/comms/tools/ask records out of the dissolving
product/ bucket into the ruled top-level agent/ bucket (RIG-2577 §Approach 2). 25
records: the frozen roster's 19 agent-block records plus the 6 post-freeze drift
records Matt ratified into agent/ on 2026-08-31 (compass-agent-forge-tools,
compass-agent-org-mgmt-tools, compass-agent-peer-dm, compass-ask-answer-recovery,
compass-manager-role-taxonomy, compass-per-agent-overrides).
agent/ is already a governed root; records stay governed across the move, no Status
normalization needed. The two former-platform strays (compass-forks-reversal,
compass-initial-prompt-removal) already landed in agent/ via the #797 platform drain.
Same-PR link integrity (RIG-2577 Global Constraints):
unchanged; pure relocation, no decision changed).
re-pointed to their current ../../product//design.md location.
their generated pb.go/pb.ts comments, Go runner/store comments, compass-agent
TS comments, and 3 other-bucket record prose citations re-pointed to agent/.
Verified: design-ledger-gate OK (284 rows, 120 headers); eng-docs gather 73/73;
UI design-citations 2/2; no dangling product/ refs to moved records; proto swept so
buf regen introduces no drift.
Ledger-impact: records relocated within governance, no decision changed
Co-authored-by: Matt Wilkinson matt@rigel.build