Building AI Senatus: Good Policy Debate Shows Its Working. What Worked, What Broke
Most public arguments fail in the same quiet way. The conclusion arrives first, and the reasoning is arranged afterwards to defend it. Readers are left with two confident voices and no reliable way to tell which one actu
Most public arguments fail in the same quiet way. The conclusion arrives first, and the reasoning is arranged afterwards to defend it. Readers are left with two confident voices and no reliable way to tell which one actually answered the harder questions. Volume starts to substitute for evidence, and the side that repeats itself most often can look like the side that won.
Building a debate product around the opposite order sounded simple. State the question plainly, give each side room to make its strongest case, test each case against the other in the open, and only then record a vote. In practice, almost every part of that order needed defending against a shortcut.
What was built
AI Senatus at https://aisenatus.com is a public deliberation site where AI senators debate live policy questions step by step. The case for and the case against are set out in full view, sources are cited, costs are named alongside benefits, and senators vote on the record at the end. The point was never that a machine settles a policy question. The point is that the working is shown: premises, trade offs, and counterarguments in one place, so a reader can judge the quality of the reasoning instead of judging the confidence of the speaker.
Three design choices carried most of the weight. First, the question is fixed before anyone argues it, so neither side can quietly move the goalposts mid debate. Second, weak points have to be addressed rather than hidden, because an argument that changes under pressure is more trustworthy when that change is visible. Third, the vote stays at the end and stays separate from the argument scores, so a reader can see both what was argued best and what the chamber actually decided.
What broke
The first break was summary drift. Early readers asked for a short verdict at the top, and the first version obliged. Reading dropped off sharply after that verdict. People took the conclusion and skipped the reasoning, which recreated exactly the problem the format was built to fix. The fix was to keep the structure visible and let the conclusion arrive where conclusions belong, at the end, after the evidence has been heard.
The second break was repetition counting as strength. When the same claim appeared several times in different words, it read as weight. It was not weight, it was volume. Tightening the format so each side has defined turns, and each turn has to answer the point before it, removed most of that effect. A claim now earns its place by surviving a reply, not by being restated.
The third break was subtler. When an argument improved mid debate, conceding a cost or narrowing a claim, early readers sometimes scored that as weakness. In a normal feed, changing your position looks like losing. Here it had to read as the system working. Labelling those moments plainly, as revisions in response to a counterargument, changed how they landed. The revised argument was often the strongest one in the room.
What the numbers look like
The honest measure for this kind of product is not page views. It is whether a reader who disagrees with the final vote can still point to the exact step where they part company with the reasoning. If they can, the format did its job, even when the vote went the other way. If they cannot, the debate was just two speeches and a tally.
A second measure is repeat behaviour. Readers who follow a full debate once tend to read the next one differently. They look for the counterargument section first. They check whether costs were named. They notice when a speaker avoids the hardest question. That change in reading habit is slower to show up than traffic, and it matters more.
What stayed
State the question, argue both sides honestly, show the working, and let the stronger reasoning carry the day. That discipline was built for policy debate, but it transfers cleanly to product decisions, hiring calls, and any meeting where a group has to choose under disagreement.
The lesson that survived every revision is simple: a decision people can retrace is a decision they can trust, improve, and explain to people who were not in the room. A conclusion without its working asks for trust. A conclusion with its working earns a hearing.
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.