The builder
Targets and edit scope
Two controls that constrain what a turn is physically able to touch. Use them once you have a workflow you do not want disturbed.
Once a sequence is validated, the risk stops being “the agent cannot build it” and becomes “the agent changed something I had already signed off”. These two controls exist for that.
Targets: which artifact a turn may write
The chip beside Attach in the composer sets the target. It follows whichever pane you have open, and you can click it to override.
| Target | The agent may | The agent cannot |
|---|---|---|
| Build | Everything. Change the workflow, write documents, wire the schematic, shape the report, start runs. | Nothing is removed. |
| Plan | Write the plan document, look things up, wire the schematic. | Change the workflow. Start a run. Write the report. |
| Report | Shape the report’s structure, units, and limits. | Change the workflow. Start a run. Write a document. Write a measured value, ever. |
Locking to Plan is the right move when you are drafting documentation against a workflow that is already correct. Locking to Report is the right move when you are shaping a deliverable from a run you do not want re-run.
Edit scope: which steps a turn may touch
In Preview, select one or more steps and the turn is scoped to them. A ring appears on the selected steps on the canvas, and a chip appears in the composer saying what you have scoped. A patch that reaches outside the selection is rejected.
- 1
Click a step
The detail panel opens. Use “scope to this” to add it to the scope. - 2
Add more
Scope as many steps as the change involves. A scope bar summarises it above the canvas. - 3
Ask for the change
The turn can rewrite those steps freely and cannot touch anything else. - 4
Clear it
The × on the chip, or the scope bar. Easy to forget, which is why it is shown in two places.
Make this measurement AC coupled with a 20 MHz bandwidth limit.
With one scope step selected, this cannot accidentally re-plan the sweep around it.
When to use which
- Writing docs against a finished test
- Lock the target to Plan.
- Tuning a report for a customer
- Lock the target to Report.
- Fixing one step in a long sequence
- Scope to that step, leave the target on Build.
- Building something new
- Leave both off. Constraints on an empty canvas just get in the way.