Final Demo Checklist

Before the final demonstration, verify:

• A new evaluator can follow the README from a clean machine/environment.
• Required dependencies and environment variables are documented.
• No secrets are committed.
• The main branch is green in CI.
• Core user workflows can be demonstrated with realistic data.
• Failure behavior can be shown for at least one important case.
• Tests can be executed during or before the demo.
• Architecture diagrams still match the implemented system.
• Known defects and limitations are documented.
• Each team member can explain major design and quality decisions.
• The final release/tag is identifiable in the repository.

Suggested demo structure

1. Problem and users — 1 minute.
2. Architecture — 2 minutes.
3. Working product — 5–7 minutes.
4. Testing/CI/quality evidence — 2–3 minutes.
5. Lessons learned and limitations — 2 minutes.