Menu
Conservative close-parity updates to GOAL_STACK, BELIEF_STATE, SELF_MODEL, and PROCEDURES. Writes only explicit or mechanically evidenced deltas; ambiguity means no write.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
The capsule verb, invoked explicitly — reconcile from the live memory, write a resume-ready capsule, then stop. Mid-session checkpoint or completion capsule; a rolling best-effort version of the same write also runs automatically on every Stop event via daemons/stop-capsule-writer.mjs.
The resume verb, invoked explicitly — load the newest valid capsule by created_at, re-ground against live memory, then ACT on waiting_on. Mid-session or on explicit ask; the post-clear boot fires the same procedure automatically via daemons/resume-verb.mjs.
Search vault notes by meaning using local embeddings
Canonical seven-leg nightly close-parity protocol. Eleven independently evidenced checkpoints cover synthesis, reconciliation, context hygiene, sweeps, heat, digest, runtime health, cognitive state, ledger capture/review, and vault sync.
Commit the session to durable vault memory and prepare a clean resume point
Nightly context trim for ACTIVE_PRIORITIES and the dated SESSION_LOG schema. Archives before removal, uses content-hash compare-and-swap, and refuses unknown shapes.
| name | cognitive-update |
| agent | none |
| description | Conservative close-parity updates to GOAL_STACK, BELIEF_STATE, SELF_MODEL, and PROCEDURES. Writes only explicit or mechanically evidenced deltas; ambiguity means no write. |
| allowed-tools | Read, Write, Bash |
| user-invocable | true |
| status | PRODUCTION - conservative and source-referenced |
| triggers | ["cognitive update","update cognitive state","runtime state update"] |
Nightly uses this shared protocol after /system-check. It never infers a
durable state change from one agent-authored claim.
This protocol may update only:
vault/memory/runtime/GOAL_STACK.jsonvault/memory/runtime/BELIEF_STATE.jsonl (append-only)vault/memory/runtime/SELF_MODEL.jsonvault/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.
Direct updates require one of:
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.
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.
Append only. A revision reuses the original id and includes revision_note; a
new belief receives max numeric bNNN plus one. Do not use line count. Serialize
UTF-8 JSON and parse the appended line.
Update only named capability, limitation, recurring-failure, reliability-risk,
or achieved-learning-goal fields. When alias arrays coexist, update each alias
pair in lockstep or fail SELF_MODEL_ALIAS. A one-off result is not a durable
capability.
Append only when the sequence occurred at least twice, the operator explicitly
made it standing, or a non-obvious workflow was mechanically proven. Allocate
max numeric pNNN plus one and parse after append.
Hash every source immediately after read and compare again before write. A hash change aborts rather than clobbering newer state. Preserve JSON formatting where practical; always serialize JSONL.
A nightly fire uses the immutable snapshot created by nightly-pass begin.
For explicit use, create an operating-system temp snapshot:
node daemons/nightly-contracts.mjs snapshot --root <aigent-root> \
--out <os-temp>/cognitive-contract-before.json
After any updates:
node daemons/nightly-contracts.mjs cognitive --root <aigent-root> \
--snapshot <os-temp>/cognitive-contract-before.json \
--new-belief-ids <csv> --new-procedure-ids <csv> \
--self-alias-additions <csv>
Only COGNITIVE_CONTRACT PASS is green. The validator re-parses all four
products, proves append-only suffixes, derives allocated ids, validates new-row
schemas, and derives alias additions and removals.
Return:
COGNITIVE_UPDATE PASS goals=<N> beliefs=<N> self_model=<N> procedures=<N> skipped=<N>