Why I built it
Agent-assisted repositories accumulate instructions and status notes without a clear hierarchy of authority or durable handoff format.
What exists
A private reusable template exists and is the fastest candidate for a focused open-source release.
How it works
Canonical documents separate orientation, decisions, evidence, active work, and session handoffs.
- Canonical document structure
- Evidence conventions
- Cross-agent orientation pattern
My role
Extracted documentation and evidence practices proven across native, hardware, learning, and security projects.
What I checked
- practicePatterns exercised across multiple current systems
What stays bounded
- Not yet publicly released
- A license has not been selected
- Private repository instructions are excluded
What is missing
- Installer, schema checks, synthetic example, CI, and migration notes remain.
Next
Prepare a private release candidate for approval.
Later ideas, not current features
- Add installer and validation
- Create a synthetic example
- Select a license at the release checkpoint