From 592577f7cd3a3c5182244aa9ce7e2ed986e5ac78 Mon Sep 17 00:00:00 2001 From: tegwick Date: Fri, 3 Jul 2026 00:49:39 +0200 Subject: [PATCH] Document implicit default phase-memory activation in ops-warden. --- docs/ops-warden-memory-contract.md | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/docs/ops-warden-memory-contract.md b/docs/ops-warden-memory-contract.md index 68d4d9e..ee4010f 100644 --- a/docs/ops-warden-memory-contract.md +++ b/docs/ops-warden-memory-contract.md @@ -55,14 +55,19 @@ Rejected writes containing token-like values or raw URLs. Rigid memory (charter, allowlist) is import-only and never promoted from episodes. +## Default Behavior + +Memory is enabled by default (`WARDEN_MEMORY=1`). ops-warden implicitly calls +`ensure_memory_context` on every command; explicit `warden memory activate` is +optional introspection only. + ## Agent Session Orientation Coding agents should: -1. Set `WARDEN_AGENT_ID` to their runtime id. -2. Run `warden memory activate --json` at session start. -3. Use normal `warden route` / `warden access` commands; episodes are recorded - automatically when memory is enabled. +1. Set `WARDEN_AGENT_ID` to their runtime id (claude, codex, grok, or future). +2. Use normal `warden route` / `warden access` commands; memory loads and episodes + are recorded automatically. ## Evaluation