docs: add architecture and stack-lock policy docs - #45
Merged
Merged
Conversation
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.
Portfolio triage wave 2 (2026-09-21)
Deeper docs pass for the orchestrator:
docs/architecture.md(114 lines): how the orchestrator wraps Constitutional Agent Testbench + Consequence Rail + MandateBound in decide -> act -> prove order, including the data flow between components and the verify-only CI boundary.docs/stack-lock.md(79 lines): whatstack-lock.jsonpins, when to update, and who can update.README.md: one-paragraph cross-link inserted between Design bounds and License pointing at the new docs.No non-docs files modified. No em dashes in user-facing text. Claims describe only what the code actually does.
Validation:
npm test(node --test) before: pass=149, skip=1, fail=0. After: same.