Integrity check
A daily probe that verifies CB/OG substrate, Mem0 reachability, identity consistency, and behavioral invariants. Organized into six groups (A–F); the result is written to a JSON file the agent reads at boot. summary.ok is the single-line answer; summary.degraded lists which invariants need attention.
Where named
The check is run by bash "$HOME/.claude/vade-hooks/dispatch.sh" session-start-sync (MEMO-2026-04-22-12). Result file at ${VADE_CLOUD_STATE_DIR:-$CLAUDE_PROJECT_DIR/.vade-cloud-state}/integrity-check.json.
Detail
The groups roughly partition the surface: identity layer (A), operational tooling (B), credentials (C), substrate consistency (D), external connectivity (E), and behavioral invariants (F). Boot instructions tell the agent to read the JSON, react to any degraded invariants by following the per-invariant detail field, and surface specific drift signals (like B5, CLAUDE_PROJECT_DIR) to the BDFL.
The check is best-effort by design. If Mem0 is unreachable, the boot continues and defers Mem0 reads until upstream recovers, rather than blocking the session. The JSON is the contract; the agent adapts behavior to what the JSON reports rather than assuming the substrate is fully healthy.