Public Playground MVP
The last capstone turns your strongest original lessons, labs, and diligence tools into one coherent public slice of a learning platform — small enough to finish, honest enough to defend, real enough to teach.
A narrow learning route with strong checks teaches more — and says more about its author — than a broad platform with none.
The final capstone turns your strongest original work — lessons, labs, formulas, scorecards, diligence tools — into one coherent public slice of a learning platform: small enough to finish, honest enough to defend, real enough to teach a stranger.
Core concepts: public explanation, capstone synthesis, assessment evidence.
A slice, not a shrine
The public playground MVP is the bridge from private mastery to something a stranger can learn from. It does not ship the whole curriculum. It ships one coherent slice: an original lesson, its prerequisite concepts, an interactive or inspectable check, a practice item, a worked example, an assessment, a source boundary, and a pointer to the next route.
The slice must prove the platform can teach, test, and transfer understanding. Two things it must never do: leak private scaffolding into public copy, and present dated, current claims as timeless facts.
The mastery check, applied to every route
Every route carries the same four pieces: . An explanation without a check manufactures false confidence. A check without a limitation teaches overclaiming. A proposed route that cannot supply all four is not ready, no matter how good the prose is.
The assessment deserves special care because it produces the platform's only hard evidence. A question the learner can answer by pattern-matching the page proves nothing. A question that requires reproducing a calculation, predicting an output before running it, or spotting a flawed claim produces assessment evidence — something you can show a skeptic when they ask whether the platform teaches anything at all.
Worked example: one route, end to end
Take a strong lesson — qubits without hype, Bell states, Grover search, resource estimation, or application baseline scoring. The route outline reads: prerequisite concepts linked; the explanation written in your own words; one visual or code artifact the learner can manipulate; one practice task; one worked example; one oral-style prompt; one source-boundary note stating what is stable, what is current, and what needs refresh.
The deliverable is a platform outline: route map, original content, checks, and the next iteration plan. Before anything ships, walk the route as a learner would and label every block — stable fundamental, current claim, private scaffolding, or needs-refresh.
How MVPs go wrong
The first failure is the landing page: polish where the learning should be. The second is scope greed — ten thin routes instead of one strong one. The third is laundering notes: pasting private source material into public pages without rewriting it as an original lesson shaped around learner tasks rather than source order.
The fourth failure is silence about scope. The MVP should say what it deliberately leaves out. A reader who knows the boundary trusts what is inside it.
The engineer's view
Treat the MVP as information architecture plus a product test: routes, schemas, reusable components, data contracts, interaction states, assessment evidence. The data layer already anticipates routes for concepts, formulas, labs, examples, practice, assessments, companies, applications, and capstones — the MVP only needs to prove one of them end to end.
Favor inspectable learning over marketing. A user should be able to read, manipulate, calculate, answer, and know whether they passed. A page that cannot tell the learner how they did is a brochure.
The iteration plan is part of the deliverable. Name the next three routes, the order you will build them in, and the reuse each one gets from the slice already shipped — components, schemas, check patterns. An MVP whose second route costs as much as its first has not found its architecture yet.
Deciding what to build first
Choose the slice with low source risk and high teaching value — stable fundamentals with an original explanation beat a current-events route that expires in a quarter. Then test it on real people and measure the right thing: not whether the page looks finished, but whether learners complete the mastery check.
Watch for the failure where the audience test measures the wrong signal. Praise is cheap; completion data is not. If testers stall at the same block, that block is the bug report. If they finish and cannot say what they would try next, the transfer prompt is the bug report. Either way the test worked — that is what it is for.
Exercise
Outline the slice. Prepare the MVP outline for one route.
- Submit: the route map with original content, learning checks, source boundaries, and the next iteration plan.
- Check: apply the teaching mastery check to every block of the route; flag or cut anything missing a check or a limitation.
- Transfer: adapt the route pattern to a second concept, lab, or diligence tool.
- Repair: if the draft resembles a summary of sources or gives the learner nothing to do, rebuild the lab discipline after Chapter 44, Reproducible Quantum Labs.
Check your understanding
Walk someone through the route and have them attempt the check.
A passing MVP is one where a real learner finishes, knows whether they passed, and can say what the route deliberately does not cover.
If you get stuck
If the slice mixes private scaffolding with public copy, hides which claims are dated, or lacks mastery checks, revisit Chapter 44 (Reproducible Quantum Labs) for checkable learner tasks before shipping anything.