Problem statement

Leadership wants a repeatable demo next Friday—not “works on my laptop.” Pin prompts, dependencies, and seeds.

Outcomes

• requirements.txt (or lock) + versioned prompts/ + trace artifact.
• Understand prototype fidelity tradeoffs (notebook vs Streamlit vs Next).

Deliverables

• Package Week 10 demo into prototype_v1/ with pinned prompts and README.

Links

• Phase 6

• [ ] Python venv + pip freeze or uv/pip-tools (pick one workflow).
• [ ] Skim Streamlit deployment constraints (secrets, env vars).

Time: ~2 h.

Task A — Reproducibility

Create prototype_v1/:

• requirements.txt with pinned major versions
• prompts/system.txt and prompts/user_template.txt
• README.md: exact commands from clean venv to run
• Optional: seed.txt if any randomness

Task B — Cost note

Estimate order-of-magnitude tokens per demo session (assumptions explicit). cost_note.md — half page.

Submit: zip or folder my-submissions/week-11/prototype_v1/.

20 min.

1

Why is versioning prompts like versioning API contracts?

2

List three items you’d include in a trace for debugging.

3

Notebook vs Streamlit for demos—one strength each.

Self-grade: Phase 6 checklist.

Concepts & curated links: read the Learn chapter Prototypes first (topic path, not calendar-only). This file is the weekly practice bank — extra drills and a checklist on top of Readings → Practice → Exam.

1. Practice bank

2. Week checklist

• [ ] PRACTICE.md + EXAM.md