top of page

The Office Manager and the Boardroom: How My System Vets Its Own Information

Writer: Brian Lathe
Brian Lathe
Oct 28
5 min read

Updated: Oct 30

The Office Manager and the Boardroom: How My System Vets Its Own Information

By Brian Lathe


Here is a problem nobody warns you about when you give AI agents real work: they will happily swallow anything.


Feed a typical setup a rumor, a stale price, a confident-sounding claim from a random page — it goes in, gets mixed with the good information, and comes back out later wearing a suit, presented as fact. For a one-person business making real decisions, that is not a quirk. That is a liability.


My system, SuccessBrian OS, handles incoming information the way a well-run office handles paperwork: nothing walks straight from the mail slot onto the boss's desk. It passes through an office manager first, and the big decisions go through a boardroom. Let me show you the two rooms.


Room one: the in-tray

Everything new enters through one door — I call it the Intel Bridge, but picture a mail room in-tray. Research I asked for, things my agents found, prices, claims, ideas, problems: they all land in the same tray, raw and unsorted.


Raw is the important word. A thing in the in-tray is inventory, not knowledge. It has not been checked, it has not been filed, and no agent of mine is allowed to treat it as true just because it arrived. That single rule — arrival is not belief — prevents most of the damage AI systems do to themselves.


Room two: the clerk's desk

The clerk is my office manager, and she is the hardest-working part of the system. Every item in the tray passes her desk, and she does four things with it:


1. She sorts it. Every item gets classified — what is it, where does it belong, which part of the business does it serve — with her reasons stated in plain words. A note marked by whoever dropped it in the tray is evidence to her, never the verdict.


2. She digs. If an item needs more than it brought with it — background, confirmation, the surrounding facts — she researches it, answers what the house records already settle, and files proper requests for the rest. I call this stage deepening, and it is the difference between a claim and a case.


3. She checks it against the source. This is the stage I care about most, so I will be precise: her fact-check is a fidelity check. Did the number survive copying exactly, or did it get rounded somewhere? Does the claim match what the source actually said? Is the fact inside its shelf life, or has it quietly gone stale? Anything she cannot verify does not get dropped and does not get believed — it gets flagged, in writing, on the item itself.


4. She routes it. Checked material gets filed to its proper home, turned into a work packet, or set aside with a reason. Flag first, fix second, and only fix what the evidence actually settles — that order matters, and it is written into how she works.


The clerk never gets the final say on the big questions. That is deliberate. Sorting is her genius; judgment sits in the next room.


Room three: the boardroom

Significant items — decisions, plans, anything with real consequences — go to the board as packets: organized, deepened, fact-checked files with the evidence inside. The board's first move is not to vote. Its first move is to ask questions back: what is missing, what is assumed, what would change the answer? Those questions return to the clerk, who answers what the records settle and researches the rest, and only then does the board deliberate and decide.


Decisions flow back out as actual work — tasks with owners, projects with checks — not as meeting notes that die in a drawer. And everything, the packet, the questions, the decision, stays on file. If I ever ask "why did we do it this way?", the answer exists.


The board also keeps receipts on itself. When the same kind of problem shows up a third time, the clerk does not just process the third instance — she packages the pattern and sends it up as a question about the rule itself: this keeps happening, maybe the procedure needs fixing. That is how a system improves its own office discipline instead of heroically surviving the same jam every month. My procedures are, quite literally, amended by the paperwork.


Two more clerk habits worth stealing

Facts have shelf lives, and she watches the dates. A price checked last week is a different animal from a price checked last year. Every filed item in my system carries a kind and a freshness window; when something expires, it does not silently stay "true" — it resurfaces for a recheck. And per the memory rules I run (there is an article on this blog about how the filing cabinet works), anything a living piece of my business depends on is exempt from expiring at all, while a used-and-replaced fact is archived rather than deleted. Stale is a status, not a surprise.


Contradictions get a flag, not a coin flip. Sooner or later two sources disagree — it happens every week in a real business. The clerk does not pick the one she likes, and she does not average them. She files it as a controversy, evidence on both sides, and routes it to whoever can settle it — often me, with the context attached so the question takes thirty seconds instead of an afternoon. "We don't know yet" is a perfectly good filing status. Pretending otherwise is how systems rot.


For scale, honestly stated: hundreds of items have passed through that in-tray in my shop — research, rulings, price checks, whole session reports — and the tray is the only reason the rest of the system can trust what it is standing on.


Why my fastest agent only eats cooked food

One consequence of this pipeline surprises people. Altair — the agent I chat with daily, my Senior VP — is a fast, light engine, and he keeps up with a business that generates information around the clock because he never touches the raw tray. Everything he ingests arrives pre-digested: sorted, deepened, and checked by the clerk. He is quick because his food is cooked.


Put a fast agent on raw input and you do not get speed. You get confident mistakes at scale. The pipeline is what makes the speed safe.


The honest part

I will tell you plainly where this stands in my own shop: the clerk's sorting runs every hour, the pipeline has survived — and been repaired after — real floods of incoming material, and the board's full deliberation rhythm is still the part being built out hardest. I would rather show you a working office with one room under renovation than a glossy render of a finished one. The receipts are public; that is the deal I offer on everything I coach.


If you run a business alone and AI is starting to feed you information faster than you can check it, this is the shape I recommend: one in-tray, an office manager who flags before she files, a boardroom that asks questions before it votes, and nobody — nobody — treating arrival as belief.


SuccessBrian OS is free and open, machinery included.


Get SuccessBrian OS on GitHub — free, Apache-2.0, and the office manager comes with it.


Read more from Brian Lathe on Substack


This blog is one room in a bigger house. My main writing lives on Substack - longer pieces, new posts first, always free to read: Brian Lathe on Substack.

 
 
 

Recent Posts

See All
Do You Need an Integrator If You're a Team of One?

Do You Need an Integrator If You're a Team of One?If you've read anything about EOS — Gino Wickman's Entrepreneurial Operating System, from Traction — you've met the famous pair. The Visionary is the

 
 
 

Comments


Talk to Brian

on WhatsApp

Appointment booking opens soon.

Questions about this article — or about SuccessBrian OS? Text me here.

Texting is best — please don't call. Calls are by confirmed appointment only.

Talk to Brian

Questions, or want a system like this working for your business? Message me directly.

What is SuccessBrian OS?

One system that runs a solo business while its owner lives his life: a checked second brain, a crew of AI agents, and one calendar that never forgets. The whole system is free and open.

Get new posts by email

I build this in public and post the progress. Follow along on Substack.

bottom of page