The standard of care for AI decisions A half-day workshop
for CTOs · CPOs · heads of engineering

Half a day in the room.
Your Automation Style Guide
in hand.

Product, engineering, and risk each own a piece of how your AI decides — and rarely settle it in one place. In a single session, they leave with one standard they all signed.

Book a half-day workshop → Explore the Standard →
Five functions · one roomAligning
Engineeringsets the threshold.
Productowns the funnel.
Riskcarries the exposure.
Legalweighs what’s defensible.
Supportanswers the person on the line.
Agreed, in half a dayOne Automation Style Guide — signed by all five.
Why this one’s missing

The framework you're missing.

A style guide for your code, a design system for your UI, brand guidelines for your voice. For the decisions your AI makes, the shelf is empty — until your team writes the one that belongs there.

Your standards shelf
Engineering
Style Guide
Two-space indent
No default exports
Errors, never silent
In place
Product & Design
Design System
Eight-point grid
One accent colour
AA contrast, always
In place
Marketing
Brand Guidelines
Plain words
No jargon
One voice
In place
UnwrittenFor the decisions
your AI makes
EngineeringProductRisk
Automation Style Guideyour team's, in its own words
iCompetence — the bar it must clear
iiCandor — what the person is told
iiiRecourse — a human back in the loop
ivNon-abandonment — who watches it, after
Written · same day
Already agreed
One reference the whole team agreed to, in the room — so you can keep coming back to it, together, long after the day ends.
Written in half a day
The workshop runs the room. Your team writes the guide.
What alignment quietly buys you

An aligned team is an aware team.

Decisions defended one thread at a time, again and again.
becomes
Written once — and pointed to, not re-argued.
"Who actually owns this?" asked after something breaks.
becomes
A named owner, agreed before it ships.
A sharp turn that scatters everyone in different directions.
becomes
A team that can take the turn together, eyes open.
A client or hire asking "how do you decide?" — and a scramble.
becomes
A clear answer you're glad to be asked.
What it's quietly worth

A few ways alignment propels your team forward.

What gets easier the day your team is finally reading from the same page.

Friday, 4:51pm

An edge case nobody's seen lands in the queue. Nobody calls a meeting — the answer's already written down.

For your team's Friday nights
A new hire's first week

They learn how you handle the hard calls from one page — not three months spelunking old Slack threads.

For the people you hire
On the sales call

"So how does your AI actually decide?" You send a link — not a nervous follow-up email.

For the clients sizing you up
When the road bends

An aligned team is an aware team. It can take a sharp turn without spinning out.

For whatever comes next
The workshop · half day

Written in half a day. In one room.

Not a policy handed down from one corner. Brand, product, risk, and engineering at one table — leaving with a guide they all signed.

First half

Name the duties & map your decisions

Agree the bar to clear, what the person's told, the way back to a human, who watches it after — then pull the calls your systems make onto the table, where every function sees them at once.

Second half

Write & share

Draft your Automation Style Guide in your own words, owned across functions — and share it so no one re-litigates it later.

See how the day runs → Refundable deposit holds your date
EngineeringProductRisk
Automation Style Guideyour team's, in its own words
iCompetence — the bar it must clear
iiCandor — what the person is told
iiiRecourse — a human back in the loop
ivNon-abandonment — who watches it, after
Written · same day

What you leave holding at the end.

One more way in

The idea that started Soma.

The founding note · free to read

You automated the decision. You did not automate away the duty of care.

Long before machines, anyone whose work could alter a life was held to a standard. The deciding moved to a model; the duty didn't disappear — it landed on no one. The note that started Soma.

Read the note →

Build the one framework
your team will thank you for.

Half a day in the room. Your team's Automation Style Guide in hand by the end of it.

Book a workshop →

Refundable deposit, or a 20-minute call first — no pressure