All books | Heidelberg AI Curriculum

Progress is saved in this browser only.

18 books

Chat & assistants1

T02-L05Run One Assistant for a Whole Institute or Company, and Hand It OverAn access audit for the shared assistant: every account, role, key and emergency access with its owner and revocation path, a tested one-action leaver removal, group budgets with last month's cost per group, the records and retention table signed by the data protection officer, and the substitute's run. It passes when a test leaver loses a live session and a fresh login within the stated window after one action, no local password login works, and the substitute repeats the audit from the runbook alone.Operator20 min read

Prompting & context1

T03-L05Keep a Production Prompt Healthy for Months, and Hand It OverAn operations folder for one production prompt: the regression set with its critical group and pass rule, the gate results for one change, a monitoring page with three signals and named responders, and one incident or drill note. It passes when the substitute reproduces the gate decision and a rollback from the runbook alone, and a colleague answers three auditor questions from the folder.Operator21 min read

Your documents & knowledge1

T04-L05Keep a Connected Knowledge Base Current, and Prove a Withdrawn Document Is GoneA withdrawal drill record for one connected knowledge base: the stated windows, a current and a withdrawn marker checked before and after, the time from withdrawal to disappearance in every place checked, who received the withdrawn document and how they were told, and the substitute's run. It passes when the withdrawn marker is gone within the window, the current one still works, and the substitute ran it from the runbook alone.Operator18 min read

Automation1

T05-L05Keep Your Automations Running for Months, and After You LeaveAn operations folder for every automation you run (register, alert setup, incident routine, change log and handover checklist), which passes when every automation has a keeper and deputy other than you alone and a heartbeat that alerts a team channel, a deputy handles a staged incident from the folder alone, and a colleague answers three auditor questions from it in 15 minutes.Operator21 min read

Build apps1

T06-L05Run the App Others Depend On, and Hand It OverA handover folder for one app (release steps, rollback record, monitor list, update and cost plan, access review, restore record), which passes when a deputy, with the builder's accounts disabled for the day, releases a change through staging, rolls it back, and restores last night's backup to a test server from the folder alone.Operator18 min read

Agents1

T07-L05Keep a Team of Agents Running for Months, With Memory a Person ApprovesAn operations folder for agents colleagues depend on: four weeks of run log and weekly reviews, the memory file with a source and review date for every note, a runbook with one drill, an audit index, and a deputy's handover record. It passes when the deputy runs a review and a drill alone and an auditor's question is answered from the folder.Operator19 min read

Write code1

T08-L05Run Automatic Checks, an AI Reviewer and Releases You Can Roll BackA repository with required checks, a comment-only AI reviewer, dependency notes, a release record and a runbook, plus a handover record. It passes when a pull request that breaks a known answer is blocked, a rollback drill restores the previous version in under 15 minutes, and the deputy runs both without help.Operator30 min read

Create media1

T09-L05Keep Every Published AI Image, Voice and Video Labelled, Cleared and TraceableA media register and a one-page runbook in a place the organisation owns; it passes when every AI asset published in the last quarter has a complete register row, one monthly check has been run and logged, a takedown drill has been done on one asset, and the deputy answers an auditor's question about a randomly chosen asset from the register alone within five minutes.Operator18 min read

Data & analysis1

T10-L05Keep a Data Pipeline Right for Years, and Trace Any Published Number to Its SourceA written trace of one number that was published from the pipeline, from where it appears back to the source rows, which passes when every step names its run ID, fingerprint and person, the missed-run alert and the drift check have each fired once in a test, and a colleague repeats the trace from the runbook alone and reaches the same rows.Operator18 min read

Run your own AI1

T11-L05Keep a Shared Model Server Fast, Affordable and RunningAn operations pack for a shared model server: a capacity table from a load test with the limit you set, a cost sheet comparing your server and an API per 1,000 answers, a one-page runbook and an operations log. It passes when a second operator has handled a practice outage from the runbook alone and the service owner has signed the cost decision.Operator21 min read

Security, privacy & governance1

T12-L05Keep One List of Every AI System Your Team Runs, and Make It Survive YouAn AI inventory for one team: every system with purpose, risk tier, responsible person and stand-in, data touched, training record, linked proof and next review date, plus a record of one 'author has left' test. It passes when a stand-in who didn't build any of the systems answers an auditor's five questions and handles a practice incident from the inventory alone.Operator19 min read

Adoption & enablement1

T13-L05Keep Everyone's AI Skills Current, and Show It When AskedA role map and a training register for one real department, which pass when every role's abilities are written as checkable tasks, every person with access to an AI tool has a current check result or a dated reason why not, one monthly reconciliation with the access lists has been run and logged, one change has gone through the refresh decision, and a deputy answers an auditor's three questions from the register alone.Operator19 min read

Connect your tools1

T14-L05Run Your Organisation's Connectors: One List, Per-Person Access, a Log and a Clean ExitA connector list for one department or company team, plus one retirement record: it passes when every connector has what it reaches, whose access, version, log, responsible person, stand-in and stop; two test accounts show different access where they should; and a retired connector can't be called while its former users know the fallback.Operator19 min read

AI in research1

T15-L05Keep Your Group's AI Use Compliant and Running After You LeaveA compliance and continuity dossier: a register of the group's AI uses with who decided each open question, a retention plan per item, and a record of a named successor's walkthrough; it passes when the successor has run the main AI-assisted step and restored one archived result without help, and the PI has signed.Operator21 min read

Choose tools1

T16-L05Keep Your Toolset UsefulA toolset folder (register, last quarterly review, change routine, one completed retirement record, handover checklist), which passes when every tool has two named admins and organisation billing, every contract with personal data has a data processing agreement on file, one tool has been retired with a deletion confirmation, and a colleague answers three auditor questions from the folder in 15 minutes.Operator17 min read

Structure & understand1

T17-L05Decide Which Problems Deserve BuildingA ranked portfolio of every running and proposed item with four scores and a decision each, plus a decision log, which passes when every kept or built item has a named keeper and backup other than you, and a colleague who wasn't involved can answer three questions about past decisions from the log alone.Operator17 min read

Share & review code1

T19-L05Run Your Organisation's Gitea: Teams, Safe Sign-In and a Restore You Have TestedA colleague restores last night's backup on a test server using only the runbook and finds the organisation with its repositories, issues and pull requests; every password account has two-factor, a student account can read but not edit, and the mirror updated within the last day.Operator22 min read

AI harnesses1

T20-L05Run Coding Agents for a Team: Shared Rules, a Test Set, Nightly Jobs and No Lock-InHouse rules with their checks, the four-row run table, links to one passing and one deliberately failed workflow run, and the operator log. Passes when every rule has a check, the job fails on a broken rule even if the agent reports success, harness/model/gateway are single settings, and the log names the next test-set date.Operator20 min read