brain

At your side · by thecognitivelab

The senior colleague
you do not have.

You are the person the hard calls land on, and there is nobody at your level to think them through with. Pick the empty chair — engineering, design, finance. A specialist argues the call with you, then does the work.

Built for one person.

Not for teams, not for enterprises. For the individual contributor whose scope outgrew their headcount — and who is still expected to be right.

You own more than you can cover

Staff and principal engineers. Senior PMs with no research function. The only designer. The one person accountable for a domain that used to have a department.

No peer to argue with

Seniority removes the person who used to check your reasoning. A general assistant agrees with you by construction, which is the opposite of what a decision needs.

Depth you cannot buy in

A fractional specialist costs thousands a month and arrives without your context. A consultant leaves with what they learned. A hire has been the only way to buy the judgement.

The market split,
and left a gap.

On one side, expert clones that hold an opinion and cannot do anything. On the other, AI workers that do things with nobody’s judgement behind them.

No hands
With hands
No named judgement
Assistant personas, custom GPTs
Generic “AI workforce” agents
Named judgement
Expert clones that only talk
brain — alone here

One building block.

A synthetic specialist with three properties. Everything else — war room, team, duty roster, ritual — is a composition of these.

An opinion with a name

Not “act as”. A specialist with named criteria and a verifiable body of work behind it. Which means you can argue with it, and it can be wrong in a way you can check.

It sees your actual work

Connected to the real material — repository, documents, metrics — rather than to whatever you remembered to paste. The difference between an opinion about software and an opinion about your codebase.

It produces the thing

Deliverables with a defined shape — the brand, the written opinion, the decision memo — not a transcript you have to turn into work yourself afterwards.

A room you carry
in your pocket.

A room, not a chatbox

Open a war room for a decision and the relevant specialists are convened around it, disagreeing where they should. Hand over a domain you own but cannot watch, and it stays theirs: monitored, reported on, brought back when something moves.

Dissent is preserved rather than smoothed into consensus — the minority position is the part you will want back in six months, when the decision is being questioned.

Mobile first, on purpose

The calls that need a senior colleague rarely wait for you to be at a desk. They land between meetings, in a car, the night before. So the room is designed for the phone first, and the desk inherits it — not the other way round.

Today it runs in the browser. A native app is being built. When it ships, this is where it will say so.

The ladder of access.

What separates a specialist from a prompt is how much of your world it can reach. We climb it deliberately — depth in a few chairs beats breadth across a hundred.

0

Pretends

“Act as a head of engineering.” The baseline everyone already has.

baseline
1

Knows what it knows

Its own retrieval over curated sources — criteria that are real and traceable, not improvised.

built
2

Sees your work

The context of your editor and repository, over MCP. It is the rung we climb next, and it is not climbed yet.

next
3

Remembers what was decided

Append-only institutional memory, dissent included, so a decision survives the meeting that made it.

in progress
4

Watches without being called

Standing credentials, a watch on a domain, a cadence. The opinion that arrives before you asked.

later
5

Acts in your systems

The pull request, the document, the memo — behind evaluation gates, because a bad recurring opinion costs more than ten bad chats.

horizon

The people you would ask,
if you had them.

Start with the one specialist whose absence costs you most. When that one is earning its keep, add the next. You are not deploying a platform — you are adding a person at a time.

War room

The specialists a decision needs, convened around it, arguing it out while you are still deciding.

Team

Specialists grouped by domain, so an area you own has more than you behind it.

On duty

A standing mission on a domain you cannot watch — reporting to you, not waiting to be asked.

Ritual

The same thing on a cadence, so the watching survives the week you have no time for it.

Which call are you making alone?