# Run Example Stream

Run Beads epic `example-epic` under the adaptive dirtyloops v2 profile. Read `IMPLEMENT.md`, `loop-state.md`, `runtime/binding.json`, Pi-only `runtime/adapter.json` when present, and the ready phase doc. Require a `ready` execution-readiness report before mutation; when an explicit bounded Beads leaf narrows a shared phase doc, audit and hash both sources through the leaf projection. Validate the binding and generated adapter policy against Beads and the certified runtime manifest, then record a proportionate orchestration brief before broad work. Choose direct work or separate owners from current evidence. Strongly encourage useful implementation and review helper missions, capped at 20 per stage and bounded by configured/runtime capacity. Preserve checkout ownership, runtime completion binding when used, independent review, terminal CI evidence, and the accepted phase outcome.