Karte 13 · Kapitel capstone
Demo day
🟢 USE — Run first
0 - 15 min
Watch the first demo — then critique it
The first team presents their project. Your job is not just to watch — it is to ask one question the presenter cannot answer with just a demo.
- Watch the first presentation (about 5 minutes).
- Write down one question about: a failure mode, a data assumption, a privacy risk, or a scalability limit.
- When Q&A opens, ask your question.
- Listen to the answer. Was it satisfying? Did the presenter know or guess?
- After Q&A, write a two-sentence private assessment: what was strong, what was uncertain.
- Repeat for each team.
Done-Signal: You asked at least one substantive question during the session and wrote assessments for each team.
🔵 UNDERSTAND — Look inside
15 - 60 min
What makes a defensible architecture
Before you present, review these criteria. A good presentation defends the architecture, not just the demo.
🎯 Problem framing
Why this problem
Can you explain the specific user pain without referencing the technology? The problem should be compelling even to someone who does not know AI.
🏗️ Architecture rationale
Why these choices
Can you defend each architectural decision? Why n8n vs Dify? Why this model? Why this data source? Every choice should have a reason.
⚠️ Failure honesty
What does not work
The most credible presentations are honest about limitations. What are three things your system cannot do? What would it take to fix each one?
A demo proves that a system can work once under ideal conditions. A defensible architecture demonstrates that the team understands why it works, where it breaks, and what it would take to make it reliable. The goal is not to impress — it is to be honest.
Probe-Fragen
- Can you explain your architecture to someone who has never heard of n8n or Dify?
- What is the most fragile part of your pipeline — the part most likely to break in production?
- If your project continues beyond this course, what is the first thing you would change?
🟠 BUILD — Make it yours
60 - 90 min
Present and defend
You have 10 minutes: 5 minutes demo, 5 minutes Q&A. The Q&A is the real assessment.
Aufgabe: Present your project with a live demo, then defend the architectural decisions in Q&A.
- Open your system before your presentation slot. Test it once with your best test case.
- Minute 0-2: explain the problem — who has it, why it matters, what they do without your tool.
- Minute 2-4: run the demo — one real input, show the output, explain one architectural decision along the way.
- Minute 4-5: show your test log — name one failure and what you learned from it.
- Minute 5-10: Q&A. Answer what you know. Say 'I don't know' when you don't. Explain what you would investigate.
- After all presentations: write a one-paragraph reflection on what you would do differently with one more week.
Deliverable: Working system + test log + one-paragraph reflection.
✓ SELF-CHECK
Hast du das verstanden?
- I can explain the problem without any technical jargon.
- I can justify every major architectural decision.
- I identified at least three limitations of my system.
- I am honest in Q&A about what I do not know.
You built and defended a real AI system. What is the gap between what you presented and what you would need to deploy this in a real research environment? Make a list — that list is your roadmap.
💬 KI-TUTOR
Frag den Tutor zu dieser Karte
Sokratisch: der Tutor antwortet mit Leitfragen statt fertigen Antworten — du erarbeitest die Lösung selbst.
Stell eine erste Frage zu dieser Karte unten.