Operations

How the company does things, what to do when they break, and what we depend on.

Directory	What it is
sops/	Repeatable processes involving people
runbooks/	What to do when something is broken, followed under pressure
incidents/	Severity definitions, and a postmortem per real incident
vendors/	What we pay for, who owns the account, what data it holds
obligations.md	Recurring duties: VAT, payroll, renewals
exam-year-timeline.html	The 2026/27 teaching and exam calendar for the six programmes we cover

The line between an SOP and a runbook is who is reading it and when. An SOP is read once to learn a process. A runbook is read at the worst possible moment, so it carries exact commands, expected results, and a rollback.

The exam year timeline

exam-year-timeline.html is the academic calendar we plan against. It shows every course we cover in 2026/27, when it is taught, and when its exams, mid-terms and resits fall, across five Erasmus programmes and one at UvA. Open it in a browser; it needs no server and no network.

It is a generated artefact rather than a written document, so it carries no review cadence and the documentation sweep does not track it. Regenerate it from the source timetables when a university republishes its calendar. UvA had only published semester 1 when this was built, so its spring dates are missing and should be added once available.

Not here: the technical procedure itself. Deploys, releases and backups are documented in erudeon/passtheyear/docs/. The files here say who does it, when, and with whose approval, then link.