Core concepts
Understand the stable ideas that every Chasing Mastery vertical composes.
The public platform has a small number of deliberately strict concepts. Learn these before the exact schemas; they tell you which schema should exist and which component can safely own it.
Trust boundary
Why portable meaning and host authority remain separate.
Attempt lifecycle
One atomic execution from initialization to a terminal committed result.
Evidence and story
How committed work becomes progression, overlays, narration, and media anchors.
Immutable releases
How active runs and historical results survive safe package evolution.
Composition, not privilege
Official packages are reference implementations of public contracts. If an official experience needs something that an external author cannot express, the correct response is to improve the public boundary with representative fixtures and conformance—not reach into a private host module.
That dogfooding rule is how Darts became useful infrastructure for Chess, speedrunning, memory training, browser activities, and future verticals.