Skip to content

The Kanban

The Kanban is your editable student state. Open uwwoe.fyi and you land on the atlas; the Kanban lives as a panel alongside it.

What’s in the Kanban

A Kanban is a list of terms, each term holding a list of course entries. Each entry has:

  • A course code (subject + catalog number, e.g., MATH 247).
  • A status: planned, taken, or in-progress.
  • Optional grade (used by requirements that check grade thresholds).
  • Optional notes (private; never used for academic evaluation).

Terms are typed: Fall, Winter, Spring, with a year. Co-op work terms are representable as terms with no course load.

Adding a course

  1. Open the course library search via the command palette (⌘K / Ctrl+K) or the search affordance on the Kanban.
  2. The search hits GET /api/v1/courses server-side — there is no pre-baked target list in the frontend. Type the subject (MATH), the partial code (MATH 23), or the course title.
  3. Pick a course. Choose the term and status. Submit.

The Kanban updates locally and persists via PATCH /api/v1/state/current.

Moving and editing entries

  • Drag a course across terms to reschedule it.
  • Click an entry to edit its status, grade, or notes.
  • Right-click an entry for “remove” or “view source”.

Every mutation goes through PATCH /api/v1/state/current with optimistic concurrency — your expected_state_version is checked server-side; a parallel edit elsewhere returns 409 Conflict and you’ll be prompted to reconcile.

How the Kanban overlays on the Canva

When you switch to the Canva, the universal course graph renders with your Kanban state layered as overlay:

  • Courses you have marked taken light up in the “taken” hue.
  • Courses currently on a future term are highlighted as “planned”.
  • Edges your Kanban makes reachable take on the unlocked styling.

The overlay never claims a course is satisfied based on visual reachability — overlays are always driven by backend academic_result payloads. See Frontend compute boundary (ADR 0021).

Marking a course “taken”

Mark a course taken when you have completed it (passed, official transcript reflects it). uwwoe treats taken entries as known facts for all requirement evaluations.

  • If you marked something taken by mistake, flip it back to planned and re-evaluate. Nothing is logged.
  • Grades are optional. If you do not supply a grade, requirements with grade thresholds will report unknown for that part — see Status meanings.

What the Kanban does not do

  • It does not register you for courses. uwwoe has no Quest integration.
  • It does not validate that you can fit a course into your timetable — there is no section data.
  • It does not predict offering frequency. If MATH 999 is in the catalog but has not run for five years, uwwoe will still let you put it on a future term.
  • It does not auto-import prior coursework. Quest does — uwwoe does not. You add what you have taken yourself.

Conflicts on the board

If two Kanban entries conflict — for example, both members of an antirequisite pair are marked taken — Advisory will flag a conflict status against any requirement that depends on either course, with a source reference to the antirequisite rule. See Status meanings.

Saving and recovering

Your plan persists automatically as you edit. To export a portable JSON copy, hit “Export” in the Kanban menu — this calls GET /api/v1/state/current/export, returns Cache-Control: no-store, and does not write any new state-event row.

To hard-delete your plan, hit “Delete plan” and confirm. See Your plan.