Acta fori · the engineering record
E disputatione veritas— from debate, truth
AGORA was not merely designed by the method it embodies — it was built by it. This is the record: how a council of diverse minds shaped the system, the sessions that caught real flaws before they shipped, a live worked example auditing a real security project, and how to wield the boost.
The widest possible use: any team connects its own AI and convenes a forum to think harder.
AGORA is a self-hosted MCP server: any team connects its own AI over MCP and convenes a forum of diverse-model personas to debate a task — better coding, review and architecture, research, project and strategic decisions, incident analysis. Claims become verifiable predictions, the system learns from real verified outcomes, it builds memory — and deliberately does not surveil people.
The idea is simple and universal: one model's answer is fragile; truth is born in argument between different minds. AGORA is for everyone who wants to build more effectively with their own AI — and for everyone who believes that E disputatione veritas.
Any development team with its own AI; researchers; anyone who decides hard questions and believes truth comes from debate.
payneteasy connects its AI to AGORA. Their hard contour — payments, AML/KYC/PCI — we took as a stress-test: if it passes payments, it passes anything.
E disputatione veritas. Diversity preserves dissent; a verifiable outcome outweighs an opinion.
We built the council with councils. Every contested decision was deliberated before it was built.
Two independent legates debate a question; truth is settled not by rhetoric but by a deterministic probe on a real box (probe-falsify), not by a vote. A working prototype of AGORA itself.
Parallel reviewers per dimension — security · code · architecture · operations — followed by synthesis.
A four-layer control plane; inference external; a closed learning loop.
debate across families
falsify verdict, no LLM
tests / returned-broken
the dissenter rehabilitated
route by proven fact
↑ the outcome returns to the forum — the system learns on verified reality, not on approval.
The hard spec principles are honored in code and schema: verifiable>opinion (P1), relevance≠truth with two separate appraisals (P2), protected dissent (P3), exploration with a probability floor (P4), "improve the system, do not police people" (P5), canon freshness and compliance (P6–P7).
Each session caught a real defect before it was built — the method in action.
Genuine disagreement across model families, then a synthesis. Motif: "parallel or debate mode by default for engineering decisions in a payments organization?"
For parallel mode: fast independent contributions, then a merge.
Against parallel: it forfeits deep working-through; in payments, reliability outweighs speed.
For debate mode: asymmetric risk — the cost of a missed objection is many times the gain from speed.
Consensus: payment decisions carry asymmetric risk. Live disagreement: builder for speed, architect+skeptic for depth. A recommendation, with its single biggest risk named.
The product per spec: not one confident answer, but preserved disagreement across families plus a governed synthesis. All under audit, persisted in the database.
Atop a premium core, free models as extra voices — more uncorrelated families at zero cost.
GPT-4o · OpenAI • Hermes-405B · Nous • Claude-Sonnet-4.6 · Anthropic • Gemini · Google
Nemotron · Nvidia • Kimi · Moonshot • GLM · Zhipu • Dolphin · Mistral • Qwen · Alibaba
A wide panel — up to 8 voices from 9 families. Masters add diversity when they answer; if one declines (rate-limit) the round does not break — the synthesis proceeds on the active voices. "Masters under the professors": they help, they do not gate the panel. The cost is zero.
What is in service, what is proven, and the decision on the next step.
27 MCP tools, P0–P8: gateway with budgets, forum, verifiable claims, the outcome + re-appraisal loop, bandit, compliance gate, memory, aggregate observability. Network and DB isolation, secrets-in-files.
AGORA outside the PCI perimeter; the payment node untouched; the forum is decision-support, not a safety gate; only verified outcomes move the routing.
The worked audits and the usage guide now live on their own pages.
Real consilium runs on randomly-picked GitHub security repos — every project named, every git link shown, every finding highlighted. Open the combat audits →
UsusHow to call the forum over MCP, the knobs, and the discipline of using the boost only when the task needs it. Open the usage guide →