The Council of Phronesis

Earlier Review Apparatus

This structure was developed for earlier adversarial work. Current discipline is Prosoche v2: a seven-stage spine with halt-checks, steel-man requirements, and explicit abstention where evidence does not settle the question. The useful claim this apparatus demonstrated is that an intention to be fair is not a check; a structure that leaves a record is.

The Question Everyone Answers Dishonestly

Ask anyone who reasons in public how they guard against their own bias and you will get a version of the same answer: I try to consider the other side. I steel-man. I stay open. Every word of it is sincere and almost none of it is binding. An intention to be fair, held privately, is checked by nobody, halts nothing, and leaves no record of what it caught. It is the unverified claim from the inside — authority without evidence, applied to oneself.

The honest version is not a better intention. It is a structure that removes the discretion to skip it. The one described here is the Council of Phronesis — phronesis being the classical name for practical judgment under uncertainty. It is built on three branches with distinct roles, formal mechanics between them, and a list of commitments that no finding may override even when overriding them would be convenient. The structure converts "I checked my bias" from a thing claimed into a thing that leaves a record.

Why Three Branches and Not Five Reviewers

An earlier version of this review was a small set of adversarial roles run in sequence. Testing showed it was insufficient. Even when the analyst rotated faithfully through every role, specific failure classes slipped through reliably — definitional shell games inside the analyst's own prose, cross-source numerical reconciliation, scrutiny that went easy exactly where the conclusion was favorable, over-confidence about how a claim would survive transmission. The pattern was not analyst laziness. It was a coverage gap in the roster combined with the structural weakness of any review the reviewer administers to himself.

Three branches address both at once. They widen the roster so the known failure classes are each somebody's explicit job, and they make the previously implicit accountability commitments — no silent override, charitable interpretation, falsifiability, calibrated confidence — into enumerated requirements with enforcement mechanisms. The structure creates separation of powers, a written charter, checks between branches, and review of compliance.

The Legislative Branch — Seven Personas That Also Check Each Other

Seven personas make findings on the draft: the Skeptic, the Adversary, the Definitional Shell-Hunter, the Numerical Reconciler, the Steel-Manner, the Reader-of-Output, and the Cross-Examiner. Each is a fixed hostile lens with a mandate, an interrogation style, and a specific failure mode it exists to catch — the Shell-Hunter for definitional sleight in the analyst's own language, the Reconciler for numbers that do not survive cross-source contact, the Steel-Manner for the strongest opposing argument stated in a form its proponent would accept, and so on.

The mechanism that makes the Legislative branch more than a list is the cross-persona challenge protocol. Each persona, on entry, sees every prior persona's findings and must record — for each — agree, extend, challenge, or defer before adding its own. A challenge does not resolve itself into a private judgment; it puts the finding into a contested state that the Executive is then obliged to resolve in the open.

The Executive Branch — The Analyst, Who May Veto Only in Writing

The Executive is the analyst. The role cannot be delegated, because the work is published under the analyst's name and that accountability is not transferable. The Executive drafts the synthesis, presides over the personas in sequence, and resolves contested findings by choosing — with recorded reasoning that engages both sides' evidence — to adopt one, adopt the other, or synthesize.

The Executive holds a veto. Any Legislative finding can be rejected, but only by a written rejection that engages the finding's evidence base — not "I disagree," not "out of scope." A rejection the Executive cannot or will not put in writing is not a veto; it is a silent override, and silent override is the specific thing this structure exists to forbid.

The Judicial Branch — Compliance, Not Agreement

The Judicial branch reviews for compliance with the charter, which is categorically different from disagreeing with a conclusion. It does not ask is this finding right? It asks was this finding reached the way the charter requires? — was the charitable-interpretation menu actually run before the adverse reading was recorded; was each load-bearing claim checked against the analyst's own use of it; was scrutiny applied evenly rather than going soft where the conclusion was favorable. A finding can be substantively defensible and still fail compliance because of how it was produced.

Above the Judicial branch sits a final review conducted in a separate session by an external adversary that did not produce the work. It receives the scoping document, the source set, the finalized register with every judicial verdict attached, and the draft, and reviews the whole body for integrity and merit. Four conditions force escalation to mandatory human review: the external reviewer disagrees with a key judgment; it surfaces a major miss; an unresolved cross-persona challenge was not closed cleanly; or its verdict is I would not sign this as my own work.

The Bill of Rights — What No Finding May Override

The branches describe procedure. The structure's force comes from a short list of commitments that procedure may not suspend. Among them: the right against silent override — no finding may be rejected, deferred, or modified without recorded reasoning, regardless of how correct the rejection is. The right to steel-man acknowledgment — the strongest opposing argument appears in the synthesis in a form a thoughtful opponent would recognize as their own. And the commitments to charitable interpretation, to stated falsifiability, to confidence language calibrated to evidence rather than to the conclusion.

The supremacy clause is the part that matters most: a finding that violates one of these commitments fails compliance regardless of its substantive correctness. Being right is not a defense against having reached the conclusion by a route the charter forbids.

Why It Was Published

This procedure was developed for adversarial work, and it is published here because the charter is worth inspecting regardless of which review structure is applied. Find the objection a branch should have caught. If it was not recorded, weighed, and disposed of in the open, the structure was not followed.