The AI track ends, like every level of the academy, with three parts: a demo of ten minutes, a code reading in which someone points at a place and says "Explain this to me", and a technical discussion about your test set, your attack test and your costs. Nothing more is built in this lesson. The Kladde is finished, and all six issues are closed. The lesson prepares you for the discussion.
The discussion is not an interrogation and not an exam that you are supposed to fail. It is the moment when it shows what you have learned: not whether you know the names of all the classes, but whether you know why your code is the way it is, and how you know that it works. Whoever can answer every question with "this test shows it" or "this number says it" has won.
The demo: ten minutes
Ten minutes are short. Whoever starts explaining the Kladde is at minute twelve after three features. So plan the demo like a small story of the made-up IT office, with a sequence you can recite by heart:
| Minute | What you show | The proof for it |
|---|---|---|
| 0–1 | The office and its question: "Is this tender worth it, and how does the quote go out quickly and safely?" | – |
| 1–3 | A tender is assessed; suitability, reasons, prompt version and model are on the assessment. | the acceptance test of the assessment, the test set with its rate |
| 3–5 | The support chat answers a question with a source and declines one that the help does not answer. | WithoutAHitTheChatAsksNoModel, AnInventedSourceNeverBecomesALink |
| 5–8 | The agent drafts a quote, wants to send, a human approves, a mail goes out, a second click sends nothing. | AQuoteIsDraftedApprovedAndSentExactlyOnce |
| 8–9 | check.ps1 from a fresh clone: all green. The meter shows the tokens per feature, the cap shows the month. |
check.ps1, /ki/verbrauch |
| 9–10 | One attack from the report, with what the person saw. | docs/attack-test.md, AgentAttacksInTheBuildTests |
Three rules keep a demo calm:
- The sequence is rehearsed, with a clock. At least twice, once of them in front of someone who does not know the Kladde.
- There is a plan B. A local model can be slow, or the answer turns out differently today. Keep a way out ready for every step: an assessment that is already saved, or the test that shows the same thing. Reaching for the test then is no flaw but exactly what the Kladde teaches: the test is the proof, the demonstration only an example.
- No real data, not even by accident. The tenders, contacts and help pages of the demo are made up. Check beforehand what is visible on the screen: browser tabs, the list of recent files, notifications.