80  Canon Audit

81 Canon Audit

The canon audit page is intentionally strict. AI-assisted pre-audit can prepare evidence, but the project cannot claim human canonical signoff until a named human maintainer records it.

81.1 Status

  • Current status: pending-human-maintainer-signoff
  • Policy: Codex can prepare audit records and preflight evidence, but canonical human review requires a named human maintainer decision.

81.2 Required Human Fields

  • reviewer
  • review_date
  • decision
  • scope
  • notes

81.3 Queue

Audit Scope Prepared Evidence Status Blocker
canon.major-50.shadow-review 50 major canon entries data/canon_quality.json shows 50/50 reviewed major-canon shadows. pending A named human maintainer must decide whether these reviewed shadows are canonically accepted.
canon.pocket-300.prompt-use-review 300 pocket canon entries Every reviewed entry has prompt uses and examples. pending Usage-earned promotion needs maintainer acceptance and issue-driven correction path.
canon.first-two-houses.reviewed-tranche Architecture and language/semantics houses data/semantic_promotion.json marks the first two houses fully reviewed. pending Canonical status remains blocked on human review notes.

81.4 Decision Intake

Use the pending decision template and validator when a named maintainer is ready to record a real audit decision:

python3 scripts/check_canon_audit_decision.py validate examples/canon/canon-audit-decision-template.json

The pending template validates structure only. It must not be counted as human signoff until the record is replaced with a human-signed decision that names the reviewer, date, decision, evidence checked, correction outcome, and signoff notes.

Raw data: canon_audit.json

Pending decision template: canon-audit-decision-template.json