Staff archive-successor preview
CivicPal notice archive successor proof
Review how CivicPal can summarize replacement notice linkage, fallback-route continuity, and unresolved closure blockers before any live successor rewiring, redirect behavior, or delivery runtime exists.
Preview-only archive successor surface
Ready for successor-handoff review
This preview row shows the successor-proof shape when replacement notice linkage, fallback continuity, and archive-closure proof are all documented for the next bounded handoff slice.
- Replacement notice route is documented and labeled as the current public guidance
- Fallback route keeps public guidance continuity if no direct successor notice exists
- Archive-closure proof still explains why the older notice remains in the trust trail
Ready rows stay deterministic here. They frame the successor handoff story without mutating routes, replacing content, or enabling delivery behavior.
Replacement notice linkage still blocks successor proof
Use this state when archive successor review cannot move forward because the current notice route or replacement guidance is still missing from the handoff story.
- Current replacement notice route is still missing or not review-safe enough to reference
- Older archive guidance remains visible until the replacement linkage is explicit
- Successor proof stays blocked rather than implying the archive trail can be collapsed
This blocker remains explanatory only and does not rewire links, unpublish content, or open a workflow backend.
Fallback route continuity still needs proof
Use this state when staff can show archive history but cannot yet prove where the public should go when there is no direct replacement notice.
- Fallback route keeps guidance continuity without inventing a live redirect or replacement record
- Language parity notes remain visible wherever successor and fallback guidance differ
- Successor proof explains what remains future bounded work before any live continuity runtime exists
Fallback continuity stays preview-only here and does not create redirects, route rewrites, or stored audience state.
Archive-closure proof is still incomplete
Use this state when successor review cannot close safely because the archive-closure handoff still lacks enough trust-trail proof or blocked-channel continuity.
- Archive-closure notes still need review-safe successor or fallback references
- Preview-only channel posture remains visible until later bounded runtime work exists
- Successor proof stays blocked until archive-closure evidence is complete and handoff-safe
This state keeps unresolved closure proof visible without claiming live replacement, deletion, or delivery records.
Route handoffs stay explicit