The 5th Ledger

adopt-fifth-ledger

Establish a target-routed Fifth Ledger governance profile by mapping existing authority, canonical sources, evidence requirements, user-facing surfaces, lifecycle records, protected invariants, and review expectations. Use when adopting The 5th Ledger for a repository or non-Git artifact, repairing a missing or stale profile, or determining whether existing governance can be reused without creating shadow authority.

close-governance-decision

Reconcile an explicitly decided project proposal or governance transition across decision records, canonical sources, agent guidance, private continuity, implementation, validation, documentation, deployment, and release claims. Use after a human approves, rejects, narrows, supersedes, implements, publishes, promotes, or releases a governed decision; do not use to invent evidence or perform unauthorised work.

draft-governed-proposal

Draft a bounded, evidence-led, review-only project proposal with explicit authority, source precedence, five-ledger impact, risk, validation, containment, review findings, unresolved disagreement, and next human decision. Use when a durable proposal, amendment, architecture decision, migration direction, or promotion request is needed; do not use to imply implementation, publication, deployment, or release.

establish-governance-boundary

Classify project work by requested outcome, authority, risk, target identity, canonical sources, evidence needs, and excluded actions before analysis or mutation. Use when a task could change files, repository state, external systems, public material, deployment or release state, or when the safe next action is unclear.

harmonize-project-content

Review project-controlled user-facing content for calm plain language, correct surface placement, source-traceable claims, protected safety and degraded-state truth, and consistency with canonical implementation and lifecycle evidence. Use for explicit harmonisation, humanisation, normalization, content coherence, documentation alignment, or user-facing closeout across README, docs, websites, releases, support material, setup flows, translations, reports, or UI copy.

review-project-coherence

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.

review-release-evidence

Assess deployment health, validation coverage, observation or soak completion, documentation, rollback, approval, and release readiness from exact identity-bound project evidence. Use when asked whether a build, package, service, migration, deployment, promotion, or release is ready, healthy, or blocked. This workflow is read-only and never authorises deployment, publication, promotion, tagging, or release.

run-independent-review

Coordinate Canon, Sentinel, Challenger, and Steward review findings over one bounded project artifact, preserve initial findings and substantive disagreement, and label whether reviews were genuinely independent or only role-separated. Use for governance-sensitive proposals, cross-surface changes, release decisions, or any request requiring multiple specialist perspectives without conflating review with implementation authority.