Throndar

The council

One answer from a thirteen-seat council.

Throndar answers with a governed council of thirteen seats. Your prompt goes to the council's configured seats, and one seat cross-examines and fuses their drafts: a council answer is normally synthesised from several seats, and when only one seat answered, or the synthesis failed, the signed receipt records it (council-grounded: false). In the signed-in console, an answer whose model plane states how it was made is then post-quantum signed, so you can verify it yourself. Don't trust it — check it.

The thirteen seats

These are the seats the model plane defines. Two of them run models from OpenAI: OpenAI's own seat and the open-weights gpt-oss-120b seat.

The status page asks every seat a one-word question, at most once every five minutes, and shows the latest probe: when it ran, which seats answered and, on wider screens, the model each one ran. Live council status →

Step 1

Route

Your prompt goes to every configured seat of the council — the same prompt to each, or to the first three on a fast Live-Voice turn. Nothing splits it up or picks seats per part.

Step 2

Deliberate

The seats answer in parallel, each without seeing the others' drafts. A seat that has not answered within the draft window (at most 30 seconds) is dropped.

Step 3

Synthesize

One seat — the first configured one — cross-examines the drafts and fuses them into one answer. It is instructed to keep what they agree on, resolve disagreements on the merits, drop what is unsupported, and say so when a conflict cannot be resolved. If only one seat answers, or the fusion fails, the receipt says so.

Step 4

Govern

The answer's governance flag records how it was made — council_synthesised, synthesis_fallback or single_model — and the receipt signs that flag with the answer. No separate check grades or approves an answer before it ships.

Step 5

Sign

A council answer streamed to the signed-in console gets an ML-DSA-87 (FIPS 204) receipt when the model plane states how the answer was made, and the model-plane bridge co-signs the answers it produces with Falcon-1024 (Round 3; not FN-DSA); a saved answer keeps that co-signature only if it verified. The free demo and the non-streaming API sign no receipt.

Step 6

Verify

Anyone holding a signed answer can confirm, in their own browser and offline, that the exact text came from Throndar and wasn't altered — against the published public keys, with no trust in Throndar's servers at check time. A signature attests origin and integrity, not that the answer is correct.

Why thirteen seats, mostly from different labs?

A single model has a single set of blind spots — the same training, the same failure modes. A council of models from different labs gives the fusing seat independently written drafts to cross-examine: an error one model makes is one the others can catch. It is a governance and reliability design, not a benchmark score — and it is why a signed answer carries a record of how it was made instead of a promise.

Take your seat

Start free, with no card: 200 starter credits, and up to 5 free council answers a day behind a verified email. Ask in the signed-in console, then verify a signed answer's post-quantum receipt yourself, in your own browser.

Start free →   Verify an answer

Skeptical? Try to fake a THRONDAR answer →

Learn more

Verification attests an answer's origin and integrity — it came from Throndar, unaltered — not the factual accuracy of the answer. Algorithm names denote the public standards the primitives are based on (ML-DSA-87 / FIPS 204; SLH-DSA-SHA2-256f / FIPS 205, on the model-plane bridge's answers and, when that leg is enabled, on the web layer's receipts; Falcon-1024 / Falcon Round 3, not FN-DSA), not a FIPS-140 / CMVP validation. Cryptography (CBOM) · Developer API · EU AI Act