cognitive-update

# /cognitive-update Nightly uses this shared protocol after `/system-check`. It never infers a durable state change from one agent-authored claim. ## Ownership fence This protocol may update only: - `vault/memory/runtime/GOAL_STACK.json` - `vault/memory/runtime/BELIEF_STATE.jsonl` (append-only) - `vault/memory/runtime/SELF_MODEL.json` - `vault/memory/runtime/PROCEDURES.jsonl` (append-only) The documented `memory/` fallback is valid for minimal installations. This protocol never writes `ACTIVE_STATE.json` or `STATE_EVENTS.jsonl`; the runtime state daemon owns those products. It never writes Dream or measurement ledgers. ## Evidence admission Direct updates require one of: - the operator's explicit goal, belief, or procedure statement with a durable source reference; - a repository-owned command or test invoked with explicit arguments and a literal exit code; - an external artifact that directly decides the claim; - two independent observed occurrences for a recurring capability or failure. Capsules and Session Log entries are discovery sources. They cannot verify their own confident claims. If evidence is incomplete, skip the durable update and stage an observation through the nightly evidence flow. ## File rules ### GOAL_STACK.json Move, append, or update only explicit goals, blockers, next actions, and completions. Completion requires success criteria plus an external artifact or operator confirmation. Preserve unknown fields and unrelated arrays. ### BELIEF...