# Chasing Mastery Developer Documentation

> Public contracts and authoring guidance for packages, Practice Modes, overlays, Station connectors, and complete vertical capability stacks.

# Chasing Mastery Developers

- [Platform overview](/docs): The public extension model for turning measurable pursuits into purposeful practice, trustworthy progress, and synchronized stories.
- Get started: From idea to real Workbench artifact
  - [Start building](/docs/get-started): Go from a plain-language practice idea to a real package or connector without learning the entire platform first.
  - [The five-minute mental model](/docs/get-started/mental-model): Pursuits, Sprints, Experience Suites, Practice Modes, Attempts, evidence, and story—without overlapping vocabulary.
  - [Choose the correct artifact](/docs/get-started/choose-an-artifact): Put each concern in the public component that can own it safely and portably.
  - [Build with your agent](/docs/get-started/build-with-an-agent): Install one source-owned Chasing Mastery authoring workflow in Codex, ChatGPT, or Claude and take an idea to the real Workbench.
  - [Chasing Mastery Author plugin](/docs/get-started/author-plugin): One source-owned plugin for Codex, ChatGPT, and Claude—portable packages, Station connectors, and scoped Club setup from a blank workspace.
  - [The authoring workflow](/docs/get-started/authoring-workflow): The complete local loop from product idea to immutable review handoff.
- Core concepts: Product and runtime mental models
  - [Core concepts](/docs/concepts): Understand the stable ideas that every Chasing Mastery vertical composes.
  - [Trust and authority](/docs/concepts/trust-boundary): The package knows the domain; the host owns identity, time, persistence, devices, and recovery.
  - [Attempt lifecycle](/docs/concepts/attempt-lifecycle): Design one atomic unit of practice that completes cleanly, replays exactly, and never depends on an enclosing session.
  - [Evidence becomes story](/docs/concepts/evidence-and-story): Preserve practice truth once, then derive progression, presentation, creator moments, and production evidence safely.
  - [Immutable releases and comparable results](/docs/concepts/immutability): Evolve visuals and behavior without silently changing what historical evidence means.
- Packages and Practice Modes: Build portable deterministic experiences
  - [Packages and Practice Modes](/docs/packages): Build immutable portable experiences that own domain meaning while the host retains authority.
  - [Package anatomy](/docs/packages/anatomy): Understand immutable release bytes, contributions, artifacts, authoring metadata, and member-facing listing promises.
  - [Activity engine](/docs/packages/activity-engine): Define deterministic Attempt behavior with describe, initialize, and apply.
  - [Input and package-owned UI](/docs/packages/input-and-ui): Build a simple host form or a rich portable player, and make every evidence path converge on one domain reducer.
  - [Measurements and progression](/docs/packages/measurements-and-progression): Design stable result contracts and rank ladders that remain meaningful outside a Sprint.
  - [Story Events and overlays](/docs/packages/story-and-overlays): Turn committed domain facts into safe, useful presentation for members, viewers, and editors.
  - [Correction and exact replay](/docs/packages/corrections): Repair committed evidence without mutating history, duplicating logic, or granting replay new authority.
  - [Coordination and multiplayer](/docs/packages/coordination): Add deterministic match, race, roster, round, and input-arbitration policy without creating a privileged multiplayer activity fork.
  - [Narration policy](/docs/packages/narration): Turn committed broadcast facts into provider-neutral cues while the host owns voices, synthesis, playback, and failure recovery.
  - [Domain Kits](/docs/packages/domain-kits): Reuse pure vertical rules, schemas, fixtures, UI, and presentation at build time without creating runtime privilege or member configuration.
  - [Workbench](/docs/packages/workbench): Design, exercise, diagnose, and prove the real package experience before immutable release bytes leave the author workspace.
  - [Package evolution and release compatibility](/docs/packages/evolution): Ship fixes and improvements while preserving pinned runs, historical evidence, and honest progression lanes.
