SESSION 01 · TUESDAY
Threat-model your product, defend your AI feature against prompt injection, handle personal data with care and take test payments.
You will be able to
- Build a threat model with Adam Shostack’s four questions and rank what could go wrong
- Explain prompt injection and apply five layered defences to your AI feature or internal tool
- Write a privacy notice and list the questions a data-protection specialist must answer
- Decide what your logs record, so they help you debug without leaking personal data
- Take a test-mode payment through hosted checkout, fulfilled once by a verified webhook
OUTPUT · Threat model + injection tests + privacy notice + test-mode payments
SESSION 02 · THURSDAY
Every change takes the same checked path: tests and evals in CI, a review, then a staged rollout you can undo in seconds.
You will be able to
- Set up continuous delivery: branch, pull request, CI, review, deploy
- Run tests and evals on every pull request, with branch protection blocking a failing merge
- Put Claude in the pipeline: @claude reviews and Claude Code in GitHub Actions
- Build a dashboard for errors, speed, AI quality and cost, with alerts that name an owner
- Plan a staged rollout behind a feature flag (5%, 25%, 100%) with a rehearsed rollback
OUTPUT · CI pipeline + dashboard + staged rollout plan in product/11-operations.md
© 2026 MVP Studios Ltd. MVPAI™ and the MVP Founders Programme materials are original works of MVP Studios Ltd. All rights reserved. No copying, redistribution or commercial use without written permission. Course terms