The Company OS
Graph engineering.
Part of the Company OS. How the knowledge core is engineered.
Some work is too wide for any single session: a rebrand touching forty files, an audit of every account kit, research across a whole market. For that, the brain stops being a writer and becomes a coordinator.
Fan out. Verify with fresh eyes. Merge one answer.
A wide job splits into parallel workers: one per file, per draft, per account. Every worker inherits the constitution before it starts, because a worker that never read the rules is a leak vector, and the guardrails have to hold at every node of the graph, not just at the top.
Then the part that separates this from just running many chats at once: every result is attacked by independent verifiers that never saw the worker’s reasoning. Different lenses rather than repeated passes: one reads for confidentiality, one for factual grounding, one for voice. A model shown its own reasoning nods along with it. Fresh context is what makes verification mean something.
The three rules that keep a fleet honest
Count the returns
Every run counts what came back against what went out. A silent failure hides easily inside a complete-looking report, and a fleet that cannot notice a missing worker will happily summarize the gap away.
Anchor on the arguable-with-nothing
Every graph terminates in a signal that cannot be argued with: a scanner’s exit code, an authority file, a diff. An agent reporting that it finished is not a signal. A deterministic check exiting clean is.
End at a human
Fleets do the breadth. People keep the judgment. Nothing a graph produces goes anywhere without a named person promoting it.
A worked example you are looking at
This site was audited under exactly this discipline. Three independent attackers went hunting: one for confidentiality leaks, one for false claims, one for rendering defects. They raised forty-two findings. Every finding was then adjudicated by a separate judge that had not seen the attacker’s reasoning, with instructions to assume the reporter was wrong. Eighteen findings died there. The ones that survived were real, and the most serious was a confidentiality disclosure that never used a forbidden word, which no keyword gate could have caught.
That is the whole argument for the pattern in one sentence: the finder’s enthusiasm and the judge’s skepticism have to live in different heads.
The account of that audit, including what it caught, is on how this site is built.