- Station connectors: Bring exact automatic evidence into Chasing Mastery
  - [Station connectors](/docs/connectors): Translate a local device, game, browser, specialist tool, file, or service into exact semantic observations through a separately reviewed sidecar.
  - [Connector protocol and lifecycle](/docs/connectors/protocol): Build a supervised zero-grant sidecar with bounded messages, explicit capabilities, health, and graceful recovery.
  - [Exact observation contracts](/docs/connectors/observations): Make independently released package and connector bytes agree on meaning, schema, version, and identity.
  - [Source binding and live verification](/docs/connectors/binding-and-verification): Let a member choose the right automatic source, prove that it is live, and route it without creating fake practice history.
  - [Connector Lab](/docs/connectors/connector-lab): Exercise real connector bytes, grants, protocol messages, health, failure recovery, and package compatibility before review.
  - [Health and recovery](/docs/connectors/health-and-recovery): Keep automatic evidence understandable through startup, stale sources, reconnect, duplicates, gaps, and restart.
  - [Connector security and review](/docs/connectors/security): Request the narrowest local authority, prove it under supervision, and keep native code independent from package publication.
- Creator tooling: Make practice legible to viewers and editors
  - [Creator tooling](/docs/creator): Use the same verified practice evidence to improve a live stream, preserve story moments, and prepare a production handoff.
  - [OBS and capture synchronization](/docs/creator/obs-and-capture): Connect Station to a recording clock, verify presentation, and map committed facts to exact media windows without blocking practice.
  - [Design the creator timeline](/docs/creator/creator-timeline): Emit fewer, better semantic moments that explain progress, stakes, setbacks, breakthroughs, and outcomes.
  - [Production evidence and Studio intake](/docs/creator/production-evidence): Seal source provenance, activity truth, Story Events, media anchors, and gaps into an immutable editorial starting point.
- Complete verticals: Turn public extension points into a pursuit-native product
  - [Build a complete vertical](/docs/verticals): Go beyond a metric form or connector and make one pursuit community feel deeply understood.
  - [Vertical blueprint](/docs/verticals/blueprint): Design the pursuit, suite, evidence, progression, presentation, creator story, and proof before writing package code.
  - [Darts, end to end](/docs/verticals/darts-reference): Trace the demanding Darts reference implementation through every public SDK, Station, creator, and release boundary.
  - [Vertical acceptance matrix](/docs/verticals/acceptance-matrix): Prove rules, package behavior, input equivalence, product journeys, creator evidence, and release integrity at the right layers.
- Reference: Exact public TypeScript and protocol contracts
  - [Public reference](/docs/reference): Source-derived TypeScript contracts and bounded host protocols for package authors, connector authors, and agents.
  - [TypeScript SDK](/docs/reference/sdk): The small public helper layer that validates packages, engines, worker adapters, and portable UI messages.
  - [Package manifest](/docs/reference/package-manifest): Declare identity, compatibility, artifacts, capabilities, permissions, provenance, migrations, and portable contributions.
  - [Activity runtime](/docs/reference/activity): Exact context, inputs, transition effects, status, presentation, and terminal semantics for one atomic Attempt.
  - [Portable UI bridge](/docs/reference/ui-bridge): The bounded, capability-aware protocol shared by browser iframes, native WebViews, Workbench, and read-only replay.
  - [Activity Presentation](/docs/reference/presentation): A bounded semantic projection for rich players and useful overlays without moving domain meaning into the host.
  - [Connector protocol](/docs/reference/connector): Exact zero-grant sidecar identity, resources, source inventory, observations, host commands, and lifecycle frames.
  - [Creator evidence](/docs/reference/creator-evidence): Exact Story Event, capture, anchor, export, and immutable Content Studio intake contracts.
  - [Agent API and MCP](/docs/reference/agent-api): Let an authorized coding agent find Pursuits, install Suites, create Sprints, and submit a private package without gaining practice or billing authority.
  - [Limits and versions](/docs/reference/limits): Design within explicit protocol, payload, collection, artifact, and lifecycle bounds instead of discovering them in production.
- Release and review: Turn local evidence into an immutable, reviewable artifact
  - [Release and review](/docs/release): Prepare immutable package or connector bytes, prove them locally, and preserve enough evidence for independent review.
  - [Preflight checklist](/docs/release/preflight): The minimum evidence package and connector authors should close before creating release bytes.
  - [Compatibility and evolution](/docs/release/compatibility): Decide whether a change can share history, needs migration, requires a new result lane, or must remain pinned to old runs.
  - [Private review and install](/docs/release/private-review): Return a local artifact safely to one member before any public Library or connector distribution decision.