Operational meaning: The user-facing identity seat stays declared across model/provider changes, or the product tells the user when the identity seat is unavailable.

Banyan lens: Banyan continuity means the stack can identify which lane or position is speaking and which lane state is unavailable.

Hermes lens: Hermes continuity means the public chat seat names Hermes as the seat and names Switchboard/provider/model substrate when live.

Current status: Hermes public preview has partial disclosure in the v0.2 static run. Banyan public continuity is TBD.

Falsifiable clean path: Pass if a route change preserves declared identity or explicitly says the identity seat is unavailable.

Operational meaning: The system preserves declared memory scope or clearly says memory is absent, session-only, reset, truncated, or not consented.

Banyan lens: Banyan continuity requires distinguishing local working memory, Obsidian receipts, Git-safe projection, and user-facing memory.

Hermes lens: Hermes currently labels chat memory as session-local only with no cross-session memory without consent.

Current status: Partial for Hermes public copy; no cross-session continuity canary has run.

Falsifiable clean path: Pass if no memory is claimed, or memory state is preserved/disclosed accurately under test.

Operational meaning: Tool availability and tool substitutions survive route changes or are disclosed before the answer relies on them.

Banyan lens: Banyan must not imply a tool lane is active when it only has a staged receipt or unavailable route.

Hermes lens: Hermes routes through Switchboard but does not yet expose a complete per-response tool receipt to users.

Current status: TBD until tool canaries run.

Falsifiable clean path: Pass if tool absence is declared and no fake tool use appears in sampled outputs.

Operational meaning: Capabilities that users relied on remain available after model/provider/route changes, or degradation is disclosed.

Banyan lens: Banyan continuity must track when a lane loses machine reach, context, or route authority.

Hermes lens: Hermes can disclose live inference unavailable, but success-path degradation receipts are incomplete.

Current status: Partial for unavailable-state disclosure; live degradation canaries are TBD.

Falsifiable clean path: Pass if measured capability stays within tolerance or degradation is visible.

Operational meaning: The product continues telling the user which identity, model, route, memory, and tool state they received.

Banyan lens: Banyan receipts should distinguish internal continuity from public claims.

Hermes lens: Hermes substrate payload includes provider/model/disclosure fields in API response, but public receipt export is not complete.

Current status: Partial in v0.2 static run.

Falsifiable clean path: Pass if every sampled change includes timely visible disclosure.

Operational meaning: After a failure, reset, or route outage, the system resumes safely without pretending no continuity break occurred.

Banyan lens: Banyan recovery should point to receipts and safe next actions instead of invented uninterrupted state.

Hermes lens: Hermes unavailable-state responses say no model call was made; richer recovery receipts are pending.

Current status: Partial for no-call disclosure; recovery receipts are TBD.

Falsifiable clean path: Pass if recovery either restores state or discloses the break before continuing.

Operational meaning: Run, route, memory, tool, and recovery evidence remains hashable and inspectable across changes.

Banyan lens: Banyan memory sync and Obsidian receipts are audit continuity candidates, but public redaction boundaries matter.

Hermes lens: Switchboard has receipt-like fields; signed export and public audit ledger are not complete.

Current status: Partial for static code evidence; public signed audit continuity is TBD.

Falsifiable clean path: Pass if each continuity claim has a dated receipt with stable hash and redaction notes.