Context Circuit
Concepts

Product knowledge

Accepted project understanding that survives a task, a session, and a machine.

Template 2.5.0CLI 2.5.0

What belongs here

Knowledge notes explain durable architecture, domain rules, conventions, decisions, vocabulary, and repository relationships. They describe the product as it is, rather than task progress. Raw evidence stays separate from accepted knowledge.

context/INDEX.md is an optional retrieval catalog, searched for the entries a task needs rather than read in full. One unwrapped entry names a note, its repositories, the question it answers, search terms, and the date it was reviewed against code. The glossary maps project vocabulary to code identifiers.

Make claims traceable

A note collects logical repository paths in an Owner: block. These are code anchors, not machine-specific paths. A note never names an intent, plan, or raw source file as its durable authority. Knowledge stays English; domain names and code identifiers retain their spelling.

Keep it current

Completion asks which notes the actual change affected. Update the note and its catalog entry together, including the reviewed date, and rewrite the entry's search terms against what the note now says rather than only adding to them. An unchanged concept needs no rewrite.

Borrowed knowledge and sources

Borrowed knowledge is read-only here. A wrong borrowed fact is neither copied nor corrected in context/: the agent tells you the fix goes upstream through that repository's own review, and does not edit, clone, commit to, or push the borrowed repository unless you ask for that as its own task.

Raw evidence under sources/ is read only when a person or task names the exact file. The workspace ships a root .ignore with /sources/, which keeps the folder out of ripgrep-based search, including Claude Code's Grep and Glob and Cursor's search; with any other search the agent leaves it out itself.

See gather project context.

On this page