- Code conventions: naming, comments, modules and file placement.
- Architecture: application boundaries and the data model.
- Catalogue operations: importing, reviewing, editing and publishing catalogue records.
- Environment template: required settings, optional services and defaults.
- Database setup: local services and database operations.
- Contributing: workflow and verification requirements.
- Catalogue automation: scheduled discovery and syncing, what a scheduled run may and may not do, and the journeys that prove it.
- Redesign plan: the prerequisite modelling, student interface and campus map projects still to come.
Keep current operating instructions in the guides and label proposals explicitly. When work lands, move lasting decisions into the relevant guide and remove the superseded proposal or migration notes. Git history retains the old documents; do not maintain a separate archive or present old verification as current.