The canvas — fill one per process
Work through the nine blocks with every functional seat present. Indigo blocks define human judgment, teal blocks define agent execution, amber blocks define the control layer. Accountability never moves to agents.
Trigger
Calendar, event, or signal? What starts this process today — and what should, once a continuous agent substrate exists?
Accountability map
Which function certifies what? Certification stays human, always.
Execution layer
Assembly, reconciliation, drafting, analysis. Which activities are agent-delegable now / within 12 months?
Judgment layer
Which judgment types does this process consume — taste · trade-off · subtraction · market · risk — and which seat carries each?
Encoded judgment
Which judgments become agent rules? Every rule needs an owner and a review trigger — unowned rules fossilize (B1).
Option architecture
What option sets should agents pre-generate and pre-validate? Where are the human choice points? Reserve one unscored wildcard slot (prevents B6).
Control plane
Six checks: reconciliation · forecast drift · assumption freshness · override log · option-set hygiene · semantic consistency. Name the auditor.
Staffing shape
Consolidators to redeploy; stewards to create; judgment seats to protect. Stewards before redeployment (prevents B7).
Learning loop
Where do juniors form judgment once execution is absorbed? Override reviews, stuck-session drills, shadow certification (prevents B4).
JDEA grid — the task-level actor split
RACI assumed every actor was human. JDEA separates who Judges, who Directs, who Executes (may be non-human), and who Audits.
Rules: every task has exactly one J · A must be independent of J and D · J = E means delegation candidate · empty J means orphaned judgment — bug B3. The grid checks these live.
| TASK | J — JUDGES | D — DIRECTS | E — EXECUTES | A — AUDITS | DIAGNOSTICS |
|---|
Coverage map — lifecycle × judgment type
First place the process/product on its lifecycle stage. Dots show the judgment intensity each stage requires; type the named human carrier in each required cell of your stage. A required cell (●● or more) with no carrier flags GAP. Other stages stay visible for reference — useful when the process is about to transition. Headcount follows judgment gaps — not workload.
| JUDGMENT TYPE | PRE-PMF | GROWTH | MATURE | SUNSET |
|---|
Bug registry — failure modes and their signals
Bugs are failure modes to detect and fix. Each is wired to a control-plane signal so detection is operational, not vibes. Mark a bug detected to log it and open a note field.
Twist registry — role mutations to expect, not fight
Twists are expected mutations to track and support. Treating twists as bugs (resisting role change) while missing real bugs is the classic failure. Set each twist's status as it emerges.
Implementation sequence
Order matters: control before delegation, stewards before redeployment.
Process redesign report
Generated live from the workspace state — findings, guidelines, and action plan in circulate-able form. Regenerates every time you open this tab. Export produces a self-contained HTML document; print gives PDF.