Problem statement

You have 8 minutes with VP-level stakeholders. Script the demo; start the Insight copilot capstone per master plan.

Outcomes

• 5-minute demo script with fallback lines.
• Capstone charter: problem, users, scope, non-goals, success metrics.

Deliverables

• demo_script.md (timed reading ~8 min aloud).
• capstone_charter.md (1–2 pages).

Links

• Capstone

• [ ] Re-read Capstone section in master plan.
• [ ] Optional: one post on offline vs online eval.

Time: ~2 h.

Task A — Demo script

demo_script.md: sections Setup → Question 1 (insight from DB) → Question 2 (doc/policy) → Failure fallback → Q&A. Include exact opening line and exact line if API fails.

Task B — Capstone charter

capstone_charter.md must define:

• Problem & user
• In-scope / out-of-scope
• Metrics (quality + ops + cost)
• Risks (safety, wrong SQL, stale docs)
• Week 13–14 milestones

Task C — Dry run

Practice aloud once; record actual duration; trim script if > 8 min.

Submit: my-submissions/week-12/.

25 min.

1

What belongs in a demo fallback line that engineers often forget?

2

Name two capstone metrics that are not “users love it.”

3

One non-goal you should write explicitly to prevent scope creep.

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

• [ ] Demo dry-run recorded or timed
• [ ] PRACTICE.md + EXAM.md