Skip to main content

Demo acceptance plan

  1. Reproduce before fixing: the old startup proof against a resting user order, the typed-order path on a real 3-member cluster, and edge-proxy/console gaps on a fresh rig. Done.
  2. Fix the rig scripts and the console presentation in this lane. Propose engine, gateway, read-model and coordinator changes to their owners (F1 and F3 to the coordinator; O1 and O2 to RI-06) instead of editing them. Done.
  3. Make readiness a function check with negative controls, run twice. Done.
  4. Write one maintained guide, with labels and known blockers first. Done.
  5. Review R1–R3 corrected. Section 4 was rerun on the integrated F1 fix (done, 2026-09-24).
  6. F3 fixed and re-judged (2026-09-24): 31/31, exit 0, twice.
  7. Next: a second person follows the guide (RI-07's definition of done).