agent-notepad-capture

name	agent-notepad-capture
description	Persist operational learning as atomic, topic-specific notes inside the .codex/notes tree. Use during and after tasks to create or update leaf notes, route them into the right branch, link evidence, and keep the note map navigable.

Agent Notepad Capture

Store memory as small files in domain branches.

Workflow

1. Choose the branch path in .codex/notes/ that best matches the topic.
2. If the branch does not exist, create it with an INDEX.md and link it from the parent index.
3. Use one file per narrow topic (kebab-case.md).
4. Update existing topic files before creating new ones to avoid duplication.
5. Keep each note focused and short; split when a file starts covering multiple concerns.
6. Add traceability to each claim:
   • Status: draft|active|stable|needs-revalidation|superseded
   • Confidence: high|medium|low
   • Last-Validated: YYYY-MM-DD
   • Evidence: <file path | command>
7. When new evidence contradicts an old note, update the old note as superseded and link the replacement.
8. Update branch INDEX.md entries so lookup can discover the note quickly.

Recommended Note Template

# <Topic>

- Status: active
- Confidence: medium
- Last-Validated: YYYY-MM-DD
- Evidence: <path or command>

## Facts
- <single factual statement>

## Implications
- <what this changes for execution>

## Follow-ups
- <open checks or next validation>

Guardrails

• Do not keep long rolling journals in a single file.
• Do not store secrets or credentials.
• Do not promote assumptions to facts without evidence.