Supervised Execution

APQC is the coordinator of governed cryptographic-estate transformation. It exists because crypto migration is a lifecycle that must be orchestrated across many components without losing governance. Supervise is the phase APQC coordinates during the cryptographic operation itself: the commissioned change runs under governance, each action consuming its reserved grant, every step attested and reversible. APQC supervises the operation — it does not perform the primitive, and the “every promise held” journal is the executor's claim, not yet an independent verdict.

The APQC invariant. APQC coordinates the execution transition; it does not produce the evidence, govern the policy, render the verification verdict, or preserve authority, and it does not compute the ML‑KEM / ML‑DSA primitive. The cryptographic surfaces perform the primitive under Agent-008 governance; the console coordinates and records each step into an Execution Journal, which becomes the sole input the independent verifier receives next.

Who owns each adjacent responsibility: the cryptographic surfaces perform ML‑KEM / ML‑DSA · Agent-008 governs the operation · H33-74 produces the portable evidence · Verification renders the independent verdict (next, in Verify) · Authority Center preserves authority · HATS monitors continuously (later, in Sustain). When to use APQC vs. another capability: use APQC to coordinate the supervised execution; use the owning flagship directly when you need that capability on its own.