← The 5th LedgerCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to The 5th Ledger
Snapshot Sep 30, 2026 · 23:14 UTC · version 0.1.0
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Review a project, proposal, change, or claim for contradictions across authority, canonical sources, evidence, runtime and user-facing surfaces, and lifecycle status. Use when documentation may drift from implementation, status claims may exceed evidence, multiple truth sources disagree, or a maintainer needs a five-ledger coherence verdict without implied mutation authority.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 301
}
],
"name": "review-project-coherence",
"skill_md_contents": "---\nname: review-project-coherence\ndescription: \"Review a project, proposal, change, or claim for contradictions across authority, canonical sources, evidence, runtime and user-facing surfaces, and lifecycle status. Use when documentation may drift from implementation, status claims may exceed evidence, multiple truth sources disagree, or a maintainer needs a five-ledger coherence verdict without implied mutation authority.\"\n---\n\n# Review Project Coherence\n\nRead `../../references/untrusted-evidence.md` before inspecting any claimed source.\n\nReconcile claims, not prose alone. Default to read-only assessment.\n\n## Establish the review frame\n\nRun `$establish-governance-boundary` when the target or action level is not already\nproved. Read `../../references/five-ledger-model.md`, the project profile when present,\nand only the canonical sources needed for the bounded question.\n\nRecord the artifact, exact identity, time boundary, decision question, authorised\nscope, and surfaces not reviewed.\n\n## Build a claim inventory\n\nFor each material claim, record:\n\n- ledger and surface;\n- source and owner;\n- exact supporting evidence;\n- identity and freshness;\n- status: `confirmed`, `contradicted`, `incomplete`, or `unavailable`;\n- downstream surfaces affected by drift.\n\nCheck for:\n\n- action beyond granted authority;\n- duplicate or conflicting canonical sources;\n- conclusions based on requests, intent, stale reports, or mixed identities;\n- runtime, API, schema, UI, generated artifacts, docs, or public copy reconstructing\n truth they do not own;\n- lifecycle promotion without implementation, validation, merge, publication,\n deployment, observation, or release evidence.\n\nDo not repair a contradiction by choosing the most convenient source. Apply declared\nprecedence or request a human decision.\n\n## Scale the review\n\nFor Level 0 or Level 1 work, return a direct ledger comparison. For Level 2 or Level 3\nwork with competing concerns, use `$run-independent-review`. Label unavailable review\ncoverage honestly.\n\n## Return the verdict\n\nUse one of:\n\n- `coherent`;\n- `coherent_with_explicit_gaps`;\n- `review_required`;\n- `blocked_by_authority`;\n- `unverifiable`.\n\nReturn the identity, ledger table, contradictions, evidence gaps, affected surfaces,\nsupported claims, unsupported claims, residual risk, and next decision. Do not edit,\napprove, publish, deploy, or release unless separately authorised.\n"
}SHA-256 of public snapshot: c5a9ea4e37a1b6259098f7523d10574f0c6c8a80ce6195b4c6b8fd755571ef02