Staff archive-continuity preview

CivicPal notice archive continuity handoff

Review how CivicPal can summarize successor continuity, fallback continuity, and unresolved trust-trail continuity blockers before any live continuity automation, redirect behavior, or delivery runtime exists.

Preview-only archive continuity surface

This route does not automate continuity, redirect readers, or collapse the archive trail. It exists to prove the deterministic archive continuity handoff shape under CPAL-142.
Ready for continuity handoff reviewNotice expired

Ready for continuity handoff review

This preview row shows the continuity handoff shape when successor proof, fallback guidance, and trust-trail continuity are all documented for the next bounded archive slice.

  • Successor notice or archive fallback path is documented as the current continuation route
  • Archive closure and successor proof still explain why the older notice remains reviewable
  • Continuity story stays explicit even when no live redirect or automation exists

Ready rows stay deterministic here. They frame the continuity handoff story without mutating routes, replacing content, or enabling delivery behavior.

Blocked for successor continuity proofNotice under review

Successor continuity proof still blocks handoff

Use this state when archive continuity review cannot move forward because successor proof still leaves a gap between the older notice and the current public guidance.

  • Current successor route still needs a clearer continuity handoff from the archived notice
  • Archive guidance remains visible until successor continuity proof is explicit
  • Continuity handoff stays blocked rather than implying the trust trail can collapse automatically

This blocker remains explanatory only and does not rewire links, unpublish content, or create automated archive continuity.

Blocked for fallback continuity proofLanguage unavailable

Fallback continuity proof still needs review

Use this state when staff can show successor and closure proof but cannot yet prove where the public should continue when fallback guidance is the only safe next step.

  • Fallback route keeps guidance continuity without inventing a live redirect or hidden continuation record
  • Language parity notes remain visible wherever continuity and fallback guidance differ
  • Continuity 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.

Blocked for trust-trail continuityChannel unavailable

Trust-trail continuity is still incomplete

Use this state when continuity review cannot close safely because the archive trust trail still lacks enough continuity notes or blocked-channel visibility.

  • Trust-trail notes still need review-safe continuity references across archive, closure, and successor proof
  • Preview-only channel posture remains visible until later bounded runtime work exists
  • Continuity handoff stays blocked until archive trust-trail evidence is complete and handoff-safe

This state keeps unresolved trust-trail continuity visible without claiming live replacement, deletion, or delivery records.

Route handoffs stay explicit

Staff can step back to archive successor proof, archive closure, archive history, publish-readiness, review approval, compose preview, or workflow overview without implying a live continuity engine, redirect runtime, or continuity datastore.