Chasing MasteryDevelopers
Chasing Mastery public platform

Platform overview

The public extension model for turning measurable pursuits into purposeful practice, trustworthy progress, and synchronized stories.

Chasing Mastery is a club and creator platform for measurable pursuits. Members join a shared Pursuit, practice through reusable Practice Modes, record atomic Attempts, follow independent progression, work toward focused Sprints, and optionally turn verified activity into stream presentation and production evidence.

The extension platform lets you build the part that understands a domain without giving portable code account, network, filesystem, device, or media authority.

Choose the thing you are building

One rule explains the architecture

Your package owns meaningPortable, deterministic, immutable
  • Rules and activity state
  • Measurements and progression
  • Manual player and overlay
  • Story, coordination, narration policy
Typed public boundaryNo ambient authority
The host owns authorityTrusted, recoverable, revocable
  • Identity and authorization
  • Clocks and persistence
  • Devices, Station, OBS and media
  • Routing, retries and recovery

The package decides what an observation means. The host decides whether it is authorized, where it is routed, what time it happened, and how committed evidence is persisted. The connector observes a source; it does not score an Attempt. An overlay presents committed truth; it never creates it.

This split is what makes rich third-party experiences possible without turning every package into a trusted application.

What “supported” means

Chasing Mastery does not consider a vertical supported because it has a timer or a generic metric form. A launch-quality vertical is a deep capability stack:

  1. 01
    DiscoveryPursuit + Library listing + Experience Suite
  2. 02
    PracticeSeveral useful modes + honest Attempt boundaries
  3. 03
    EvidenceManual input + one near-zero-effort automatic path
  4. 04
    ProgressComparable Measurements + ranks + Sprint finish lines
  5. 05
    PresentationPlayer + overlay + semantic Story Events
  6. 06
    CreatorOBS anchors + narration + sealed production evidence
  7. 07
    ProofFixtures + conformance + cross-surface acceptance

The Darts case study demonstrates this entire stack through the same public contracts available to an external author.

The fastest route to working bytes

Understand the Attempt

Write down when one unit of practice begins, which inputs are allowed, what makes it terminal, and which Measurements make two results comparable.

Bootstrap with the Author plugin

Choose Codex, ChatGPT, or Claude, then ask the same Chasing Mastery Author workflow to build the experience. It creates a standalone project with a pinned project-local toolchain; no platform checkout or global Chasing Mastery CLI is required.

Exercise the real artifact

Use Workbench to drive the actual reducer, player, overlay, observations, progression, Story Events, corrections, coordination, and narration across member and broadcast viewports.

Produce immutable release evidence

Run conformance and ready, inspect the deterministic .cmpkg, digest, and submission handoff, then submit it through the authenticated private review flow.

Continue with Get started for the five-minute mental model and first build.

On this page