What you can build
Practical examples of the practice, automatic evidence, progression, live presentation, and creator experiences the platform can compose.
Chasing Mastery is not limited to a timer, score form, or one type of hobby. A complete experience can be as simple as a focused manual drill or as deep as a Pursuit-native practice and creator system.
Practice experiences
A package can provide a responsive player with real domain rules. It can use buttons and forms, or render a rich board, route, puzzle, target, timeline, or game surface on web and mobile.
It can support:
- several related Practice Modes in one coherent Experience Suite;
- typed results such as score, time, accuracy, streak, success, or a composite;
- rank ladders and lifetime progress that exist independently of Sprints;
- corrections without rewriting history;
- solo practice, local or remote matches, races, rounds, and teams;
- provider-neutral narration policy and accessible manual input.
Examples include a chess puzzle trainer, a memory recall test, an aim routine, a split-segment drill, a darts scoring game, or a mode made specifically for one game and its community.
Automatic input
The best experience often uses a specialist tool people already trust. Station connectors can translate evidence from devices, games, browsers, timers, files, logs, local webhooks, and reviewed services into the same package rules used by manual input.
This lets Chasing Mastery add goals, progression, community, and creator value without forcing a community to abandon its preferred execution tool. Examples include AutoDarts, LiveSplit, browser-based chess, hotkeys, game logs, and training-result exports.
Automatic input is never mandatory. A thoughtful manual path is the fallback and often the right first release.
Progress that stays meaningful
Every completed Attempt can contribute to mode-specific history and progression whether or not it belongs to an active Sprint. A Sprint can then use a chosen Practice Mode result as a starting point and finish line without owning the member's broader practice history.
This supports both people pursuing lifelong mastery across several skills and creators concentrating on one clear challenge story at a time.
Creator experiences
Packages can describe what a viewer should understand, while Chasing Mastery and Station safely handle provider and machine authority.
An experience can contribute:
- a read-only stream overlay with current state, stakes, pace, or rank;
- semantic moments such as personal bests, setbacks, wins, and breakthroughs;
- narration cues without choosing or calling a voice provider;
- OBS capture timestamps and media anchors;
- correction-aware production evidence for Content Studio.
The goal is useful live presentation first and easier storytelling later—not a noisy event stream or a generic clip button.
Complete Pursuit experiences
The deepest result combines community discovery, several genuinely useful Practice Modes, a low-effort evidence path, progression, Sprint templates, creator presentation, and proof across web, mobile, Station, and broadcast surfaces.
The Darts reference is the current example: eight modes, a rich dartboard, manual and AutoDarts input, corrections, progression, multiplayer, narration, overlays, OBS timing, and immutable Studio evidence—all built through the public boundary.
What your agent needs from you
You do not need to turn this list into a technical specification. Bring the community, the practice problem, the important result, and the experience you wish existed. The Author workflow will ask about the few missing decisions that actually change the product, then handle the public SDK and proof mechanics.