See what a readiness checklist checks
What counts as ready?
Ask what the path-to-launch checklist checks and how many gates it has. Then print every gate yourself.
What you get: the gates something has to pass before DoneEngine calls it ready, which ones decide whether it can ship, and which ones a machine checks.
Ask Quox
Section titled “Ask Quox”Name the checklist the way you would say it:
What does our path-to-launch checklist in DoneEngine actually check before something counts as ready? How many gates are on it, and what are the first few?
▤ AOCL │ L1 identity complete · allowed · 1ms
▤ AOCL │ L3 policy gate complete · proceed · 2ms
◐ DONEENGINE │ doneengine_readiness action=packs ✔ DONEENGINE │ doneengine_readiness action=packs │ 5 count, 5 packs · 2.1s
◐ QUOX │ cli ✔ QUOX │ cli │ 0 exit code, 4848 duration ms · 7.9s
⛓ AEE │ envelope opened · ops.tool · doneengine_readiness ok
⛓ AEE │ envelope opened · ops.tool · quox_cli ok
⛓ AEE │ envelope opened · stream_success
The "Path to launch" checklist (the launch-spine pack, version 1.0.0) has 10 gates. It currently covers 11 subjects. All 10 gates are inherited from the House definition of done ( house-dod ), so the pack adds none of its own. The first few, in the order the checklist lists them: 1. Has a maturity map. The subject has to have one. This is attested, meaning someone vouches for it. 2. Maturity table has at least one rated row. The map can't be empty. 3. No rows tagged Broken. This is a finish gate. 4. No rows tagged Stub. This is also a finish gate. 5. Claims live-verified, not just tested. This is another finish gate, and it's attested. The remaining five are: • Cites a test corpus • Names its own limits (a finish gate) • CLI parity mentioned (a house gate) • Running code matches the repo ( deployed_current ) • Mapped test suite passes at the current commit ( tests_pass ) Only the last two are machine-checked. deployed_current is the only gate at the "deployed" stage. The other eight are attested at the "build" stage, which means they are claims someone has to stand behind, not automated measurements. I read the pack definition, not a live score for any subject. If you want the current readiness of a particular surface against it, I can pull the estate board next.
20.1s · 2 tools · 0 approvals
quox.✔ Machine verified against the CLI on 13 Nov 2026 · test report mweavy
Quox listed the DoneEngine packs, then read the Path to launch checklist itself. It said the checklist has 10 gates, all inherited from the house definition of done, and named the first five in order, starting with “Has a maturity map”. It pointed out that only the last two gates are machine-checked and the rest are attested, meaning someone has to stand behind them. It said it read the checklist, not a live score for any subject.
Do it yourself
Section titled “Do it yourself”quox done checklist launch-spine**Path to launch checklist, [email protected].** Generated from the pack the engine judges. `finish` gates decide can-ship. Inherited from house-dod:- [ ] `has_map` Has a maturity map (attested)- [ ] `has_rows` Maturity table has at least one rated row (attested)- [ ] `no_broken` No rows tagged Broken (attested, finish)- [ ] `no_stub` No rows tagged Stub (attested, finish)- [ ] `live_verified` Claims live-verified, not just tested (attested, finish)- [ ] `cites_tests` Cites a test corpus (attested)- [ ] `names_limits` Names its own limits (attested, finish)- [ ] `cli_parity` CLI parity mentioned (house gate) (attested)- [ ] `deployed_current` Running code matches the repo (machine)- [ ] `tests_pass` Mapped test suite passes at the current commit (machine) Each line is one gate with its id and what it asks for. attested means a person vouches for it, machine means the engine checks it, and finish marks the gates that decide whether something can ship. The checklist is generated from the pack, so it never drifts from what the engine actually judges.
Add --json to get each gate’s stage as well: deployed_current is the only gate at the deployed stage.
What just happened
Section titled “What just happened”Both Quox and the command only read the checklist. To ask whether one subject passes it, run quox done check <subject> --pack launch-spine. That is advice only and never blocks.