Problem
Running charter audit on the charter repo itself returns 0/100 FAIL:
Score: [fail] 0/100
Git Governance Coverage
Commits analyzed: 5
With trailers: 0 (0%)
Blessed Stack Patterns
Total defined: 0
Policy Documentation
Policy files: 0
Missing sections: 4
Similarly, charter doctor warns on the repo's own setup:
- No patterns found in
.charter/patterns/*.json
- No policy markdown files
charter drift also reports nothing to scan because no patterns are defined.
Impact
Charter is the governance CLI. If it doesn't govern itself, it undermines the entire pitch. A potential adopter running charter audit during evaluation would see this as a red flag.
Fix
- Add at minimum 2-3
.charter/patterns/*.json examples to the repo (can be governance-specific: ADF mutation patterns, release trailer patterns)
- Add a
docs/governance-policy.md covering the 4 required sections: Commit Trailers, Change Classification, Exception Path, Escalation & Approval
- Start adding
Governed-By: trailers to release commits and breaking changes
- Bootstrap
.charter/ as a reference implementation that scores ≥80 on its own audit
This also serves as living documentation for adopters — "here's exactly what a well-configured charter repo looks like."
Problem
Running
charter auditon the charter repo itself returns 0/100 FAIL:Similarly,
charter doctorwarns on the repo's own setup:.charter/patterns/*.jsoncharter driftalso reports nothing to scan because no patterns are defined.Impact
Charter is the governance CLI. If it doesn't govern itself, it undermines the entire pitch. A potential adopter running
charter auditduring evaluation would see this as a red flag.Fix
.charter/patterns/*.jsonexamples to the repo (can be governance-specific: ADF mutation patterns, release trailer patterns)docs/governance-policy.mdcovering the 4 required sections: Commit Trailers, Change Classification, Exception Path, Escalation & ApprovalGoverned-By:trailers to release commits and breaking changes.charter/as a reference implementation that scores ≥80 on its own auditThis also serves as living documentation for adopters — "here's exactly what a well-configured charter repo looks like."