R01 · Patch
Apply a precise, reversible fix to code or Paper nodes and check the result.
- Status
- Proposed
- Last reviewed
- 2026-10-06
- Stage
- Operations
How to use this route
The change is already defined: no exploration, research or delegation. One targeted fix pass after the first check; report remaining issues instead of iterating.
Stages: explore, refine, ship. Work surface: as specified in the assignment. Involvement and budget come from the run's dials (shared rules).
Map
Read from top to bottom. Labeled arrows show conditions; dashed arrows exist only in the stages they name; loops represent repairs within the budget. Instructions for each node appear below.
Loading diagram…
Mermaid source
flowchart TD
n_in(["Precise fix"])
n_surface{"Where is the change?"}
n_code["Edit the code"]
n_paper["Edit the Paper nodes"]
n_proof["Capture and check"]
n_gate{"Is the problem resolved?"}
n_fix["One targeted fix pass"]
n_done(["Deliver the fix and evidence"])
n_stop(["Report the remaining issue"])
n_in --> n_surface
n_surface -->|"Code"| n_code
n_surface -->|"Paper"| n_paper
n_code --> n_proof
n_paper --> n_proof
n_proof --> n_gate
n_gate -->|"Yes"| n_done
n_gate -->|"No, fix pass left"| n_fix
n_fix --> n_proof
n_gate -->|"Cap reached or blocked"| n_stopInput and outcome
- Input: Precise problem and affected files or nodes.
- Outcome: Local fix with current evidence.
Work limits
Route cap: no new delegations; at most 1 repair batch. The effective budget is the lower of this cap and the budget dial; the stage sets the fix passes per artifact. Shared rules.
Step instructions
Precise fix
Read the expected result, the target files or nodes and the constraints.
ID: in.
Continue with «Where is the change?».
Where is the change?
Distinguish code from Paper nodes.
ID: surface.
- Code → «Edit the code».
- Paper → «Edit the Paper nodes».
Edit the code
Apply jado-craft-core in code mode; change only the assigned scope.
Skill instructions jado-craft-core ID: code.
Continue with «Capture and check».
Edit the Paper nodes
Read the affected nodes and an initial capture, then edit with jado-canvas-layout.
Skill instructions jado-canvas-layout ID: paper.
Continue with «Capture and check».
Capture and check
Code: check the affected viewport and state in the browser. Paper: apply jado-canvas-verify to the changed nodes.
ID: proof.
Continue with «Is the problem resolved?».
Is the problem resolved?
Compare the capture with the expected result.
ID: gate.
- Yes → «Deliver the fix and evidence».
- No, fix pass left → «One targeted fix pass».
- Cap reached or blocked → «Report the remaining issue».
One targeted fix pass
Fix only what the check found, then capture again.
ID: fix.
Continue with «Capture and check».
Deliver the fix and evidence
Return changed files or nodes and the capture.
ID: done.
The route ends here.
Report the remaining issue
State what is still wrong and why the cap or a blocker stopped the work.
ID: stop.
The route ends here.