docs / 03-one-analysis.md
One analysis
One analysis, from the question to a draft a board can read.
The workspace
Chat is on the left. The analyst steers there, and the agents report what they did. Every search and every read shows as one line, including the ones that found nothing.
The analysis is on the right: the document, the claims behind it, the sources used, notes, and a count of what is covered. Closing the chat loses nothing, because the analysis never lived in it.
Every section the method asks for is always listed. An empty one says it is empty.
The steps
The first target is the skeleton: two pages of bullets covering every section. A board already uses it to decide whether a full analysis is worth writing. It takes an analyst about two hours by hand, which gives a time to compare against.
The full draft grows from the skeleton. The approved skeleton is kept as it was when the board read it.
The sections come from a method document the agents read, not from code. The published method has five: the problem, the players, the rules of the game, the state of play, and where reform can happen. A different client can use different sections without changing any code.
The agents
| Role | Reads | Writes |
|---|---|---|
| Planner | The plan and the claims so far | What to work on next |
| Research | The registry, search, and the pages a reading model quotes | Sources it found, notes on them, claims from checked quotes, or a gap when it finds nothing |
| Analysis | Claims only | Actors, rules and disagreements, and judgements that rest on claims |
| Writing | Claims and analysis | The skeleton and the draft |
The analysis role reads claims, never documents. So it cannot form a view from a source that no claim records. This holds because it has no tool that reads a document, not because it is told not to.
Research runs as several agents in parallel, each on one part of the question. They all make claims through one step, which checks the quotes and sets the labels the same way every time.
In the first version one agent does all four jobs with every tool, so the analysis role can still read documents.
The check
In a published analysis, about one sentence in four carries an endnote. The rest connect, restate or argue. So the check does not ask for a citation on every sentence. It looks for sentences that state a fact and have no claim behind them.
Nothing is blocked. The author picks: find a source and make it a claim, mark it as their own judgement, or cut it.
The check runs on the analyst's writing too.
Where the analyst's knowledge goes
An expert knows things no open source says. When the check flags one of their sentences, they can record it as a claim from their own knowledge. It then sits in the evidence with everything else, marked as theirs.
Interview notes work the same way. A transcript is a source, and claims from it quote it. Running the same question with and without the interviews shows what the interviews added.