L03 · Responsibility level
Colleagues depend on something you built
You have completed the same task by hand eleven times this month. In a lab, it is a weekly check for new papers; in a company, it is a Friday status report. You promise to make the next run easier for colleagues. One colleague suggests an app. Another suggests an agent that can search, decide, and write by itself.
This mini-book is for Level 3 Builder. Colleagues will depend on an assistant you configure. If its sources, permissions, or instructions are wrong, several people can create the same bad document before anyone notices.
T03-L03 · Prompting & context · Level 3 Builder · 60 minutes
At Level 3 Builder, colleagues depend on a retrieval system you configured. A citation can point to a real document while the answer still uses the wrong passage, drops a qualifier, or answers a different question. Your job is to make those failures observable before changing the model or shipping the system.
At Level 3 Builder, colleagues depend on something you built. A pipeline that silently omits a paper or misroutes a request creates work for everyone who trusts its report. Build for inspection: every source item, exception, model result, and review decision must remain traceable.
At Level 3 Builder, the prototype is no longer only yours. This book turns the tracker from T06-L02 into a bounded multi-user test app whose login, roles, validation, failure states, conflicts, and feedback path work for a second user.
At Level 3 Builder, other people may rely on what you build. Your first agent therefore needs less freedom than the demonstrations that make agents look impressive: one job, two or three narrow tools, a hard stopping condition, visible traces, and a person who approves the proposed result.
At Level 3 Builder, another person may depend on code you direct an agent to change. The goal is no longer merely to get code that runs. You need a change whose intended behavior was agreed before implementation, whose boundaries are visible in the diff, and whose evidence lets a reviewer accept or reject it...
This mini-book is for Level 3 Builder. You will turn a folder of recordings into a traceable batch of draft transcripts and subtitles, with an optional dubbing branch and a human gate before any approved output. The exercise uses synthetic recordings only. A successful execution is not permission to publish.
At Level 3 Builder, colleagues depend on something you built. A correct figure on your computer is not enough: raw evidence, transformation steps, parameters, checks, and run instructions must let another person regenerate it without your memory or hidden setup.
At this level, colleagues depend on something you built. A container makes an application repeatable; it does not make the application persistent, reachable, secure, or recoverable. You own those boundaries and the evidence that they work.
At Level 3 Builder, colleagues depend on something you built. A mistake no longer stays in your own chat: an unattended workflow can repeat it across a shared queue before anyone notices. Governance at this level means giving the team a rule they can inspect, test, and use to stop the build.
T13-L03 · Adoption & enablement · Level 3 Builder · 35 minutes
At Level 3, an assistant can request live data instead of waiting for you to paste it. That removes copying, but it also gives the assistant a route to another system. The route must be narrower than the account behind it, inspectable on every call, and proven to refuse access outside the task.
At Level 3 Builder, a successful prototype is not permission to use live data. When an AI component touches information about participants, patients, employees, customers, or applicants, you must make the proposed processing visible to the people who own ethics, privacy, security, contracts, and the affected...