Staff archive-closure preview
CivicPal notice archive-closure handoff
Review how CivicPal can summarize archive-history proof, successor-link proof, retention posture, and unresolved blockers before any live archive closure, delete boundary, or delivery runtime exists.
Preview-only archive-closure surface
Ready for archive-closure review
This preview row shows the archive-closure handoff shape when history proof, successor-link proof, and retention posture are all documented for the next bounded closure slice.
- Archive/history route confirms why the notice remains in the trust trail
- Successor or fallback route proof is documented for any replaced public guidance
- Retention posture is labeled as explanatory only until a later runtime slice exists
Ready rows stay deterministic here. They frame what must be handed off before any live archive closure or delete boundary exists.
Successor-link proof still blocks closure
Use this state when archive closure cannot move forward because the notice history does not yet point clearly to the current public guidance or fallback route.
- Current replacement notice or fallback route is still missing from handoff proof
- Staff history remains visible until successor-link proof is review-safe and complete
- Closure stays blocked rather than implying the notice can be removed from the trust trail
This blocker stays explanatory only and does not mutate route state, unpublish content, or open a workflow backend.
Retention posture still needs review
Use this state when staff can show archive history but cannot yet describe the closure boundary clearly enough for the next bounded retention slice.
- Retention wording stays public-safe and avoids promising deletion timing
- Language parity or caveat notes are preserved wherever closure wording differs
- Closure guidance explains that future retention behavior is still bounded work
Retention posture remains preview-only here and does not create jobs, timers, or real record-management behavior.
History proof is still incomplete
Use this state when archive closure cannot be reviewed safely because the trust-trail evidence or blocked-channel history is still incomplete.
- Trust-trail record still needs review-safe history notes or blocked-channel framing
- Preview-only channel posture remains visible until later bounded runtime work exists
- Archive closure stays blocked until historical proof is complete and handoff-safe
This state keeps the missing history proof visible without claiming live archive closure, retention enforcement, or delivery records.
Route handoffs stay explicit