Publish a release ledger that answers what is running
During a rehearsal, responders compare commit hashes from logs because there is no single view of release, artifact, configuration, and schema identity.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Release observability · Audit trails · Runbooks
Estimated field mix
- DevOps70%
- Site reliability30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
A fictional scheduling API is rebuilt separately for test, staging, and production-like local environments. The resulting images differ, release notes list the branch instead of the artifact, and rollback rebuilds old source with new dependencies. Use a local registry simulator and synthetic deployments; no cluster or customer traffic is supplied.
Setup prerequisites
- Artifact digests
- Release states
- Health checks
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- DREL-101 · Bind release identity to an artifact digest
- DREL-102 · Generate release notes from the promoted revision range
- DREL-103 · Promote the built artifact instead of rebuilding it
- DREL-106 · Pause a release when deployment state drifts
- DREL-104 · Gate promotion on database compatibility
- DREL-105 · Canary one cohort with a measurable abort rule
- DREL-108 · Rollback to a known artifact without rebuilding source
- DREL-109 · Resume promotion after the registry response disappears
Acceptance criteria
- Ledger shows desired and observed artifact per environment
- Entries include configuration and schema compatibility identities
- Failed, paused, rolled-back, and superseded releases remain inspectable
Implementation constraints
- The ledger is append-oriented planning and operational data; it is not candidate evidence.
Verification to include
- Trace a promotion, pause, and rollback from ledger entries.
- Remove an observation and confirm the view displays uncertainty rather than inferred state.
Deliverables
- Release ledger projection and responder guide
Rollout and recovery
Use the ledger during a full local rollback rehearsal before handoff.
Value of the work
For the engineer: Practice immutable promotion, release authority, compatibility gates, canaries, and rollback.
For the team: Review a delivery flow that can identify exactly what is running and restore a known artifact without rebuilding it.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.