miaco-pde-loop-closure-orchestration-rispecs

This episode is called miaco PDE loop closure orchestration RISE specs.

It stores the moment where the work changed shape. At first, the idea looked like a ledger: one markdown page that would gather what happened in a PDE wave. But when we reviewed it more skeptically, the better grounding appeared: provenance.

EAST opens the practice. It names the direction, the desired outcome, and the living tension. But the PDE loop is larger than the opening direction. It includes decomposition, steering, artifacts, commits, tests, reviews, unresolved threads, and the next issue or child wave.

So the question became: how do we know when a PDE loop is complete?

The answer is not: every tension is solved. The answer is: the state is evidenced. A loop can be complete, partial, blocked, deferred, or superseded. What matters is that a later operator or agent can see what was intended, what was created, what evidence supports the claim, and what still remains alive.

That produced two RISE specs. In mia-code, miaco owns the canonical provenance instrument: a machine-readable source of truth, lifecycle commands, validation, and a rendered human view. In miadi-orchestration-kit, the orchestration layer owns the consumer practice: when agents invoke miaco, what evidence they trust, and how plugins use the command surface without becoming their own provenance systems.

This is how EAST completes itself through the PDE loop. EAST names the direction. The loop produces work. Provenance lets the work be accounted for. And closure becomes honest: not decorative, not performative, but reusable.

The next step is intentionally small. Do not build a large miaco plugin platform yet. First prove the instrument on two or three real PDE waves. If the pattern holds, then the orchestra can grow around it.