Read these first:
- docs/ARCHITECTURAL-PRINCIPLES.md for ownership and layering rules
- docs/ARCHITECTURE.md for the current runtime map
- docs/PRODUCT-VALIDATION-OBJECTIVES.md for user-frustration goals and proof direction
- docs/TESTING.md for validation policy
- docs/REVIEW-RULES.md for cross-cutting review heuristics
- docs/TERMINAL-DEVELOPMENT-GUIDE.md only when touching terminal or browser-lab work
- docs/UPSTREAM-DIVERGENCE.md when reviewing upstream parity or porting changes
- PRODUCT.md for product context only
- .impeccable.md for design context only
Precedence:
- principles are normative
- architecture describes the current system
- product validation objectives define user pain and proof intent
- testing defines validation expectations
- terminal guide is a runbook, not a second architecture doc
- review rules record reusable review lessons
Keep policy in the owning doc. If behavior changes, update the owner instead of restating the rule here.