Releases kept
Verification and recovery · release record. On a deployment this row is a control; the demo shows the row with the reading its source supports.
Evidence
- Running
- 2 of 2 tagged releases kept (3 images retained)
- Built
- 1.0 (2026-08-29), 1.1 (2026-09-03)
- Latest known
- 1.1 (2026-09-03)
- Source
- git for-each-ref refs/tags
- Checked
- 2 hours ago
- Cadence
- none — record only
- Mode
- record only
- State
- current
- Backup unit
- The kept image digests are the backup unit of every release-borne row.
- Recovery
- compose up -d a kept digest; the verify sweep runs before recovered is shown.
The five steps
Plan, back up, apply, verify, recover — in record only mode. On a deployment each step runs, is verified and lands on the audit trail; every component on the demo is current, so every step reads done.
- ✓ done Plan The tags and the digests kept for them are listed with their stamps; there is nothing to confirm.
- ✓ done Back up The kept digests are the backups; nothing further is copied here.
- ✓ done Apply Nothing is applied; a digest is removed only after a newer verified release exists.
- ✓ done Verify Each kept digest is present in the registry and its stamp matches its tag.
- ✓ done Recover Nothing is recovered here; the Running image row rolls back to a kept digest.
Every row behind this reading (2)
| Release | Date | Commit | Kept |
|---|---|---|---|
| 1.0 | 2026-08-29 | bf1d7d712b71 | kept |
| 1.1 | 2026-09-03 | 960264d9b3ec | kept |
History
Applies and recoveries of this row, from the update journal. On a deployment every apply and every recovery lands here as it completes.
No apply or recovery recorded for this row. The demo's journal holds one completed update, of Running image.
Acknowledge: keep as is until <date> because <reason> — on a deployment this line is a form, audited as system.component_acknowledged; the demo shows the words.