Retire SBOM Nexus production cutover
Assistant: codex Assistant-Model: gpt-5.6-sol Assistant-Session: 01a028f0-a42f-7582-89a8-ebaad7343834
This commit is contained in:
parent
11a07a697b
commit
0b14e0d0b2
2 changed files with 64 additions and 2 deletions
|
|
@ -4,7 +4,7 @@ type: workplan
|
|||
title: "Deploy and cut over SBOM Nexus production authority"
|
||||
domain: infotech
|
||||
repo: sbom-nexus
|
||||
status: active
|
||||
status: finished
|
||||
owner: codex
|
||||
topic_slug: infotech
|
||||
created: "2026-08-22"
|
||||
|
|
@ -13,6 +13,10 @@ quality_dor: DoR-Ok
|
|||
quality_dor_at: "2026-08-22"
|
||||
quality_dor_by: codex
|
||||
quality_dor_note: "Goal, ownership boundaries, staged dependencies, production safety gates, reconciliation evidence, rollback paths, and cross-repository handoffs were reviewed against the implemented Nexus contract and current State Hub history."
|
||||
quality_dod: DoD-Ok
|
||||
quality_dod_at: "2026-08-22"
|
||||
quality_dod_by: codex
|
||||
quality_dod_note: "Production authority, migration reconciliation, reversible caller cutovers, scanner handoff, bounded automation, retention decision, clean verification, evidence, and owner-directed retirement were reviewed. The scheduled Monday observation was explicitly waived rather than claimed; legacy history remains retained and no destructive cleanup was performed."
|
||||
parent_workplan: CUST-WP-0062
|
||||
related:
|
||||
- SBOM-WP-0001
|
||||
|
|
@ -157,7 +161,7 @@ disabled and paused. See
|
|||
|
||||
```task
|
||||
id: SBOM-WP-0002-T07
|
||||
status: wait
|
||||
status: done
|
||||
priority: medium
|
||||
state_hub_task_id: "bb1ff087-f204-5fd0-9295-3bd10bf0d38a"
|
||||
```
|
||||
|
|
@ -165,3 +169,16 @@ state_hub_task_id: "bb1ff087-f204-5fd0-9295-3bd10bf0d38a"
|
|||
Capture two successful daily fires and a zero-flood Monday window. Record the
|
||||
retention decision, then retire State Hub SBOM ownership after the stabilization
|
||||
window without deleting historical data implicitly.
|
||||
|
||||
Retired by explicit owner direction on 2026-08-22 after the Hall of Helix entry
|
||||
was published. The already-proven conditions are recorded exactly: two bounded
|
||||
production fires, six distinct terminal outcomes, zero spawned tasks, an active
|
||||
daily schedule, and the legacy weekly schedule disabled and paused. The owner
|
||||
waived waiting for the next Monday observation; this record does not claim that
|
||||
window occurred.
|
||||
|
||||
Retention decision: keep State Hub's 22 historical snapshots and compatibility
|
||||
surface read-only as rollback evidence. New reads and writes remain owned by
|
||||
SBOM Nexus. Do not delete the retained rows, remove rollback flags, or tear out
|
||||
the façade as part of this retirement. See
|
||||
`docs/evidence/SBOM-WP-0002-T07-retirement-2026-08-22.md`.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue