AI Continuity

AI Continuity

XCSV uses an isolated continuity lane named XCSV_AI_CONTINUITY.

Runtime state root: D:\CAGE\xcsv-ai-continuity

Tracked operator entrypoint: D:\XCSV\tools\xcsv-continuity.ps1

Hermes profile: xcsvcontinuity

OpenClaw profile: xcsvcontinuity

The lane carries only the active baton: work item, authority, source/runtime state, evidence, unknowns, blockers, and one bounded next action. It must not store chat transcripts or previous-worker summaries as authority.

Commands

Create or update the current baton:

D:\XCSV\tools\xcsv-continuity.ps1 checkpoint

Show the current baton:

D:\XCSV\tools\xcsv-continuity.ps1 show

Hydrate a continuation summary:

D:\XCSV\tools\xcsv-continuity.ps1 hydrate

Show worker policy:

D:\XCSV\tools\xcsv-continuity.ps1 workers

Verify basic isolation:

D:\XCSV\tools\xcsv-continuity.ps1 verify-isolation

Run the simulated worker-exhaustion check:

D:\XCSV\tools\xcsv-continuity.ps1 failure-test

Isolation Rules

XCSV handoffs, logs, receipts, prompts, worker histories, routing state, and authority envelopes stay under D:\CAGE\xcsv-ai-continuity or tracked XCSV repo files.

Do not store XCSV baton state in Hermes default state, Hermes sovran-command-deck, OpenClaw default state, or any SOVRAN project directory.

Current Status

Status is PARTIAL.

Hermes profile isolation is established. OpenClaw profile isolation exists, but initializing openclaw --profile xcsvcontinuity config file unexpectedly migrated default C:\Users\Architect\.openclaw\exec-approvals.json into the new profile and archived the default file as .migrated. The default file was restored from the archive. Treat OpenClaw profile initialization as collision-sensitive until this behavior is fully understood and covered by a stronger collision test.