ENGINEERING FIELD NOTES
From independent views to a decision
The deliberation workflow and the work needed to make it dependable.
Public brief · September 2026 · Product capabilities remain in development.
01 / Submission & admission
Start with a bounded question.
A commission defines the question, evidence, constraints and expected result. Admission checks whether the needed capacity and conditions exist. A queued request is not a running deliberation.
Continue ↓02 / Dispatch & discussion
Independent perspectives need real differences.
Seats receive the problem and produce claims and critiques across rounds. Several seats using the same model do not automatically create independent viewpoints. Time, context and resource limits are part of the design.
Continue ↓03 / Rapporteur & dossier
Preserve the disagreement as well as the answer.
A rapporteur brings the reasoning into a dossier: claims, evidence, tensions and unresolved points. A finished dossier is an output of deliberation, not necessarily an accepted decision or an implemented change.
Continue ↓04 / Adjudication & receipt
Judgment needs an accountable owner.
The designated adjudicator evaluates the dossier and records a verdict with provenance. Local models can contribute analysis; consequential implementation and release decisions retain a responsible frontier or human review. The frontier provider is the user’s choice.
Continue ↓05 / Disposition & feedback
The conclusion has to go somewhere.
A verdict should be adopted, rejected with a reason, or filed as a specific unresolved item. Execution and verification follow through their own controls. Failures feed the repair loop; operational retries must not erase the underlying evidence.
Continue ↓06 / Success criteria
Useful work, not just a completed run.
Evaluate valuable content, adjudication, genuine divergence, faithful citations, honest refusal, a recorded disposition, time to verdict and cost per useful output. Finding nothing worth adding can be a useful result.
Continue ↓07 / Development status
Still being made dependable.
The August 2026 review documented reliability and completion-reporting gaps. This brief explains the workflow and criteria, not a claim that every stage is fully reliable today. Agent and deliberation capabilities are planned extensions of the Core suite.
Discuss the work ↗