Project Canon
ActiveCompact architectural laws and product invariants for coding agents. Code remembers where, Canon remembers why.
Every fresh agent session rebuilds its picture of your system from code alone, and code cannot say why the system is shaped this way. The cap that is a product promise, the gateway rule that ended an outage, the decision that was argued for a week and settled: none of it survives compilation, so each session re-derives what it can and guesses the rest.
Project Canon gives repository-scoped coding agents a small, durable record of the rules that must survive implementation churn:
Canon explains why the system is shaped this way and what must remain true. Code, schemas, package manifests, build graphs, and generated reports explain where the implementation currently lives.
Canon is not a manually synchronized mirror of the repository. File moves, renames, helper extraction, test refactors, and new instances of an established pattern should normally produce Canon impact: none.