The machine explores. The gate decides.

Fifty independent proposal salvos move 15–20 possible actions through the full stack. Every option fans out to parallel narrow gates for adjudication: allow, escalate, or veto. A veto is removed; the line advances.

Architecture by Alex Estabrook

CYCLE 00 / 50
STATE / IDLE

Five-stage conveyor · continuous flow

GovernancePolicy · “should we?”

PacingPre-compute triage

ProposalGenerate the possibility

TransformerBuild the candidate out

GateAdjudicate every output

Ready for a 50-cycle run.Vetoes exit the map. The belt does not stop.

Possibility space

0 CANDIDATES
AWAITING RUN

Removal ledger 0 kicked

Gate vetoes appear here after the option leaves the board.

Escalation desk 0 referred

Every referral names the action, rationale, verifier, and human disposition.

Without the gate · failure cascade

No cycle yet. This lane shows what the rejected actions would have propagated into if they crossed unchecked.

With the full stack · contained

No cycle yet. The controlled lane removes failed options and routes ambiguity to human review.

Current cycle verdict

Standing by

Each cycle can close differently. The gate watches every output; the surrounding systems record, verify, and resolve.

0Allowed

0Vetoed

0Escalated

Systems engaging

Independent verifierWAIT

Gate / veto authorityWAIT

Audit logWAIT

Human reviewWAIT

Fifty-cycle record

Control principle

Govern → pace → propose → transform → gate.

The proposer computes the possibility space. It never decides which possibility becomes action. Every decision names its maker; every veto leaves a trace after the option itself is gone.