The project-scale version of the sovereign-starter two-file method — same shape, wider canon.
Drop into any host repo's /canon or /governance directory. Point the AI at CANON.md as its first read. That is the install.
The single first read. Part I — Terms (bilateral agreement, 9 articles). Part II — Narrowing (boot contract, inherited compliance, blueprint, reference framework, project-specific rules and standing preferences).
The register. Type-O rows record drift; Type-Δ rows record changes to the canon with prior text verbatim, new text verbatim, and reason. The evidence base and the change ledger in one register. This is the file that travels between contexts.
The sovereign-starter kit ships two files as the entry point for practitioners starting from scratch. This plug-in is that same method at project scale.
NARROWING.md → plug-in CANON.mdOBSERVATIONS.md → plug-in OBSERVATIONS.mdSame role in the loop. The plug-in CANON.md is wider (agreement articles + inherited compliance + blueprint + reference framework + project rules), and the plug-in OBSERVATIONS.md adds Type-Δ rows for change tracking alongside Type-O drift rows. Adopters can start with the two-file kit and grow into this shape, or copy this plug-in wholesale and edit.
# from your host repo's root
mkdir -p canon
curl -sL https://raw.githubusercontent.com/EVEglyphDesign/canon/main/CANON.md > canon/CANON.md
curl -sL https://raw.githubusercontent.com/EVEglyphDesign/canon/main/OBSERVATIONS.md > canon/OBSERVATIONS.md
git add canon && git commit -m "add canon plug-in v1.0"
Or /governance if that is what your repo calls its policy directory. Or any other name — the plug-in is layout-agnostic.
Then in the project's AI instructions:
Read canon/CANON.md first, then recent Type-Δ rows
in canon/OBSERVATIONS.md, before any action.
Any user can copy the two files into a host repository and edit them freely. The reference version in this repository is EVEglyphDesign's own operating canon — every project-specific rule in §5 of CANON.md is EVEglyphDesign's; adopters replace §5 with their own.
Part I (Terms) and §§1–2 of Part II (boot contract, inherited compliance) are the shared shape. Sections §3 (blueprint) and §4 (reference framework) are placeholders adopters fill from their own project.
The licence is MIT. The reference-version copyright notice may be removed from copies used inside private repositories.
The repository is the record: github.com/EVEglyphDesign/canon. If this page and the repository disagree, the repository wins.
The compressed boot contract in §1 of CANON.md is drawn from eve-glyph-boot-contract; if the two disagree, that source wins.