This is the life of one job.

A single prompt births a job. It laps the OPEVC ring — observe, plan, execute, verify, condense — can spawn follow-up work and wait on dependencies, and only a [JOB-COMPLETE] answer lets it leave. The job you picture as one thing is really one ID scattered across many plugin files; each colored lane is a different owner.

1. 1Follow the numbered ring — that is the reading order through the OPEVC cycle.
2. 2Color = data owner. Solid arrows are code-enforced gates; dashed arrows are coaching or permission.
3. 3Click a glowing room (Birth, Spawn, the Stage decision…) to step inside its sub-flow.
4. 4A ⚠ badge marks where the essays and the live prototype disagree — click it for both sides.

One job. One ID. Many lanes.

Explore the journey →