Skip to content

Audits

Audits

Cross-cutting reviews of existing content against newly-ratified canon. Triggered when D-level decisions or major W-level canon files retroactively affect already-written lore.

Purpose

Canonical decisions can introduce conflicts with content authored prior to the decision. Audits surface those conflicts and document the triage — which conflicts get fixed, which trigger retcons, and which are reconciled by note rather than edit.

This page lists conducted audits in chronological order. Each audit is a single Markdown page under wiki/src/content/docs/audits/.

Lifecycle

StatusMeaning
draftnarrative-designer has authored, CEO has triaged. MRs pending.
reviewedCEO has signed off on triage decisions. MRs in flight.
canonAll MRs merged. system-reviewer final sweep clean. Trail closed.

Format

Every audit carries:

  1. Trigger — which canonical decision(s) caused this audit.
  2. Conflicts found — table from system-reviewer raw report (file + location + conflict + severity).
  3. Triage decisions — per-conflict outcome: edit / retcon / OK as-is.
  4. Resulting actions — checklist of MRs, retcon /decide flows, file notes.
  5. Open questions for CEO — anything triage couldn’t close.
  6. Sign-off — CEO + system-reviewer ticks.

Where raw reports live

Raw conflict lists generated by system-reviewer live in ops/audits/YYYY-MM-DD-raw.md (local, not committed). Digests on this page are the durable artifact.

Conducted audits

DateAuditStatus
2026-05-20D-012 + D-013 lore auditcanon
2026-05-20Naming discipline drift audit — Phase C input specreviewed