Agent Context & Exploration
This section is the working surface for Phase R research. It’s modeled on crosswalker’s agent-context/ pattern: freeform notes, decision logs, open problems, and exploration writing that doesn’t yet belong in the polished Concepts / Design / Reference layers.
What goes here
Section titled “What goes here”zz-log/. One file per decision or session. Captures the “why” at the moment of choosing, before the reasoning fades.zz-challenges/. Not questions to ask later — problems that need exploration now.FOCUS.md in the .claude/ folder.Naming conventions
Section titled “Naming conventions”zz-log/— thezz-prefix sorts these folders to the bottom of autogenerated sidebars. Files inside use the patternYYYY-MM-DD-slug.mdxso they sort chronologically.zz-challenges/— samezz-prefix for sort order. Files are named by challenge slug, not date.- Top-level
agent-context/*.mdx— general exploration pages that don’t fit the log or challenge categories. UseSCREAMING_SNAKE_CASEper the project style guide.
Relationship to .claude/ files
Section titled “Relationship to .claude/ files”The .claude/ folder is agent-context too, but it’s the meta layer: PROJECT_CONTEXT, FOCUS, KNOWLEDGE_BASE_PHILOSOPHY, the numbered first-principles files. Those are read at session start to load context.
This section (docs/src/content/docs/agent-context/) is the rendered version: viewable in the wiki, searchable, crosslinkable from other pages. Content that’s useful to readers goes here; content that’s only useful to agents between sessions stays in .claude/.
Promotion path
Section titled “Promotion path”When a zz-log entry produces a finding that generalizes, promote it to zz-challenges/. When a challenge is resolved or fully scoped, promote the resolution to Concepts/ or Design/. The zz- folders accumulate; the polished sections stay deliberately thin.