Temper → Build
Return to Build when the intent is clear and the implementation needs to change or strengthen.
The model
The Tempering Loop
Brief → Clarify → Build → Evaluate → Temper
A person and coding agent turn a brief into explicit intent. TemperWeave provides the system for authoring through MCP, reusing capabilities and keeping the implementation, graph and evidence connected.
The Tempering Loop makes the important requirements and constraints explicit, then builds, proves or falsifies claims and uses the resulting evidence to decide what needs to happen next.
Brief
You start with the outcome you need. That may be a direct request, a client brief or just a rough idea.
The brief gives us something to work with without pretending every decision has already been made. It establishes what the work is for and gives the rest of the Tempering Loop something concrete to work from.
Focus
- The outcome the person needs the work to achieve.
- The context, audience and source material they can provide.
- Known constraints, dependencies, available capabilities and open questions.
It leaves you with
A working statement of intent for the person and coding agent to clarify, including what may be reused and the unknowns that still need attention.
Clarify
You and the coding agent turn the brief into clear commitments before the work starts to sprawl.
The coding agent asks the questions that expose gaps in the brief. You bring the client context and judgement only you can provide: what needs to be true, what is out of scope and what you are prepared to stand behind.
Focus
- The commitments the implementation needs to support.
- Requirements, boundaries and constraints that keep scope under control.
- How the important claims can be proved, challenged or falsified.
- Questions that need your judgement before they become accidental choices in the implementation.
It leaves you with
A shared definition of the work: what it must do, the conditions it must meet, the evidence it needs and the judgement it still requires.
Build
TemperWeave builds against the clarified intent, so your team can move quickly without losing the thread of what was agreed.
It can author through MCP and compose work from reusable capabilities, so every client project does not need to start from zero. The implementation stays connected to the commitments behind it, whether you need a graph view, the evidence or the underlying files.
Focus
- The implementation, from high-level system shape to the underlying files.
- Reusable capabilities that can be composed instead of rebuilt from scratch.
- The decisions that connect each part of the work to the commitments behind it.
- The dependencies, assumptions and trade-offs introduced while building.
It leaves you with
Implementation you can inspect, reuse and prepare to hand over with the intent behind it still intact.
Evaluate
Before you hand work over, TemperWeave evaluates it against the commitments you made and brings the evidence back for your review.
Evaluation does more than mark work complete or incomplete. TemperWeave attempts to prove the claims that matter and falsify the ones that do not hold up, so you can see what the result supports before it reaches the client.
Focus
- The relationship between the commitments you made and the implementation.
- Evidence that proves, challenges or falsifies a claim.
- Issues, limitations and uncertainty that need your judgement.
It leaves you with
A clear account of what was proved, what was falsified, what needs work and what still needs your judgement.
Temper
TemperWeave uses the evaluation to resolve issues, strengthen confidence and make uncertainty visible before you decide the work is ready.
When claims have been falsified but the intent is clear, TemperWeave returns to Build. When the evidence shows that intent is missing, ambiguous or incomplete, you and the coding agent return to Clarify. This is how the Tempering Loop keeps moving without hiding uncertainty or treating a first result as final.
Focus
- Issues TemperWeave can resolve by changing or strengthening the implementation.
- Ambiguity or missing intent that needs clarification before more work is built.
- Uncertainty you should see with the result rather than discover after handover.
It leaves you with
The right next pass: back to Build, back to Clarify with the coding agent, or a result accompanied by the evidence and uncertainty you need to judge it.
Temper → Clarify
Return to Clarify when evidence exposes ambiguity, missing intent or a requirement that still needs a decision.
The Tempering Loop
- Brief
- Clarify
- Build
- Evaluate
- Temper
Temper is the control point for the next pass. When the intent is clear and the implementation needs work, TemperWeave returns to Build. When evaluation has exposed ambiguity, missing intent or an unresolved requirement, the person and coding agent return to Clarify.
Current status
TemperWeave is in alpha. The Tempering Loop describes the direction in which the product is being developed.
Request an invite