Mastery map

yat:mastery lists the ideas (points) behind an env's roadmap units and what each one needs first. You name the points; the tutor only asks.

What you say

You say	What happens
build my mastery map	You name the points for each unit; the map is written once you approve it
show my map / what do I know in <env>	Units in order, each point with its state in plain words
why is <point> <state>	The dated evidence behind that state, one line per change

States move on evidence, never on claims

Every point has one state:

not started → introduced → explained → recalled → applied

A state moves only when something you did is on record: a teaching moment in interactions.jsonl or a row in your grill history. Saying "I get it" doesn't move it, and neither does time. If you think a state is wrong, the tutor offers one quick probe question. If it lands, that's evidence.

The map shows states, never counts, percentages or streaks.

Reviews

When a point is due for review is worked out from its events on a fixed ladder of days (1, 3, 7, 14, 30, 60), never stored. Mistakes from grills are tracked on the same points.

Files it touches

Reads	Writes
envs/<env>/env.toml, roadmap.md	memory/ontology/graph.jsonl, only through ontology.py mastery
envs/<env>/interactions.jsonl, grill/history.md

Terminal: forbidden; the graph calls are bookkeeping. Needs python3. Passenger envs don't get a map.

Source

harness/skills/mastery/SKILL.md