Concepts
Understand the durable records, working copies, and decisions behind each change.
A Context Circuit workspace keeps two kinds of writing apart. Product knowledge describes what is true about the project: architecture, domain rules, conventions, decisions, vocabulary, and repository relationships. Records describe a particular change: the intended outcome, the plans that implement it, and the decisions a person made along the way.
Knowledge survives a task, a session, and a machine. It is English, with domain names and code identifiers kept in their own spelling. A note never names an intent, a plan, or a raw source file as its durable authority. Completion is what brings a note back in line with the code that actually changed.
Records and working copies
An intent writes the outcome a person can approve before detailed code investigation: goal, non-goals, constraints, success criteria, rough repository scope, and numbered open questions. The original request is not approval of that derived outcome. Approval records the person's words and stops with a recommendation to plan; planning follows a request for it.
A plan is code-grounded implementation work linked to that approved outcome. There is no plan approval gate. Implementation waits until a person asks for execution after the plans exist.
A worktree is an isolated Git checkout for a repository a plan touches. It is not a record of approval. Completion removes neither worktrees nor branches. Optional workers receive bounded assignments; they do not replace the person's decisions.
Decisions that stay with you
Approving an intent, asking for plans, asking for execution, authorizing delivery, requesting completion, and requesting cleanup are separate choices. A record preserves a decision. It never makes one. A person can bypass intent and planning for an already-specified change; commits in a bound checkout, delivery, and deletion still need authorization.
- Product knowledge
- Accepted project understanding that survives a task and a machine.
- Context and repository relationships
- How repositories depend on each other, as project knowledge.
- Intents
- A written outcome a person can approve before code investigation.
- Plans
- Code-grounded implementation work linked to an approved outcome.
- Worktrees
- Isolated checkouts where a plan is implemented.
- Worker agents
- Bounded assignments beside the main implementation path.
- Delivery
- Push, pull request, merge, and publication as explicit requests.
- Completion and reconciliation
- The note, then the knowledge the change actually altered.
- Human control boundaries
- What each of your decisions authorizes next.
- Product boundaries
- What the template, CLI, and website each own.