docs: add architecture map rule (module ownership + life of a run)#816
Merged
Conversation
Path-scoped orientation for anyone (human or agent) editing src/: the exact call flow of a test run — including the subshell-payload inversion that explains how state crosses process boundaries — a module-ownership table, and the cross-cutting invariants (Bash 3.0 floor, return-slot pattern, fork budget, pinned binaries, snapshot width) with pointers to the rules that enforce them.
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
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.
🤔 Background
The rules cover style, TDD, testing and (recently) the fork budget, but nothing orients a contributor or agent in
src/itself — this session repeatedly re-derived the same call flow from scratch.💡 Changes
.claude/rules/architecture-map.md: the life of./bashunit tests/(entry → discovery → per-test subshell → encoded payload → aggregation → render), a module-ownership table, and the cross-cutting invariants with pointers to the rules enforcing them.src/**or the entrypoint.