SCP · Build Log
This was originally scoped as a 48-week plan, then compressed to a 2-month lean slice to hit a hard deadline. Engineering ran far ahead of that lean plan's own pace, so as of 2026-09-09 this page switches back to the full Master Concept scope — nothing already shipped gets re-cut, it just gets folded into the phase it actually belongs to. Nine phases, five tracks running in parallel: Claude Code carries Engineering; you carry Legal, Business Infra, Content, and Pilot development.
Lock the technical decisions and data model so every later phase builds on solid ground — before writing feature code.
Everything else depends on identity, permissions, and the learning state machine being correct — get this right before building on top of it.
The part of SCP anyone can open without a club relationship — this is what "public launch" means in the Master Concept.
The commercial product itself — a club can run its whole academy on SCP, seats aside.
Turn seat capacity into a real, provider-neutral billing ledger — this is what makes the SaaS a business.
Give SCP Admins the tools the manual-first MVP philosophy assumes they will eventually need.
Close the gap between "it works" and "it is safe to put real students, minors, and money through it."
Build the one-time tooling a real pilot club needs to bring its existing roster onto SCP.
Put the real club on the platform and find out which of the docs' PROPOSED and OPEN items were right.
Not cut — each of these needs something other than more code: a KYC'd provider account, a lawyer, a second club, or domain expertise that can't be compressed.