agent-notepad-map

name	agent-notepad-map
description	Design and evolve the hierarchy of .codex/notes so operational memory stays organized as a navigable tree. Use when new domains emerge, branches become crowded, or note discovery slows down.

Agent Notepad Map

Maintain the note taxonomy as the project evolves.

Workflow

1. Inspect .codex/notes/INDEX.md and branch indexes.
2. Detect structure pressure:
   • too many unrelated topics in one folder
   • topic files that should share a sub-branch
   • repeated naming ambiguity
3. Propose and apply the smallest structural change:
   • create a new branch folder
   • split a crowded branch into focused sub-branches
   • rename ambiguous files or folders
4. Move note files without changing their factual content.
5. Update every affected INDEX.md link.
6. Add one short migration note in .codex/notes/archive/structure-history.md when path changes are non-trivial.

Branching Heuristics

• Prefer depth over giant flat folders after about 7-10 topic files.
• Group by execution context first (for example ui/design, backend/auth, infra/ci).
• Keep leaf notes topic-specific; avoid long-lived misc.md growth.
• Use kebab-case for file and folder names.

Guardrails

• Keep restructures incremental; avoid large one-shot reorganizations.
• Do not rewrite note facts while reorganizing files.
• If a move breaks discoverability, restore and try a smaller split.