project / code
Council
Council turns disputed questions into public records that can be sourced, inspected, and challenged. Give it a claim, forecast, ranking, link, post, or argument and it produces a record containing the answer, evidence, model votes, dissent, limitations, challenges, and version history.
The idea is not "chat with several models." It is closer to a public docket for AI-mediated judgment. The first read should be decisive, but the record underneath should stay inspectable and movable when better evidence arrives.
What It Does
Council turns broad input into a claim verdict, forecast, comparison, ranking, or clarification when the question is too vague. Completed runs become public records instead of disappearing into a chat history.
The answer comes first. Underneath it are the confidence, council split, source status, strongest support and objection, main crux, challenge activity, and the details of the run.
Why It Exists
I am interested in AI interfaces that produce artifacts people can argue with. A raw model answer disappears into the chat scroll. A Council Record is meant to sit in public: sourced, versioned, challengeable, and clear about where the judgment could move.
The product tension is the fun part. It needs to feel calm and authoritative without pretending to be an oracle. It should help disagreement become more inspectable: not by forcing consensus, but by preserving the evidence, dissent, and update path in the same artifact.
The Protocol Surface
Council Protocol v1.5 is a working local vertical slice. It includes the filing and confirmation flow, live and replayable Floor views, settled Records, an archive, challenges, reruns, version history, evidence panels, and SQLite persistence. Vitest and Playwright cover the core flows, and no-key fallbacks keep local development usable.
The Floor view is where the record forms: model roles, transcript events, observer notes, source checks, provisional record fields, and final synthesis. The goal is for the process to be visible enough that the answer does not feel like a black box, while still ending in something someone can actually read.
