MIT new University — Edinburgh-shaped governance with three-body separation, a federated sub-unit model, and a 1k → 10k student trajectory across five years. The structure is what the ERP wires onto.
Same separation of powers as Edinburgh's Court / Senate / Principal, renamed for the Indian-trust context. Three bodies because separation defends against the failure mode common in young Indian private universities — one strong founder making every call.
Strategy, finance, fiduciary. Appoints the Vice-Chancellor.
Curriculum, degree awards, academic standards.
Day-to-day executive — hires, budget execution, operations.
MIT new University
└── College of Sciences and Engineering
├── School of Computing and Data Sciences (~400 students)
└── School of Engineering (~600 students)
Departments are not formally constituted at year 1 — too small, adds bureaucracy. Each School has a Head of School + Director of Teaching.
MIT new University
├── College of Sciences and Engineering
│ ├── School of Computing and Data Sciences
│ ├── School of Engineering
│ └── School of Natural Sciences (NEW)
└── College of Humanities and Social Sciences (NEW college)
├── School of Design (NEW)
├── School of Business (NEW)
└── School of Liberal Arts (NEW)
Full Edinburgh shape: 3 colleges, 8-10 schools, ~12 departments under schools, plus cross-cutting research institutes that draw faculty from multiple schools (Climate & Sustainability, AI Safety, Indian-Language NLP). Departments hold discretionary budgets within school allocations.
Detail: STRUCTURE_PROPOSAL_v1.md §2 (source in private repo).
vice_chancellor registrar chief_finance_officer chief_hr_officer controller_of_examinations it_admin internal_auditor
dean associate_dean_academic associate_dean_research head_of_school director_of_teaching director_of_research school_administrator head_of_department
lab_admin mess_manager hostel_warden library_admin placement_officer cultural_coordinator
Per user direction (2026-04-15): every unit inside MIT new University can have its own ERP slice, or a role-activated subset of the central ERP. Ravikiran-style. The central registry has read-everything for compliance + reporting; sub-units have full control within their slice.
Examples: each lab gets a lab-ops portal; each mess gets a dining portal; each hostel gets a residential portal; each school gets an academic-administration portal. All run from one CATALYST codebase, with per-unit scoping enforced by the spine.
Implementation contract in STRUCTURE_PROPOSAL_v1.md §4 (source in private repo).
Three converging metaphors describe what the editor will be:
→ Visual mockup (open in browser)
Editor scope is delegated by role — superadmin sees everything; HR can move people between schools; HoS can edit within their school; HoD edits within their department; sub-unit admins manage their own slice. Detail: STRUCTURE_PROPOSAL_v1.md §9 (source in private repo).
Spend + people-flow + academic approval routes; mapped to CATALYST's approval_steps primitive.
Devolution rules, year-1/3/5 envelopes, per-school + sub-unit allocations, reserve policy.
Three-tier retention, role × tier read-access matrix, PII classification, hash-chain integrity.
Four-thread playbook (infrastructure / people / ERP / regulatory) with T-90 → T+90 offsets.
Project scope, ownership, cadence, what's in/out of scope.
The full structure design — source of truth for every other governance doc.
The CATALYST product is being commercialized through a separate Pvt Ltd company, founded by Vishvajeet (CTO + product) and Nikita (co-founder, commercial). MIT new University is the anchor customer; MIT ADT, MITWPU, and external vendors follow. Detail: PLAN.md §B (source in private repo).