Operate / Release owners

Release assurance and runbooks

Execute the complete gate, evidence, attestation, deployment, smoke, and rollback sequence.

release provenancerelease freeze, governance controls, attestation, and archiveComplete production checklist

Implementation rail · release freeze, governance controls, attestation, and archive

Exact execution and operator checks

  1. 01

    Operator check

    Bind release dimensions

    Bind repository commit and tree, tag, package identities, candidate artifact digests, deployment target, smoke plan, rollback owner, and attestation custodian as separate evidence dimensions.

    Substantive records: /reference/releases · /releases/v124.0.0

    Expected: No release dimension is inferred from another.

  2. 02

    Exact mechanic

    Run test:release-freeze

    pnpm test:release-freeze
    Mechanic
    pnpm test:release-freeze
    Authentication and account boundary
    Authorized local repository checkout; the command proves only the checked repository boundary.
    Exact source
    package.json · SHA-256 132f99232dfaf26f7186b73752938d1377042808f42d60d374fe7b2e57c7646b

    Expected: The coordinated repository release gate passes.

  3. 03

    Exact mechanic

    Run release:attest

    pnpm release:attest
    Mechanic
    pnpm release:attest
    Authentication and account boundary
    Authorized local repository checkout; the command proves only the checked repository boundary.
    Exact source
    package.json · SHA-256 132f99232dfaf26f7186b73752938d1377042808f42d60d374fe7b2e57c7646b

    Expected: An authorized dated attestation is emitted after all gates pass.

  4. 04

    Operator check

    Qualify publication

    Verify the emitted attestation, publish the exact package and deployment, execute dated smoke checks, and retain rollback proof. Stop on commit, tree, digest, signature, deployment, or smoke mismatch.

    Substantive records: /trust/evidence · /trust/governance

    Expected: Every published claim has its own exact evidence.

Complete operating anatomy

Every boundary required to ship.

Solved outcome
Every release claim maps to a distinct repository, tag, package, deployment, smoke, or attestation evidence dimension.
Prerequisites
Hold repository commit and tree, tag, package identities, gate commands, candidate digests, release-key custody, deployment target, smoke matrix, publication authority, and rollback owner.
Exact primitive
release provenance
Governing law
Release assurance and runbooks is governed by release-attestation-create: The command emits a dated attestation only from its observed inputs. release-attestation-verify: A passing command verifies every bound attestation field for the supplied artifact. evidence-register: Declared evidence remains traceable to a stable registered record.
Source-of-truth order
Receiz law → sealed artifact truth → deterministic proof object state → verified durable local or register truth → authenticated snapshot → server distribution, synchronization, indexing, and publication → database, session, observability, and interface projections.
Expected artifact, receipt, or state
Gate output plus distinct evidence records; a passing gate does not manufacture deployment, smoke, publication, or signature status.
Inspection
Inspect the release archive record and each independent evidence dimension. Inspection exposes structure and receipt fields; inspection never establishes verification.
Independent verification
Independent verification for release-assurance: verify the emitted dated attestation against its exact commit, tree, payload digest, signature, and registered public material. This establishes only the release provenance boundary named by the bound sources; The implementation rail remains beneath proof authority: release freeze, governance controls, attestation, and archive.
Offline behavior
Local gates and dated committed attestations verify offline. Live deployment state requires a dated external observation.
Identity and account boundary
Public Record Moment, Seal File, Verify, Export, and public proof reading are account-free. Identity is optional and adds continuity, custody, recovery, and governed private controls after proof admission.
Security boundary
Attestation signing requires authorized custody; verification uses registered public material.
Conformance command
pnpm test:release-freeze
Deployment checks
Qualify repository gates, package contents, signatures, attestation, publication, deployment, dated smoke, rollback, and archive as independent release evidence dimensions.
Production checklist
Run full freeze; verify package contents; attest under authorized custody; verify attestation; publish exact artifacts; observe deployment; execute smoke; test rollback; archive every independent result.
Rollback and containment
Containment for release-assurance: Only the gate claim is established. Collect the absent evidence before claiming release completion. The publication is rejected. Withdraw the mismatch and publish the exact attested package. Rollback safety is unproven. Select the last independently verified release and observe it after rollback. Preserve every stronger held artifact and admitted state while the named boundary is corrected.

Fail closed

Mutation and failure matrix

F1

A gate passes but package, deployment, or smoke evidence is absent.

Effect
Only the gate claim is established.
Retry
Do not infer the missing dimension.
Recovery
Collect the absent evidence before claiming release completion.
F2

Published package bytes differ from the attested digest.

Effect
The publication is rejected.
Retry
Do not re-sign unknown bytes.
Recovery
Withdraw the mismatch and publish the exact attested package.
F3

Rollback target lacks a verified attestation or smoke record.

Effect
Rollback safety is unproven.
Retry
Do not improvise a target.
Recovery
Select the last independently verified release and observe it after rollback.

Exact authority

Claim-to-source bindings

  1. The command emits a dated attestation only from its observed inputs.

    scripts/create_release_attestation.tsrelease-evidence-emitter · SHA-256 918a5c328799194fe44095100ba30c54eede44b956b7dcfe0d03ba5347a397db
  2. A passing command verifies every bound attestation field for the supplied artifact.

    scripts/verify_release_attestation.tssigned-evidence-verifier · SHA-256 f04e07009107c30a2c41a2f237ed08a581b4773caef3771d8167b762e23d6606
  3. Declared evidence remains traceable to a stable registered record.

    docs/governance/evidence-register.v1.jsonevidence-register · SHA-256 d08b41fe380fa07035f85d05520ca260d38e64043e90596d58501e79a8423354