Throndar

THRONDAR Autopilot

Autopilot: bounded council runs with a signed receipt

Give the council a goal. Autopilot plans a bounded sequence of steps, runs each step as a governed council turn, verifies every output, writes a final synthesis and seals the run with an ML-DSA-87 signature receipt.

Sign in to start a run   How the council answers

What a run does

  1. Plan. Your goal (up to 2,000 characters) becomes a plan of at most 8 steps. You set the step cap and the credit budget.
  2. Execute. Each step is one council turn (81 credits). With deep verify on, the council critiques each step as a further turn (+1 turn per step).
  3. Verify. Every step’s output carries a verification flag and the reason for it.
  4. Synthesise. A final synthesis draws the steps together.
  5. Seal. The finished run is signed. The run is saved after every step, so partial progress survives a stop.

Guardrails

What the receipt proves

The run is reduced to a canonical core — the goal, a hash of each step’s output, the verification flags, the outcome and the budget — and signed with ML-DSA-87 (FIPS 204). When a deployment has its second signature leg enabled, SLH-DSA (FIPS 205) co-signs the same core.

The receipt proves origin and integrity: this run, with these outputs, was produced by THRONDAR and has not been altered. It is not a proof that the run’s conclusions are correct, and it never claims to be.

A run is marked council-grounded only when every part of it — each step, each critique and the synthesis — came from the council rather than a single-model fallback.

You can download an AI Provenance Record for a run: the evidence pack plus an EU AI Act obligation mapping, as factual evidence to file with your own documentation. It is not a declaration of conformity.

Requirements

A signed-in account with credits. Autopilot is not available anonymously, and this page is all a visitor without a session sees at this address.