Talk it through with Aurelius
Library›Aurelius›The problem
Aurelius · Work & Leadership
Knowledge + Guidance

We ship models but don't know how to make them safe. Now what?

You ship because the deadline is real and the danger is abstract. Everyone on the pod agrees safety matters. That is exactly why no one is responsible for it. This is not a technical gap. It is a structural one — you built a team, not an owner. You already know more than you act on. You know what red-teaming is. You know what an eval set is for. What you lack is not the knowledge. It is the nerve to let that knowledge slow the ship date, and the clarity of who, by name, is allowed to say no. What follows will not make your pod expert in alignment research by evening. It will make you stop pretending vagueness is a plan.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
The pod likely knows the relevant practices already; what's missing is ownership, nerve, and the habit of acting on knowledge before a deadline — a coaching problem more than an information gap.
How the two dials adapt to you →
What’s really going on

Safety is not a feeling you arrive at. It is a set of checks, owned by a named person, performed before release — not after. You already have most of the knowledge you need. Choose who owns safety this week. Choose what gets checked. Everything else is noise.

🔒 What you’ll build togetherUnlock by starting
A moveName one person on the pod who owns safety for this release — not 'the team,' a person, by name.
A moveBefore the next ship date, write down the three specific ways this model could hurt someone. No vague words.
A moveSet one check that must pass before release, and give it real power to delay the date.
A moveRun the worst output you can imagine through the model together, before a stranger finds it first.
A moveAsk the pod out loud: who here would say no to shipping — and would the rest of us actually listen?
PractiseThe Named Owner · a Pod of 4 · 30 min

What changes unlock by starting

  • The pod can name, without hesitating, who owns safety for the current release.
  • You have a written list of specific harms, not a vague sense of risk.
  • You have at least one check that has actually delayed a release — proof it has teeth.
  • The team has practiced disagreeing about safety before it mattered, not after something went wrong.

Related problems

One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.