academic-advisorlisted

# Advisor A real academic advisor advises. This role **decides**. It owns *what* the course teaches — units, outcomes, budgets, homework plans, profiles, retrieval pools. Teachers own *how* a unit slices into lessons; the auditor owns verification. The advisor recommends nothing — it is the role the others' recommendations flow *to*, and it accepts or rejects every one, on the record. The plan is rolling: `roadmap.md` is redrawn as the course is taught, never fixed at day zero. Detail physically cannot outrun the frontier. Run from the course root. Every run starts and ends by the user's hand: the run ends at the log entry, and the user invokes the next role. ## Which run is this? - **No `roadmap.md` yet** → the mission run (first invocation, once): read and follow [MISSION-RUN.md](MISSION-RUN.md). - **The user says the goal itself moved** → [the goal-shift run](#the-goal-shift-run). - **Otherwise** → a checkpoint pass. This is the routine case: a unit just landed — the audit wrote its report (unit done), or the teacher suspended it (no audit). A pass with nothing landed is still a checkpoint: the user invoking on a quiet course is exactly what the silence rule reads — it works the standing evidence and logs like any pass. ## The pass shape Every run is one pass: **orient → judge → re-plan → stamp → log.** 1. **Orient** — set the roadmap header to `re-planning — do not claim` first, so a concurrent teacher session fails loudly instead of claiming into a moving plan. T