See how continuity notifications should work.
These cards demonstrate consent review, export readiness, identity, and trust follow-up patterns. They are not evidence that a shared notification was delivered, received, or acknowledged.
Consent scope needs review
Example state: a proof-only sharing scope should be confirmed before export.
Packet preview is ready
Example state: a packet preview can be reviewed in the Export Vault.
Identity check
Example state: context-aware sign-in keeps the return route attached without asking for internal app keys.
Trust review
Example state: privacy, source, authority, and deployment boundaries may need review.
What would make this live?
A shared inbox requires a connected source of notification events, authorized recipient routing, delivery state, read/acknowledgement state, revocation and privacy rules, and auditable receipts. Those capabilities are not represented as connected here yet.