Moes

moes is the final hardening review for a functionally complete change. It takes a change that has already passed through implementation and QA and decides whether it is ready to ship.

It is a self-contained review operating system: it carries its own instructions for every phase, builds shared evidence artifacts up front, routes scrutiny by risk, and produces a verdict from explicit verification and verified findings. moes stays artifact-driven rather than phase-local and narrative-first.

The pipeline is ordered so that code-modifying phases run first against a known-good baseline, and verification + sign-off run last — you never declare something shippable that you changed after you last confirmed it works.

When NOT to Use