University Handover — Isolated Documentation
This folder contains all documentation that is specific to handing over the system to the university (or a single target institution).
Why It’s Isolated
- Re-branching: To reuse the same codebase and main docs for another client (different institution, white-label, SaaS), delete this entire
docs/university/folder. The rest of the repo stays client-agnostic. - Single place: Everything about “we’re building for / handing over to the uni” lives here. The rest of
docs/is generic (architecture, guides, strategy, todo) and not tied to the university.
Folder Structure (Domain Separation)
| Folder | Purpose |
|---|---|
| handover/ | What we are handing over: checklist, scope, commitment (e.g. 12-month support), and how we run the handover. |
| our-planning/ | Our strategy and plans about the university: positioning, presentation, “real win,” if rejected, portability Q&A. Files here are for us; some are to be removed once the institution accepts and takes over (see removal guide). |
| for-institution/ | Documents intended for the institution: training, admin guide, support, branding, etc. |
| Removal and leave-as-is | See our-planning/files-to-remove-and-leave.md: which files to remove when they take over (our plans about them) and which to leave as-is (or hand to them). |
Quick Links
- Handover checklist — What we hand over and in what order.
- Positioning and strategy — How to present, what the real win is, 12-month commitment, portability.
- Files to remove / leave as-is — When they accept and take over: what to delete from this folder vs what stays or goes to them.
- For the institution — Index of docs we give to the university.
Relation to Main Docs
- Root docs (
docs/outside this folder): Architecture, guides, strategy, roadmap, vision, todo, security — written in a generic way (no “university” or “we’re building for them”). They describe the system and how to run/evolve it for any deployment. - Institutional readiness docs:
docs/institutional-readiness/capture the institutional gap assessment and hardening plan (SSO, governance, DR, ownership) that apply to any serious university/enterprise deployment. - This folder: Everything that is specific to this handover (this university, our plans about them, files for them, and what to remove when re-branching).
Deleting docs/university/ does not break the main documentation; it only removes institution-specific handover material. The institutional readiness docs stay as the generic review pack for future institutions.