Build a complete vertical
Go beyond a metric form or connector and make one pursuit community feel deeply understood.
A package can be technically valid and still be a weak product. A complete vertical combines the public extension points into a pursuit-native experience that serious practitioners would actually choose.
- 01DiscoveryPursuit + Library listing + Experience Suite
- 02PracticeSeveral useful modes + honest Attempt boundaries
- 03EvidenceManual input + one near-zero-effort automatic path
- 04ProgressComparable Measurements + ranks + Sprint finish lines
- 05PresentationPlayer + overlay + semantic Story Events
- 06CreatorOBS anchors + narration + sealed production evidence
- 07ProofFixtures + conformance + cross-surface acceptance
The standard is depth
A launch-quality vertical should answer all of these questions:
- What do skilled practitioners actually practice, and why?
- Which existing tools should Chasing Mastery integrate rather than replace?
- Which Practice Modes are missing or materially better when owned here?
- What can be observed with almost no effort from the member?
- Which Measurements remain comparable over time?
- What makes progress legible during a stream and useful in an edit?
- Which failure states preserve trustworthy practice history?
The member should discover a deliberate Darts, Chess, or Trackmania experience—not install a generic category package and configure the product's meaning themselves.
Use public composition, not privileged code
Every official vertical is built through the same contracts available to an external author. Domain logic belongs in a Domain Kit or immutable package. Native observations come through a separately reviewed Station connector. The host remains domain-neutral.
- Rules and activity state
- Measurements and progression
- Manual player and overlay
- Story, coordination, narration policy
- Identity and authorization
- Clocks and persistence
- Devices, Station, OBS and media
- Routing, retries and recovery
Recommended route
- Write the vertical blueprint before implementation.
- Build one honest manual-input gold path in Workbench.
- Add the lowest-friction evidence path without changing the reducer.
- Add progression, story, presentation, and creator evidence in that order.
- Use the Darts reference to see each seam exercised.
- Close the acceptance matrix with retained evidence.