ORACLE COUNCIL

Abstract

The oracle council is the review fleet the judge panel draws on: a roster of models, mostly running locally on my own hardware, dispatched against work that needs adversarial verification rather than agreement. Reviews are routed by lens, so a compliance question and a correctness question do not go to the same readers. Dispatch is serialized behind a hardware preflight, because loading several large local models at once is how you take the machine down, and a refused preflight defers the review instead of quietly approving it. Per-model health is tracked over time, so a degrading model cannot keep casting votes nobody notices are noise.

Provenance

Came out of a failure mode nobody advertises: when the same model writes the code and reviews the code, it approves its own blind spots with total confidence. A reviewer has to be able to disagree, which means it has to be a different mind.

Declassified

The reason it is local-first is not cost, it is independence: a review fleet that runs on someone else's inference has correlated failure with everything else in the stack. Running it on my own hardware means the reviewers fail differently from the thing they are reviewing, which is the entire point of a second opinion. It also forces an unglamorous discipline. Serial dispatch, load gates, and refusing to run are the parts that came from an actual crash, not from a design document. The roster, the routing taxonomy, and the thresholds stay private.

Also in FORGE

• AARIA The orchestrator. Plan first, route always.
• SF TEAM A senior delivery team, expressed as agents.
• SYNARK The flight panel. What the factory is actually doing.