Skip to content
Build n Bloom

The work, as saved.

Explore the reports, proposals and plans an advisory team works with—and the workflows and agents designed to prepare them. All sixteen saved outputs use fictional material from local builds. Open one to see the work and the human decision.

16 of 16 responsibilities

All responsibilities

Evidence analyst

Turns documents and authorised interview material into observations traceable to their source.

The saved work

Northline · fictionalReport 12 · source 2DOCX

An interpretation the reviewer can challenge

The sponsor’s version uncertainty and the lead’s report of complete handovers concern distinct aspects of the process. The lead passage challenges a missing-information explanation for two cases; it does not contradict the sponsor’s experience or the distinction made in this theme. Treat its relationship as qualified rather than as an opposing account.

Evidence — 02-client-sponsor.txt: I could not tell which version the team was using.

Reason and limits: Fresh method2 run still uses the same lead quotation as both support and counter-evidence. Human review distinguishes the claim being challenged from the theme itself. This is a new run-specific judgement, not an automatic carry-over of the earlier T1 correction. Three authored accounts establish no frequency, cause or demand.

A related local example. It shows the stated part of the work, not every step in this design. Read it in saved outputs

What it works from
Case question; approved method; source versions
What it prepares
Evidence index, candidate themes and contradictions
Who keeps the decision
Evidence owner
Where its responsibility ends
Interview coding is a method-specific configuration; cannot claim representativeness or causal certainty.

These are designs, not 16 deployed agents. A saved output shows the stated local work; it does not establish an installed workflow or a separately running agent. Nothing runs on this website.