update

Update

Ingest external information into this ops repo's knowledge base. Two modes depending on whether arguments are provided.

Detect Mode

• If $ARGUMENTS is non-empty → Inline mode: the arguments contain the information to integrate.
• If $ARGUMENTS is empty or blank → Inbox mode: process files from .update/.

---

Inline Mode

The user provided content directly: $ARGUMENTS

1. Load context. Read CLAUDE.md and MEMORY.md to understand the repo structure, goals, and current state.

2. Classify the information. Apply the whole-file test from CLAUDE.md — fact about the world, or decision/framework?

   • Fact about the world (status, metric, inventory) → state/
   • Decision / strategy / framework / guardrails / research → references/
   • Specific actions to do next → backlog/
   • Delivered output → artifacts/
   • Strategic insight → may also warrant a MEMORY.md Key Learnings update
   • Mixed → split

   Trap: "current strategic posture" content feels state-shaped but is forward-looking strategy → references/.

3. Integrate. For each piece of information:

   • Read the target file first — never overwrite blindly. Merge or append.
   • When updating state files, update the _Last updated: YYYY-MM-DD_ line.
   • When adding backlog items, insert in priority order (highest first), not at the end.
   • If placement is ambiguous, apply the Whole-File Test and place it anyway — then note the call in a clause when you report. Ask the user only when the ambiguity is about what the information means for the project: a fact you can't reconcile with existing state, or a claim that changes a stated goal. Never ask which folder something belongs in.

4. INDEX.md cascade. For every file created or significantly changed, update that folder's INDEX.md. If the folder's overall summary changed, cascade to the parent INDEX.md.

5. MEMORY.md check. If the information shifts the project's strategic understanding — a new constraint, a key learning, a changed goal — add or update an entry under Key Learnings. Don't add specific data points (those belong in state/references); only add general insights.