The Heroism Tax — authored.systems

In healthcare, a nurse can’t skip a step. The system won’t let them. The medication gets scanned, the patient ID gets verified, the dosage gets checked against the order. If any of those fail, the process stops. Not because the nurse is incompetent, but because the architecture treats the procedure as a gate, not a suggestion.

In a gym, a coach walks the floor before the first class. Checks the obstacles. Looks for frayed cables, loose bolts, worn landing mats. There is no gate. There’s just the coach’s judgment and memory. If they miss something, nobody knows until a kid gets hurt.

Both operations have procedures. The difference isn’t discipline or effort. It’s whether the procedure is authored (written, enforced, recorded) or inferred from the habits of whoever shows up that morning.

The tax you’re already paying

Every operation that runs on tribal knowledge pays a tax. You don’t see it on a balance sheet. You feel it when things go wrong.

Your best person quits. The knowledge of how things actually work (not the employee handbook version, the real version) walks out with them. The next person does it differently. The one after that does it a third way. Within a month, you’ve lost consistency you spent years building.

Or it’s subtler than that. Two people perform the same task in two different ways. Neither is wrong, exactly, but you can’t measure what you can’t see. You can’t optimize a process that changes depending on who’s working.

Or something breaks and you try to walk it back. Why did this happen? Who made this call? When was this last checked? You hit a wall of “I think so” and “that’s just how we do it.” The record doesn’t exist because nobody was required to create it.

None of these are failures of effort. They’re failures of design. When the system state lives inside specific people, the operation is only as reliable as their memory and their continued employment.

The objection

When people hear “structured procedures” and “explicit policies,” they hear bureaucracy. They picture clipboards and forms and someone in a cubicle stamping approvals.

The opposite is true. Inferred systems are the ones full of red tape.

In an inferred system, you have to ask for permission because the rules aren’t clear. You sit through sync meetings because the records are incomplete. You wait for the manager to bless a decision because the policy lives in their head. Every handoff requires a conversation. Every escalation requires finding the right person and hoping they remember.

When the policy is authored and the procedure is a gate, you don’t need permission. The system already told you what’s allowed. You don’t need to report what you did because the ledger records it as you work. You don’t need to wonder if you’re qualified. The system already knows.

The structure doesn’t add steps. It removes the overhead around the steps you were already doing.

What “authored” looks like

An authored system names the six things every operation already has:

Policy: the rule. Written, inspectable, enforceable. Not “everyone knows we don’t deploy on Fridays.”
Procedure: the steps the best operator follows on Tuesday morning, written as gates. Not the SOP from 2019 that nobody reads.
Asset: the thing being acted on, with state and history.
Actor: the qualified doer — human or non-human. An entity with specific qualifications, capacity, and availability, attributed in the ledger.
Trigger: what activates a specific policy.
Ledger: structured records that answer “was this done, when, by whom, and what did they find?”

In an authored system, these aren’t just words. They’re gates. The procedure can’t start unless the Actor has the right policy clearance and the trigger has been classified. The ledger is written as the work happens, not reconstructed from memory at the end of the day.

Why this matters now

The heroism tax used to be the price of doing business. Structuring an operation was expensive. It required institutional infrastructure, compliance departments, regulatory pressure. Healthcare has authored systems because regulators forced it. Aviation has authored systems because crashes forced it. Nobody authors a system voluntarily when the cost is that high.

But AI changed the math.

AI’s contribution to operations isn’t thinking. It’s perception. It can see a photo of a frayed cable and classify it as an equipment issue. It can hear a voice note and extract a structured inspection record. It can read an unstructured email and create a classified event before the first rule fires.

AI makes it cheap to be structured. It removes the paperwork humans hate while keeping the structure businesses need. The structuring work that used to require a compliance department can now happen as a natural byproduct of the work itself.

Your operation already has these six structures. Every operation does. The only variable is whether they’re authored (explicit, enforced, recorded) or living in someone’s head, accumulating risk every day they don’t write it down.