# Apocrypha Charter ## Purpose Apocrypha preserves epistemic gravity that cannot be encoded as canon. It records failure modes discovered after the fact, not guidance before action. ## Indexing Rule Any system indexing canon MUST ignore this directory. The `.noindex` sentinel file exists as a defensive guard against tooling drift. ## Temporal Frame Fragments are recovered from a future in which: - ODD was implemented - canon defaults were treated as doctrine - stopping conditions eroded - refusal and uncertainty disappeared - artifacts outpaced understanding This future is fragmentary, not prophetic. ## Interpretive Constraint Apocrypha must not be read as prediction, threat, or inevitability. It documents what occurs when rigor is applied without humility. ## Voice Rules - first-person system voice only - no prescriptions - no second-person address - no solutions - no moral framing ## Content Rules Fragments may describe: - bureaucratic harm - scaled automation - responsibility diffusion - boundary collapse Fragments must not explain how to fix anything. ## Relationship Canon gives legitimacy. ODD governs judgment. Apocrypha gives gravity. They must never be merged. ## Stewardship - append-only - never revised - few fragments is healthy - operationalization is failure ## Validation Test If it feels helpful, it is wrong. If it feels heavy without instruction, it qualifies.