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 for automated failover and HANDOFF_READY_MANUAL_FAILOVER for the XCSV baton.

Fresh checks on 2026-08-08 proved the existing continuity lane is usable for a manual baton and read-only sidecar critics:

• D:\XCSV\tools\xcsv-continuity.ps1 hydrate reads the active XCSV baton.
• D:\XCSV\tools\xcsv-continuity.ps1 verify-isolation returns PASS_BASIC_ISOLATION.
• D:\XCSV\tools\xcsv-continuity.ps1 failure-test returns PASS_FAILURE_DOES_NOT_MUTATE_HANDOFF.
• openclaw --profile xcsvcontinuity config validate reports the isolated config valid.
• openclaw --profile xcsvcontinuity sessions list --json reports zero sessions under C:\Users\Architect\.openclaw-xcsvcontinuity\agents\main\sessions\sessions.json.
• openclaw --profile xcsvcontinuity plugins list --json --enabled loads 32 enabled bundled plugins with no registry diagnostics.
• openclaw --profile xcsvcontinuity skills list --json --eligible succeeds; unavailable optional skills were disabled by openclaw --profile xcsvcontinuity doctor --fix --non-interactive --yes.
• The default and profile OpenClaw approval files remain distinct by SHA256 after repair.
• ollama run qwen3-4b-instruct "Reply exactly: XCSV local fallback OK" returned the requested phrase.

Do not upgrade this to automatic failover authority yet. Hermes profile isolation is file-proven, but no hermes executable is currently on PATH and the xcsvcontinuity profile has no API keys. OpenClaw profile initialization previously migrated the default C:\Users\Architect\.openclaw\exec-approvals.json into the new profile and archived the default file as .migrated; the default file was restored. Treat OpenClaw as collision-sensitive and read-only until profile operations are covered by a stronger before/after hash test that wraps real OpenClaw commands.

2026-08-08 EXILE-DB-001 Checkpoint

Active extDB3 SQL_CUSTOM file is proven as E:\arma3server\@ExileServer\sql_custom\exile.ini. Proof: launcher runs from E:\arma3server with -servermod=@ExileServer; RPT loaded E:\arma3server\@ExileServer\extDB3_x64.dll; extDB3 logs are written under @ExileServer\logs; local runbooks and extDB3 staging tools identify @ExileServer\sql_custom\exile.ini as the live SQL_CUSTOM file. The @ExileServer\extDB\sql_custom\exile.ini copy is a byte-identical compatibility mirror.

EXILE-DB-001 repaired four $CUSTOM_1$ query templates: insertConstruction, insertContainer, updateContainer, and createTerritory. The repair uses NULLIF(?, 'NULL'); updateContainer and createTerritory require non-sequential SQL1_INPUTS so the former $CUSTOM_1$ argument remains bound to the nullable column.

OpenClaw remains collision-sensitive. The XCSV profile reports zero sessions at C:\Users\Architect\.openclaw-xcsvcontinuity\agents\main\sessions\sessions.json, but its approval file copied shared authorization material from the default profile. Manual failover via the XCSV baton is the allowed continuity path until OpenClaw profile initialization is fully characterized.