Working Theory · Rachel McBride
Raw at the core, intelligence on top, the human owning both ends.
When people say "put AI at the centre", what often happens is the model's output becomes the thing everyone works from. I think that's a mistake.
The centre should be the raw record you can verify. Intelligence sits on top of that. A human owns both ends: what goes in, and what gets acted on. Here's the whole thing on one picture: three rings, and what sits inside each.
Raw data is the ground truth. Intelligence is a layer over it. The human owns both ends: curating what goes in, carrying the liability for what comes out.
The load-bearing thing. Three components, each a facet of how the human relates to the data.
Together, verified, judged and owned, they make the moat. A competitor can't copy a core that has been curated by your judgement, proven true, and accumulated under your ownership. The moat isn't a fourth ingredient. It's what the three give you.
Reads, surfaces, connects, drafts, acts. All of it over the raw core, never underneath it.
Agents are the intelligence layer in motion. They don't just read, they act. They live in the intelligence ring, operate on the verifiable core, and everything they do passes through the responsible edge. The discipline that keeps it honest: an agent can propose new raw data, but it only becomes core once the expert-led, verifiable gate admits it. An agent never silently writes unverified synthesis into the core.
Three operators, in three unrelated domains, law, manufacturing, and a relationship network, arrived at this same shape independently, without comparing notes. When serious people converge from different starting points, the shape is real. That's the evidence this is a genuine design principle of the intelligence-centred firm, not a projection onto it.
The settled question is no longer whether the core should be raw. It's how you do verifiability well: provenance (where each item came from), integrity (proof it hasn't been altered), freshness (proof it's current), admission (the standard something must meet to enter the core at all), and boundary (what should never enter a given core).
That is the piece still being written. Everyone building this way needs it, and nobody has set it down yet. If it's your discipline, I'd like to hear how you'd draw the line.
See it in practice: Where the tool stops, building Mappa.
v1.3 · Opening rewritten in plain English (what people get wrong about "AI at the centre," then the fix in three plain sentences); diagram, three-part structure and keyline kept. v1.2 · Trimmed a restated closer in the agents section (kept "never silently writes unverified synthesis," cut the line that repeated it). v1.1 · Linked to "Where the tool stops" (the principle in practice). v1.0 · First public statement of the principle, adapted from the working note. The meaning is public; the operator specifics and the candid build audit stay private. The open edge (how to do "verifiable" well) is named, not solved.