Plan: fixture run, one deliverable for the fictional bookkeeping cleanup service (U24-B)
Owner: orchestrator. Goal: produce one artifact the fictional client could receive, from the fixture brief alone, through the demonstrated workflow (plan unit, builder, verifier, handoff), so U4's page can show a real run instead of a claim about one. Owner tiers: human | runner (cheap, mechanical + verifiable) | specialist (judgment) | orchestrator (coordination).
Written 2026-09-10 at about 05:00 EDT, before any artifact existed; statuses updated as each unit closed. This whole run is a test of the packaged workflow on a fictional input (../fixture/fixture-brief.md, copied unchanged from outputs/compat/fixture-brief.md). It describes no real business, person, or number, and nothing derived from it is a Backbrief decision. Everything the run produces stays inside this fixture-run/ folder; the project's own brief, plan and log are not touched.
Where the six artifacts land:
| # | Artifact | File |
|---|---|---|
| 1 | The fictional brief, structured by /intake | 01-brief-from-intake.md (the raw input is ../fixture/fixture-brief.md) |
| 2 | The scope | this file, "Scope" below |
| 3 | The plan unit | this file, the table below |
| 4 | The produced artifact | 04-decision-memo.md |
| 5 | The verifier record | 05-verifier-record.md |
| 6 | The handoff | 06-handoff.md |
Scope
The brief asks one question (../fixture/fixture-brief.md, lines 9 to 12): whether to spend the next 90 days getting more accountant referrals or building a self-serve monthly product at $79 a month. The deliverable is one decision memo, one page, that puts those two options and "do nothing different" side by side using only the numbers the brief states (the $900 flat cleanup fee, the $250 a month afterward, six cleanups in four months, four of them from one accountant's referrals, about 15 hours a week, $500 available for ads), names the evidence each option rests on and tags it, states the risks and reversibility of each, and ends with an explicit GO or NO-GO request to the owner on one recommended path. It does not decide for the owner, does not invent market figures, and does not produce the referral plan or the product; those would be later units.
Plan unit
| ID | Unit | Owner | Depends on | Acceptance criteria | Status |
|---|---|---|---|---|---|
| F1 | Structure the fixture brief with /intake into the business-brief template, in this folder | builder (specialist) | none | 01-brief-from-intake.md follows templates/business-brief-template.md; every figure in it appears in the raw brief; unknowns are written as unknown, not filled | done 2026-09-10 (builder; every figure traced by Claude's check) |
| F2 | Decision memo: accountant referrals versus the self-serve $79 product versus no change, for the next 90 days | builder (specialist), using the decision-memo skill | F1 | 04-decision-memo.md is one page (under 700 words); three options including doing nothing; every number traces to a line of the raw brief and no number appears that the brief does not state; evidence tagged (owner-stated, assumption, unknown); risks and reversibility per option; one recommendation with its reasoning; a closing GO or NO-GO request the owner answers; no real client data; plain prose, no em dashes, American spelling | done 2026-09-10 (builder; verifier PASS, one confirmed wording fix applied) |
| F3 | Verify F2 in fresh context against F2's criteria | verifier | F2 | 05-verifier-record.md states PASS or a named reason for FAIL, produced without the builder's reasoning, and does not restate the memo's own claims about itself | done 2026-09-10 (verifier; record filed verbatim by the orchestrator, the verifier having no write tool) |
| F4 | Handoff: what the client receives | orchestrator | F3 | 06-handoff.md states what was done, points to the memo and its verifier record, and names open items and the next action | done 2026-09-10 (orchestrator) |
Every agent-produced artifact passes the verifier before it is called done.