SYSTEM 02 · COORDINATION
Active development

One source of truth. Nothing marked done on a claim.

OCE keeps a set of independent services acting like one coherent system. Every piece of state has exactly one place it lives, and every change to it passes through the same verification loop before anyone, human or agent, is allowed to call it finished.

WHY IT EXISTS

Self-reported "done" isn't done.

Self-reported completion is a conflict of interest by design. The same layer that did the work is the one vouching for it. OCE's entire coordination model exists to remove that conflict structurally: state changes are proposed, then checked against real terminal output by someone else, then written, never the other way around.

1. Propose change proposed 2. Evidence output attached 3. Verify checked by hand 4. Commit written once
WHAT IT DOES DAY TO DAY

Coordination, not just monitoring.

State of record

A single Postgres-backed store that every connected service reads and writes against. No service keeps its own silent copy of the truth.

Change proposals

State changes arrive as proposals with attached evidence, not as direct writes, so a bad claim never reaches the record unexamined.

Operator console

A Vite-built console gives a human a live, readable view of exactly what changed, when, and on what evidence.

Audit trail

Every accepted change keeps its supporting evidence attached, so the reasoning behind a decision stays visible later, not just the outcome.

Want the full story behind why OCE's implementation loop looks different from the other two?