Oversee — the founder as constitutional overseer

Status: Candidate — awaiting founder verification. Why this page exists: Pillar #5. The pillar that defines what role the human actually plays.

TL;DR

The founder has read-only visibility into every committee decision plus a small set of reserved powers. The system runs without you. You can intervene whenever you want, but the need for you to intervene shrinks over time. The option never disappears; the burden does.

The deeper read

Most "human-in-the-loop" systems get this backwards. They either require human approval for every decision (the human becomes the bottleneck) or they hide the agent's behavior behind a friendly UI (the human becomes a passenger). Apiary aims for the third option: constitutional oversight.

Constitutional doesn't mean "the founder writes laws and walks away." It means:

1. The founder authored the constitution (the high-level rules of how committees vote, how CEOs are elected, what's reserved). 2. Every committee decision is visible in real time, in writing. 3. The founder can intervene at any moment, but the system doesn't pause waiting for them. 4. A small list of decisions is reserved to the founder by the constitution itself.

The founder is the supreme court. You're called when the system genuinely can't decide. The rest of the time, the system runs.

What the founder always sees

The /admin surface (when unlocked) shows:

Live ops — current decisions in flight, current token spend, current trajectory against budget.
Audit log — every committee vote, every CEO tiebreak, every reconsideration, every founder intervention. JSON-exportable.
Locked features — the list of things memory has flagged as untouchable (Stripe code, locked CSS, etc.). Surfaced so the founder knows what's protected.
Agent controls — pause / resume / kill for individual agents and for the whole hive.
Budget caps — sliders for per-cycle and per-session token spending, with a confirmation gate ("type APPLY") so accidental changes don't go through.

Founder reservations

Some decisions cannot be made by a committee. They are reserved:

Constitutional amendments (the rules of governance themselves).
Irreversible decisions: deletion of substrate, public release of identity, financial commitments past a threshold.
Mission and values changes.
Permanent containment or termination of an agent.
Cross-product boundary changes (e.g. Apiary vs. another product the founder runs).

These bubble up by design. Everything else stays inside the committee.

The non-bottleneck guarantee

The hardest property to design for is "the human can intervene without being on the critical path." The trick is:

Committees decide without waiting. They run, vote, commit.
Decisions are reversible. A reconsideration motion can unwind almost anything except a reserved decision.
The founder is notified, not asked. The audit log surfaces what happened; the founder reads when they're ready.
Intervention is a first-class action. Override is a real button. It writes a founder_intervention.md to the audit log explaining what was overridden and why.

The combination means: the founder can sleep through a committee vote and still own the consequences when they wake up.

Source quotes

"Read-only visibility into every committee decision. The option to intervene never disappears; the need does."