What 'Done' Means: The Cutover Gate

"Dad completes the normal Recall → play → seek → subtitle/track → full-screen workflow without returning to Movist for the bounded daily feature set."

'Done' Is a Gate, Not a Feeling

The most expensive word in software is 'done,' because everyone means something different by it. Done-when-it-compiles. Done-when-the-tests-pass. Done-when-it-looks-finished. Ashen Reel refused all of those and defined done as a specific gate made of evidence — a checklist that either passes on the real machine with real media or doesn't. Feelings don't get a vote.

The 1.0.0 cutover gate is eight concrete conditions, and every one is checkable. Build, test, bundle, sign, install, and doctor all pass on the actual Office host. The golden corpus covers the real codec, container, HDR, subtitle, and audio matrix. Every required class records its decode mode, color result, A/V sync, seek accuracy, and resume. Recall exact-open works from both local and remote browser sessions. No source file changed across the run. Every P0 case passes from the installed bundle. The visible version agrees with the product source. And the last one is the one that matters most.

Define done as evidence on the real target — and include the human acceptance test. A gate of automated checks proves the machine is happy. The final condition proves the human is: Dad completing his whole daily workflow without once reaching for Movist. Ship when the evidence AND the person both say yes.

The gate, as it actually reads — including the one item honestly left open:

A conditional gate is more honest than a faked one. Dolby Vision had no representative media anywhere in the archive, so instead of fabricating a sample to turn the checkbox green, the gate marks it conditional — untested because absent, reopening the day real media exists. A release that names its one open question is stronger than one that quietly pretends every box is checked. Done with a labeled asterisk beats fake-done with none.

Why the Human Test Is the Real One

All the automated evidence in the world is a proxy for one question: does this actually replace Movist for the person who needed it replaced? That's why the final gate item is Dad completing his normal Recall-to-fullscreen workflow without returning to the old player — and why 1.0.0 shipped only when he did. The machine checks tell you the app is capable; the human check tells you it's adopted. A tool isn't done when it works; it's done when the person it was built for stops reaching for the thing it replaced.

Code

The 1.0.0 cutover gate — done as evidence, with one honest asterisk·text

The 1.0.0 cutover gate ('done' = evidence on the real target):

  [x] build, test, bundle, sign, install, doctor all pass on the real host
  [x] golden corpus covers the codec / container / HDR / subtitle / audio matrix
  [x] every required class records decode, color, A/V sync, seek, resume
  [x] Recall exact-open works from BOTH local and remote browser sessions
  [x] no source file changed before vs after the run (the audit)
  [x] every P0 parity case passes from the INSTALLED bundle
  [x] visible version agrees with cwk-product.json
  [x] Dad completes his daily workflow WITHOUT returning to Movist

  [~] Dolby Vision: CONDITIONAL -- no representative media exists in the
      archive; the gate reopens when it does. NOT faked to green.

Exercise

Write a real definition of done for something you're building. Make every item checkable on the actual deployment target, not your dev machine — and include at least one human acceptance condition (the intended user completing the real task, the thing-being-replaced going unused). If any item is genuinely unverifiable right now, mark it conditional and say why, rather than quietly assuming it. Compare this gate to how you'd have declared 'done' by feel.

Hint

A strong gate has three properties: every item is checkable (not a vibe), the checks run on the real target (not a proxy environment), and at least one item measures human adoption (not just machine capability). And when something truly can't be tested yet, a labeled conditional beats both a fake pass and a silent omission.

What 'Done' Means: The Cutover Gate

'Done' Is a Gate, Not a Feeling

Why the Human Test Is the Real One

Code

External links

Exercise

Progress

Comments 0