refactor(design-docs): dissolve product/ into server/ — server domain-model & write-path records (RIG-2577 T8) - #823
Closed
rigel-mintaka wants to merge 1 commit into
Conversation
…-model & write-path records (RIG-2577 T8) Move the server-side domain-model / write-path records out of the dissolving product/ bucket into the ruled top-level server/ bucket (RIG-2577 §Approach 2). 18 records: the frozen roster's 11 server-block records plus the 7 post-freeze drift records Matt ratified into server/ on 2026-08-31 (compass-forge-agent-notification, compass-forge-app-credentials, compass-forge-board-webhook-ingestion, compass-linear-return-path-indirection-amendment, compass-linear-webhook-mount-amendment, compass-handle-addressing-cutover, compass-linear-agent-responder). server/ is already a governed root; records stay governed across the move, no Status normalization needed. Same-PR link integrity (RIG-2577 Global Constraints): - DECISIONS.md Record cells re-pointed product/<r>/ -> server/<r>/ (284 rows unchanged; pure relocation, no decision changed). - Cross-bucket body links updated: 3 agent/ records' outbound links to now-server records re-pointed ../../product/ -> ../../server/; 2 outbound links from compass-zulip-threading-model to ui-bound records re-pointed to their current ../../product/ location. - External citation sweep: proto source (forge.proto) + its generated pb.go/pb.ts comments, Go forge/store/linearagent/server code comments, and inter-record prose. Verified: design-ledger-gate OK (284 rows, 120 headers); eng-docs gather 73/73; 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>
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
1 participant
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 server-side domain-model / write-path records out of the dissolving
product/ bucket into the ruled top-level server/ bucket (RIG-2577 §Approach 2). 18
records: the frozen roster's 11 server-block records plus the 7 post-freeze drift
records Matt ratified into server/ on 2026-08-31 (compass-forge-agent-notification,
compass-forge-app-credentials, compass-forge-board-webhook-ingestion,
compass-linear-return-path-indirection-amendment, compass-linear-webhook-mount-amendment,
compass-handle-addressing-cutover, compass-linear-agent-responder).
server/ is already a governed root; records stay governed across the move, no Status
normalization needed.
Same-PR link integrity (RIG-2577 Global Constraints):
unchanged; pure relocation, no decision changed).
now-server records re-pointed ../../product/ -> ../../server/; 2 outbound links
from compass-zulip-threading-model to ui-bound records re-pointed to their
current ../../product/ location.
comments, Go forge/store/linearagent/server code comments, and inter-record prose.
Verified: design-ledger-gate OK (284 rows, 120 headers); eng-docs gather 73/73;
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