# Example Stream Implementation Loop

Dirtyloop version: `2`

Execution profile: `adaptive`

Canonical tracker: Beads epic `example-epic`

Accepted plan: `PLAN.md`

Harness binding: `runtime/binding.json`

Pi adapter policy when present: `runtime/adapter.json`

## Goal

Deliver a small end-to-end capability, verify it independently, then integrate it without prescribing the implementation topology in advance.

## Control-Plane Invariants

- Beads owns state and dependencies.
- Each phase has an independently verifiable outcome.
- Each selected phase or qualified tracer-bullet Beads leaf must report `ready` from the execution-readiness audit before mutation; leaf projections preserve hashes for the shared authored phase and canonical issue.
- The orchestrator records an orchestration brief before broad work.
- Adaptive ownership, model, effort, helper missions, and concurrency are selected at run time.
- Implementation and review strongly encourage useful helper missions, with at most 20 per stage and active concurrency bounded by configured/runtime capacity.
- One actor owns each mutable checkout.
- Review and CI resolve before phase completion.

## Phase Ledger

| Beads Issue | Phase | Outcome | Phase Doc | Depends On | Status |
|---|---|---|---|---|---|
| `example-1` | Foundation | A verified vertical slice works locally | `01-foundation.md` | none | ready |
| `example-2` | Integration | The slice is integrated and operationally verified | `02-integration.md` | `example-1` | blocked |