Back to whitepaper
Appendix BAction assetv0.1FDE working framework · pending field validation About 15 min + working time
FDE 10-Step Delivery Canvas
A one-page working canvas for kickoff, weekly review, stage gates, and transfer.
Updated July 19, 2026
On this page
Use: Create one canvas at kickoff. Update only evidence status, links, decisions, and next actions each week. Meetings and submitted documents are activities, not sufficient proof that a step passed.
Project header
| Field | Entry |
|---|---|
| Project | |
| Version | |
| Review date | |
| Sponsor | |
| Process owner | |
| FDE delivery lead | |
| Engineering / platform owner | |
| Eval owner | |
| Security / privacy / legal / data owners | |
| Service owner | |
| Current gate | G0 / G1 / G2 / G3 / G4 |
| Overall status | Missing / Planned / Observed / Verified / Contested |
Three persistent lines
| Line | Current objective | Baseline | Target / threshold | Evidence link | Owner | Status |
|---|---|---|---|---|---|---|
| Value | ||||||
| Reliability | ||||||
| Organization |
Ten-step worksheet
| Step | Decision to make | Required evidence | Exit condition |
|---|---|---|---|
| 1 Observe the real work | Who completes what work, when, and with which exceptions? | Current-state map, roles, real cases | Users confirm trigger, terminal state, and exceptions |
| 2 Establish the value baseline | What is the current loss and acceptable improvement? | Baseline, metric dictionary, stop conditions | Sponsor approves the value gate |
| 3 Lock ownership and decision rights | Who decides, accepts, carries risk, and operates? | Accountability charter, RACI, decision gates | Every critical decision has one accountable owner |
| 4 Validate delivery boundaries | What do data, permissions, systems, law, and procurement allow? | Data flow, permissions, risk register, approvals | No ownerless hard blocker remains |
| 5 Choose the minimum system shape | Why is this the simplest operable approach? | Option matrix, ADR, autonomy level, degradation | Major trade-offs are approved |
| 6 Build a real-sample vertical slice | Do critical assumptions survive a real path? | Runnable slice, traces, failures, comparison | Continue, redesign, or stop is decided |
| 7 Turn failure modes into eval gates | What counts as success, failure, and sufficient quality? | Task set, graders, thresholds, regression | Business and risk owners approve the gate |
| 8 Integrate the production control plane | Do identity, authorization, audit, rollback, and incident paths work? | Permissions, threat model, audit, drills | Operations and security approve controlled launch |
| 9 Prove adoption with controlled traffic | Do users complete real work and create net value? | Release, adoption, quality, cost, feedback | Scale, modify, or stop is decided |
| 10 Convert to a sustainable service | Can the team operate without the original FDE? | SLOs, continuous evals, training, transfer drill | Independent operation or retained service is explicit |
For each step, also record input readiness, accountable owner, evidence links, exit-condition review, current status, and the next action with date.
Decision log
| Date | Gate | Decision | Evidence | Decision owner | Dissent / reservation | Next review |
|---|---|---|---|---|---|---|
Open gaps
| Gap | Line / step | Risk | Owner | Due date | Mitigation / alternative | Status |
|---|---|---|---|---|---|---|
Companion chapter
Chapter 5: The 10-Step FDE Delivery Loop explains the inputs, actions, owners, evidence, exit conditions, and failure modes behind every step.