Plan Graph top level + drilldown
01Intake and questions3/3
xGoal captureduser
xClarifications answeredagent
02Plan and capability review2/5
xBlueprint drafteddone
xCapability map produceddone
Persistence lanerunning
API lanerunning
Auth decisionwaiting
subagent: planner-achecking API shape
subagent: evidence-bmapping gates
operator gateapproval required
03Build implementation0/4
04Verify and repair0/3
05Evidence and comparison0/2
Build a support workbench service
Qwen has proposed a plan. Top-level tasks stay readable; expanding them reveals work items, subagents, tool calls, diffs, verification gates, and evidence rows.
Planner: I can build the first version with CLI + API + JSON persistence. Auth should be deferred or represented as a boundary stub.
System: Plan mode blocks writes except the session plan. The visible plan is the approval surface.
Approval needed: include auth as a non-functional boundary stub for this run?
You: Show tasks and what evidence each task will produce.
Planner: Opening task drilldown. The active item will produce contract examples, locked tests, operation counts, and an ACB evidence row.
>Ask, steer, approve, compare, inspect, or interrupt.../plan /tasks /diff /evidence /graph
Evidence + Data Bus live adapter contract
Evidence snapshot
Case Pass1.00
ACB Level5
Quality Issues0
Signaturef464
Current diff
src/support/api.py
- def create_ticket(payload): pass
+ def create_ticket(payload):
+ return service.create(payload)
+ assert response["status"] == 201
Data interaction model
sessionidentity, cwd, mode, provider, permissions, active run
eventsappend-only stream: task_started, tool_call, diff_ready, approval_requested, gate_passed
statederived snapshot for tasks, lanes, active work, counters, blocked gates
signalhighest-priority ambient state: failed, approval, verify, planning, compare, passed, idle
artifactsfiles, diffs, plans, specs, evidence notes, summaries, exported bundles
actionsapprove, interrupt, cancel, retry, rework, compare, open diff, switch mode