L05 · Responsibility level
Work stops when it breaks, and it must survive you leaving
This mini-book is for Level 5 Operator. The assistant is now a shared service. Work can stop when identity, capacity, routing, or recovery fails, and the service must remain operable after its original builder leaves.
T03-L05 · Prompting & context · Level 5 Operator · 35 minutes
You are operating the document stack that your lab or company now relies on. In March, the source owner withdrew a protocol after a control failed. Six months later, the assistant still tells a researcher to follow it and cites the old title. In the Company version, procurement withdrew a price list, but a sales...
T05-L05 · Automation · Level 5 Operator · 45 minutes
The booking tracker from T06-L04 now has a real API, data-layer permissions, a reviewed schema path, and a restore that somebody has actually performed. That is not yet an operated service. Its public route may still depend on a builder platform, its deployment may exist only in the author's memory, and its domain,...
The agent from T07-L04 · Agents with real credentials has a narrow identity, read-only inputs, no arbitrary network access, and no authority to publish. It can safely propose a disposition for one synthetic document. Now the queue is growing. You split the job into a retrieval agent, an extraction agent, and a...
At Level 5 Operator, automation can propose changes while nobody is watching, consume third-party code, and move an artifact toward a shared environment. Your job is to make its authority smaller than its task, make every release claim traceable to an exact commit and artifact, and prove that the previous approved...
Your marketing team publishes an AI-generated image of a person who does not exist. A colleague asks whether the image is labelled, which model produced it, whether the model and reference inputs permitted commercial use, and who approved publication. The exported JPEG contains no visible answer. The generation...
At Level 5 Operator, a successful calculation is not enough. You must preserve the source, code, checks, comparison, decision, and published value so another operator can reproduce the claim after its builder has left. This book supplies one deliberately small, standard-library implementation for both a Lab figure...
At Level 5 Operator, a model endpoint is shared capacity. A configuration that answers one prompt can still fail ten colleagues through queue growth, memory exhaustion, unfair admission, or costs nobody counted. Your job is to publish a measured operating envelope, reject excess work safely, and know when another...
At Level 5 Operator, an AI system is a continuing organisational responsibility: purpose, people, data, suppliers, controls, evidence, cost, fallback, and a decision about whether it should operate. The operator must show the current position without the builder's memory.
An auditor asks how you know the people operating your AI-enabled workflow are competent. You show a folder of course certificates. The auditor chooses one name and asks what that person may do, which system version they learned, whether they can recognise a failed output, and what changed after last month's...
Nine connectors are installed across your team. One reads shared files, one opens tickets, and another can update inventory. Two were installed by people who have left. The client shows friendly connector names, but nobody can say which publisher supplied each executable, whose identity reaches the source, whether...