Why an operating system, not another website
A website presents an institution. An operating system runs one. Programmes, partners, applicants, and country engagements each carry rules, records, and decisions that must survive staff turnover and technology change. AIOS holds those rules in one governed layer instead of scattering them across tools.
What AIOS governs
Programmes, partners, applicants, and countries. Each entity has a defined lifecycle, an owner, a record of decisions, and a standard of evidence — so the same question receives the same institutional answer wherever it is asked.
Design before build
Architecture is specified before code. Business rules, workflows, and decision logic are written and reviewed as institutional documents; the platform then implements what has been agreed. This keeps the system auditable and prevents features from becoming policy by accident.
Relationship to the live platform
AIOS governs, integrates, and extends the platform already in production. Registration, course delivery, the AI tutor, and activity databases remain in place; AIOS gives them shared standards rather than replacing them.