Heidelberg AI Curriculum

5books in this track

L01 · User

Who is affectedOnly you

Build a Small Browser Tool You Will Actually Use

Describe a small calculator or helper by its input, action and output, have OpenCode Desktop build it as one HTML file, check it against answers you worked out by hand, then improve it once because using it showed you what was missing.

Outcome: Your index.html plus three test cases, each with the input, your hand-calculated answer and the tool's answer; it passes when all three match, an impossible input is refused, and one improvement came from real use.

User14 minLast edited: Oct 18, 2026

L02 · Power user

Who is affectedYour team sees a bad document or a wrong figure

T06-L02

Build a Small Shared Tool From a Prompt, and Test It With a Colleague

Turn a shared spreadsheet your team keeps breaking into a small web app built from prompts in Base44. Describe the screens and data first, add one change at a time, restrict who can read and edit, and let a colleague prove it works in their own browser before anyone relies on it.

Outcome: A live Base44 app used by at least one colleague, plus a half-page note: the screens and fields, the access and permission settings as set, the colleague's test with one allowed and one refused action, the CSV export opened in a spreadsheet, and the account holder and deputy. It passes when a signed-out visitor sees no data and the colleague's test matches the note.

Power user15 minLast edited: Sep 23, 2026

L03 · Builder

Who is affectedColleagues depend on something you built

T06-L03

Turn Your Team App Into One Colleagues Can Depend On

Take the Base44 app from T06-L02 · Build a Small Shared Tool From a Prompt, and Test It With a Colleague to where colleagues can depend on it: two roles the data enforces, clear empty and error screens, a test copy with known answers, an operating note with a maintainer and deputy, and a line where IT takes over.

Outcome: A published Base44 app with two roles, a test copy with known-answer records, a one-page test sheet and an operating note; it passes when a colleague who didn't build it runs the whole test sheet through the testing link and every line matches, and the deputy publishes one small change without your help.

Builder20 minLast edited: Sep 23, 2026

L04 · Integrator

Who is affectedCompany or lab systems and real data are in the loop

T06-L04

Put Your Team App on the Organisation's Own Database, and Prove You Can Restore It

Move a team app's data out of the app builder into a self-hosted Supabase, the open-source PostgreSQL platform, that your IT runs. Enforce who sees which rows with row-level security, give every person, program and assistant its own narrow login, back up off the server, and restore into an empty database.

Outcome: A restore record and a role test sheet for a team app whose data lives in a Supabase your organisation runs; it passes when the restored copy, built from the off-server backup into an empty database, gives the same answers to every line of the role test sheet, no admin key appears in the app, and IT and the data owner have signed.

Integrator22 minLast edited: Sep 23, 2026

L05 · Operator

Who is affectedWork stops when it breaks, and it must survive you leaving

T06-L05

Run the App Others Depend On, and Hand It Over

Operate a team app that many people rely on, for years: every change through a staging copy, a rollback you have practised, outside checks on sign-in, backups and certificates, a yearly plan for updates, licences and costs, a quarterly access review, and a deputy who can release, roll back and restore without you.

Outcome: A 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 minLast edited: Sep 23, 2026