The Panel
Five perspectives that deliberate every question.
Disagree to decide.
The Panel is the five-perspective deliberation council that anchors every Pilot5 deliberation. Five AI models, MECE-designed, with deliberately non-overlapping mandates. The Architect, the Counsel, the Strategist, the Engineer, the Contrarian — each asks a different question, and none of them is allowed to stand in for another.
Models analyse independently in the first round (Round 1 — Divergence, zero cross-consultation, audit-traceable isolation). They critique each other anonymously in the second round, knowing each other only as ANALYSIS_1 through ANALYSIS_5. The arbiter persona — selected by domain — synthesises only what survived attack.
The same five-perspective structure runs every deliberation, every domain, every region. The model behind each persona shifts at runtime (benchmark-driven selection by use case and budget), but the role contract does not.
Structure, benchmarks, operational rigor
The Architect
“What does the data actually say?”
Builds the spreadsheet. Anchors the room in numbers — revenue impact, downside cases, operational dependencies. Refuses to let the conversation drift into vibes when the data is available.
Ethics, second-order effects, reputational and legal risk
The Counsel
“What could go wrong, and for whom?”
Maps the people, contracts, regulators, and norms that the recommendation will collide with. Ethical clarity without moralising. Knows the difference between risk that should stop a decision and risk that should be managed.
Macro trends, competitive dynamics, long-horizon positioning
The Strategist
“What does this mean in context?”
Reads the market signal. Tracks where the category is moving and what staying put would imply. Long-context synthesis: the Strategist ties what's in front of the panel back to where the world is heading.
Technical feasibility, code accuracy, mathematical precision
The Engineer
“Does this actually work?”
Stress-tests the implementation. Estimates effort, latency, integration risk, and edge cases. When the recommendation has a number in it, the Engineer is the one who checked it.
Sovereign perspective, anti-convergence by mandate
The Contrarian
“What if everyone here is wrong?”
The structural counterweight. Mandated to challenge whatever the other four agree on, even when the consensus is well-evidenced. Premature agreement is a failure mode, not a success — the Contrarian is the architecture's defence against it.
How the panel runs
- Blind divergence. All five analyse the question in parallel with no cross-consultation. Architecture-level isolation, SHA-256 audit hash on each turn.
- Anonymous critique. Round 2 reshuffles the analyses as ANALYSIS_1 through ANALYSIS_5. Personas attack the weakest reasoning in the others without knowing who wrote it.
- Arbiter synthesis. A single persona — selected by domain (Architect for pricing/logistics, Engineer for code, Strategist for strategy/marketing) — produces GO / PIVOT / STOP, confidence score, and Minority Report.
- Adaptive rounds. When consensus is suspiciously high or evidence is thin, the orchestrator inserts additional rounds (Devil's Advocate, Assumption Surfacing, Focused Research) before letting synthesis run.
Continue
- How it Works → — the deliberation pipeline end-to-end, including round orchestration and arbiter selection.
- Regional Panels → — US, Global, EU, APAC, MENA panel configurations and the models that anchor each one.
- Audit Trail → — how the five-position record is preserved, including the Minority Report.
- The Three Modes → — when the full panel runs versus when a single smart-routed model is enough.