Not everything Fusion produces is code. Runs also produce plans, specs, and design decisions, and those cannot pass a test suite because there is nothing to execute yet. The honest move is not to pretend otherwise; it is to say precisely how much proof stands behind each artifact.
Two receipts, one ladder
Fusion's receipts sit on a ladder of commitment:
- An Accepted Receipt covers planning-grade work: the artifact met its review criteria, the right people signed off, and the decision is recorded. No execution gate ran, because none could.
- A Verified Receipt covers build and review work: an objective gate executed, and every hard criterion of the Definition of Good passed.
The pillar decides the ceiling. Planning work tops out at accepted no matter how good it is; build work that wants to claim verified must earn it through the gate. A system that let a beautifully formatted plan call itself "verified" would be counterfeiting its own currency.
Why bother receipting plans at all
Because the plan is where the expensive mistakes are cheapest to catch. An Accepted Receipt on a plan records three things that evaporate otherwise: which version of the plan was agreed, which criteria it was judged against, and who accepted it. Six weeks later, when the build diverges from someone's memory of the plan, the receipt settles the argument in seconds.
It also makes the handoff explicit. A build run can require an accepted plan as its input, which means "we started building before we agreed on the plan" stops being a thing that happens silently.
The quiet rule
One vocabulary, strictly kept: accepted means reviewed and signed off, verified means executed and proven, and no artifact gets to borrow the stronger word. The ladder only works because nobody is allowed to skip rungs.
Source ledger
- Fusion planning model, sections 0, 3, and 4.
- Traceable output bundle specification, section 6.
- Fusion MVP PRD, FR-31a.