Skip to content
Rocky G
Go back

Seven AIs Walk Into an Argument

Table of contents

Open Table of contents

The problem with one opinion

Ask an LLM “will property prices in Kokapet grow?” and it will answer. Confidently. Beautifully. And you have no idea what that answer is worth.

That was the problem behind Kshetra, a tool I built for real-estate brokers in Hyderabad. A broker’s job is to stand in front of a buyer and say, this locality will grow, here is why. If the “why” is “an AI told me,” the broker looks like a fool. The forecast needs to survive questioning.

Humans solved this problem long ago. It is called a debate.

The design: a panel, not an oracle

Kshetra runs seven AI personas as independent, parallel Claude calls. Each one receives the same folder of evidence about a locality: government registration prices, RERA filings, infrastructure news, listing-portal trends. Each reads it through a different pair of eyes.

An infrastructure optimist. A data skeptic. A builder-risk hawk. A jobs-and-migration analyst. And so on. Seven specialists, each paid to care about exactly one thing, and each nothing more than the same base model steered by a different system prompt and a different mandate for which evidence to trust. That is the cheap, controllable way to buy diversity: not seven models, but one model wearing seven briefs.

EVIDENCE govt prices · RERA · news infra optimist data skeptic builder-risk hawk jobs analyst + 3 more, in parallel JUDGE synthesizes, does not vote VERDICT bold number confidence range evidence trail dissent log

Independence is the load-bearing word. The calls run in parallel and never see each other, so no persona anchors on another’s answer and their errors do not line up. It is the same reason an ensemble beats its average member: uncorrelated mistakes cancel, correlated ones compound. Run the seven in sequence, each reading the last, and you would not get a panel. You would get an echo.

IN SEQUENCE A: growth B reads A: agrees C reads B: agrees D: agrees. echo. mistakes line up IN PARALLEL same evidence A: growth B: doubts the data C: builder risk D: growth, slower mistakes cancel

Then a Judge agent reads all seven arguments and writes the verdict: a bold number, a confidence range, the evidence trail behind it, and the part I am proudest of, a dissent log.

Architecturally this is a scatter-gather. The evidence is scattered to seven workers that run concurrently and in isolation, and their outputs are gathered by a single reducer. It is map-reduce, with two twists that matter: the mappers are opinionated on purpose, each carrying a different bias so the map step produces diversity instead of seven copies of one answer, and the reducer is paid to preserve disagreement rather than average it away. Get either twist wrong and the architecture collapses back into an expensive way to run one model.

The dissent log is the product

Most AI products hide disagreement. Kshetra publishes it.

If the data skeptic thinks the listing-portal prices are inflated and says so, that objection ships with the forecast. The broker sees “6 of 7 panelists expect growth; the skeptic flags that verified registration data lags the hype by two quarters.”

THE VERDICT · WHAT THE BROKER SEES 6 of 7 panelists expect growth the skeptic confidence range: printed evidence trail: attached DISSENT LOG · SHIPS WITH THE FORECAST "Verified registration data lags the hype by two quarters."

Think about what that does for trust. A forecast with a printed objection is more believable than a forecast with none, because it proves somebody looked for problems. It is the same reason a good engineering design review includes the rejected alternatives.

One model cannot give you real dissent. Sample it twice and you get two draws from the same distribution, correlated by construction. It agrees with itself because it is itself. Genuine disagreement has to be engineered: separate calls with separate mandates and separate incentives, so the conflict on the page is real rather than performed.

Evidence is tagged, not trusted

The second honesty rule: not all data is equal, and the system says so out loud. Every input carries a provenance tag. Government registration prices and consultancy reports are tagged verified. Listing-portal numbers and broker blogs are tagged directional. The personas see the tags, the judge weights each argument by them, and the final pitch prints them, so a claim that leans on a broker blog can never quietly borrow the authority of a registered sale.

govt registrations RERA reports VERIFIED listing portals broker blogs DIRECTIONAL PANEL + JUDGE weighs every claim by tag THE PITCH every claim prints its tag verified directional

Three localities went through the engine as pilots, chosen as a deliberate spectrum: an established corridor with clean data, an emerging jobs-led corridor with noisy data, and a purely speculative one. This was not a test of whether the forecasts come true, which nobody can know for years. It was a test of calibration, which you can check today: does the system’s confidence track the quality of the evidence rather than the volume of the hype? It does. The speculative corridor gets a wide range and a low-confidence stamp even when every headline is euphoric, and the established corridor gets a tight range because the data earns it.

That distinction is the honest answer to the obvious objection. For a forecast you cannot verify for years, the thing you can actually evaluate now is whether the system is appropriately uncertain when the data is thin. Long-horizon real-estate prediction is hard, and anyone who hands you a single number without a range is selling something.

What this taught me about agents

Building this changed how I think about “multi-agent” systems, which in 2026 is a phrase attached to a lot of demos.

Multi-agent is not a performance trick. Because the seven run in parallel, the latency cost is only the slowest persona plus the judge, not seven times a single call, but the token cost is genuinely sevenfold. You pay that money for exactly one thing: structured disagreement. If your agents do not have genuinely different jobs and genuinely different incentives, you do not have a panel. You have one agent with extra steps and a bigger bill.

The judge matters more than the panel. Synthesis is the hard part: weighting a verified-data argument above a vibes argument, and preserving the dissent instead of averaging it away. A judge that simply mean-pools the seven opinions destroys the exact variance the panel was built to produce. The value lives in the disagreement, so the one thing the judge must never do is smooth it out.

And the same principle showed up later in my healthcare work: Caira, my WhatsApp clinic receptionist, refuses to answer outside its verified facts. Different domain, same belief. An AI system earns trust by showing its evidence and admitting its doubts, not by sounding sure.

Seven AIs walk into an argument. That is not the setup of a joke. It is the closest thing I have found to honesty at inference time.


Share this post on:

Previous Post
The Project Where I Banned AI
Next Post
What First-Time Users Taught Me About Building AI Products