# Teaching notes

## Who

Platform founder/builder. Deep TypeScript + Postgres. Treat as a peer who needs
the domain argument, not a student who needs the concept explained. Every claim
in every lesson carries a `file:line` so it can be checked.

Prefers to be handed a **verdict with its evidence**, then interrogated — not
walked through options. Ask questions before authoring; do not ask after.

## Established

- **Mission** = decide the Sprints/Tasks merge. See [[MISSION.md]].
- **Vocabulary** is canonical in `reference/0001-pm-glossary.html`. Use it verbatim.
- **Rule:** the repo's PM docs are fiction. Verify against `dbschema.md` + source.

## Open threads

1. **Write the verdict down.** The lesson delivers a verdict but the user has not
   yet committed to it in code or in a decision record. Next session should ask
   "which of these did you actually do?" — the answer recalibrates everything.
2. **The doc rewrite is pending.** `PM_MODULE_GUIDE.md` §2/§5 still describes 10
   non-existent tables. Until fixed, every new engineer is misled.
3. **`capacity.service.ts:262` still filters `neq("status_column", "Done")`** —
   the raw string comparison that `task-status.ts` exists to prevent. The fix is
   in fix-order step 3 of the wiring map.
4. **Unused components.** `assets/course.css` and `assets/quiz.js` are built but
   exercised by only one lesson. If lesson 0002 does not need a quiz, extend the
   recall/quiz vocabulary rather than adding a second stylesheet.

## Workspace conventions established

- Lessons: `lessons/NNNN-slug.html`, one tightly-scoped win each.
- Reference docs are the durable artefact; lessons are throwaway and link to them.
- Every lesson ends with: a primary source to read, an ask-the-agent block, and
  nav links to reference docs.
- `learning-records/` holds decision-grade insights only, titled by claim not by
  session. No activity logs.