Files to Remove vs Leave When They Take Over or We Re-Branch
Use this when (a) the university accepts and takes over the system, or (b) we re-branch the repo for another client and want to drop all university-specific material.
When the Institution Accepts and Takes Over
Files / Folders to remove (our plans about them — no longer needed)
docs/university/our-planning/(this folder)positioning-and-strategy.md— our internal strategy and positioningfiles-to-remove-and-leave.md— this file (removal guide)README.md— index of our planning
- Optionally: the whole
docs/university/folder if we are fully handing over and not keeping a copy of “university-specific” docs in our tree. If we keep a fork for them, we might remove onlyour-planning/and leavehandover/andfor-institution/in their copy.
Files / Folders to leave as-is (handover and institutional docs)
docs/university/README.md— Explains the folder; can stay in their copy or be removed if we delete the whole folder for them.docs/university/handover/— Checklist and handover scope; useful for them to see what was agreed.docs/university/for-institution/— All docs we created for the institution (training, admin, support). Leave as-is; these are theirs.
Files for them (give or already in repo)
- Everything under
for-institution/(training, admin guide, support, branding, etc.). - Main docs they need to run the system:
docs/guides/(getting started, deployment, API),docs/architecture/(as needed),docs/security/overview.md. These live in the main docs tree and are generic; no need to move.
When We Re-Branch for Another Client (e.g. Delete All Uni Stuff)
Delete this entire folder
docs/university/— Delete the whole folder. The rest of the repo (code + main docs) is client-agnostic and works for any deployment.
Leave as-is (unchanged)
- All of
docs/outsideuniversity/— Architecture, guides, strategy, roadmap, vision, todo, security, institutional-readiness. They are written in a generic way and do not assume “the university” or “we’re building for them.” Thedocs/institutional-readiness/folder is the reusable institutional gap assessment + hardening plan for any future client. - Root project files — PHASES.md, CURRENT_PHASE.md, etc. — reference “handover” in a generic way and link to
docs/university/only for institution-specific steps; with the folder removed, those links 404 and you can point them to a new client-specific folder or remove the links.
Quick Reference
| Scenario | Remove | Leave / For them |
|---|---|---|
| They accept and take over | our-planning/ (positioning, strategy, this removal guide) | handover/, for-institution/; main docs as-is |
| We re-branch for new client | Entire docs/university/ folder | Rest of docs/ and repo; add new client folder if needed |