Final systems review and demo

Inhalt

A good final demo explains what the system knows, what it does, what it does not do, why the chosen architecture fits the task, and where the main risks remain. That is the difference between a demo and a defensible system. Six-slide rule: knows / does / doesn't / architecture / humans-in-loop / failures. If you can't tell the story in six slides, you don't yet understand your own system.

Beispiel: A team presents a literature-triage assistant, shows the routing logic in n8n, the RAG grounding in Dify, explains source and memory constraints, and identifies where human review remains necessary.

Hast du das verstanden?

• [ ] You have all six slides and can deliver them in under 10 minutes
• [ ] "Doesn't do" slide lists ≥3 explicit refusals
• [ ] Architecture slide maps each concern to exactly one tool
• [ ] You show at least one logged failure and how you caught it
• [ ] You can explain in one sentence what you learned that you would tell a labmate tomorrow

Direkt ausprobieren

Diese Links öffnen die laufenden Demos auf n8n.32dots.de + dify.32dots.de.