plan-what-is-learned-and-when

# Plan what is learned and when ## What it does Builds the plan of which courses each role takes, in what order and in which week, and books the dates, the trainers and the rooms in diaries on both sides. ## Where it happens The agent does this in three activities across two reference processes. Each one names the activity as that process words it. - **Book the Sessions** - `ref/prt/certify-a-partner`, activity 5 - [Certify a Partner](../../../../processes/partners/certify-a-partner.md) - **Build the Curriculum** - `ref/prt/certify-a-partner`, activity 4 - [Certify a Partner](../../../../processes/partners/certify-a-partner.md) - **Build the Learning Plan** - `ref/rev/onboard-a-seller`, activity 6 - [Onboard a Seller](../../../../processes/revenue-operations/onboard-a-seller.md) ## What to record Per plan: what each role has to prove, written as testable lines at a version, and every course traced to the requirement it covers. What each person was excused, with the evidence behind the exemption. The schedule, with who was expected in each session. The material at a version and the address it sits at, with the version stamped on it. Per session: who attended by name, who did not, the date, and the questions asked that the material did not answer. Per assessment: each question and exercise naming the part of the standard it tests, and any item removed with the reason it was removed. Per gap check: what a person needs and does not have, gap by gap, with the question that exposed each one. Per retrain: the gap named, the date it was taught again, and who sat it. Any change to a plan after teaching started, dated. Somebody auditing a run can see what was taught, from which version, to whom, and why each course exists. That contract covers every activity this abstract agent takes on, and it is repeated in `com.agentcatalog.agent/RECORDS.md`. What the abstract agent does not do is in `com.agentcatalog.agent/NOT.md`.