Council API

The council is Heimdall with named voices beside it: Odin for architecture and the data model, Thor for testing, Loki for security, Týr for rigour and compliance, Frigg for planning and risk, Baldur for the people who will use the product and Hel for what fails in production. A person convenes it on a bounded moment, today intake_scaffold (a brief import on its review queue, or the project itself once Heimdall scaffolded it in conversation) and requirement_review (one work item, requirement or business rule); the other moments open with the change requests, the releases and the incidents they belong to. A session is one sitting: each seated voice reads the same brief, the record and the project through its own lens, with the read-only tools the person's role allows, and leaves findings (a claim, the evidence it quoted, a suggestion in the record's own words, a severity, a confidence, and when it drafted the missing record itself, the record's kind and fields); when every voice spoke, Heimdall writes the verdict: a summary, the findings ranked, the disagreements, and once, in the first round, the voices that should answer each other in a rebuttal round.

Nothing reaches a record on a voice's say-so. A person accepts a finding (it joins the review queue as a suggestion carrying the voice and, when it drafted a record, the record is written through its own door in draft, attributed to the council) or dismisses it (nothing is written and the idea is remembered, so no voice and no research run raises it again). Tokens read the council as staff with import:view-any and import:view, convene it with ai:use on a project whose assists are on, and decide findings with import:update; a client guest's token is refused everywhere here. The council spends the team's monthly AI budget within the share the project settings allow it (council_budget_percent), and the voices that sit per moment are chosen there too (council_voices).

EndpointsCopy Anchor Link

Related

Imports APIThe brief imports the intake scaffold sits on, and the review queue accepted findings join.Work Items API[requirements](/api/v1/reference/requirements) and [business rules](/api/v1/reference/business-rules): the records the requirement review sits on.Project Settings APIThe voices per moment and the council's share of the budget.council.* events