REPOSITORY GOVERNANCE
Give people and agents the same map
Treat documentation, durable decisions, and structural checks as part of the workspace rather than an afterthought.
01
Put durable context in durable places
Specs, plans, decisions, audits, research, and reports have distinct lifecycles. Stable identifiers keep their relationships intact as files move or archive.
02
Encode the structural rules
Tags and lint rules turn architectural intent into local feedback, while warning-first adoption lets an established repository ratchet toward the target safely.
03
Check the whole system
The Megamono check joins project classification, dependency boundaries, artifact ownership, and documentation health into one repeatable repository task. Its exit codes are a stable contract, so scripts and agents can act on the outcome instead of parsing output.
npm exec -- nx run megamono:checkExit classifications are stable across every command
0 success or no-op
1 validation or execution failure
2 invalid options
3 preflight refusal
4 unresolved decision, non-interactive