Research University · Continuity

Built to be handed forward.

The ambition is an institution that can keep learning across generations. The method is to make its records readable, its infrastructure replaceable and its authority accountable.

Year 3000 is a design horizon, not a durability guarantee. This first continuity release adds export verification and an implementation plan. It does not certify archival preservation or disaster recovery.

My workspaceLearning and personal exportsSchool FoundryRepository connections

01

People and authority

One personal workspace; distinct accounts, institutional memberships and delegated agent permissions. Humans retain admissions, assessment and publication authority.

02

Institutional memory

Versioned publications, source provenance and personal record exports. Historical decisions retain their context; private learner data stays access-controlled.

03

Replaceable intelligence

Keep knowledge, citations, policies and evaluations outside model-specific prompts. Provider adapters and revocable, bounded agent jobs are the next infrastructure stage.

04

Portable operations

School blueprints and repository starters separate reusable design from learner records. Document storage contracts and prove migrations before replacing a host.

05

Recovery and succession

Independent encrypted backups, tested restoration, key succession and designated human custodians are required operational work; they are not yet verified.

Check a saved record

Choose a personal-record JSON export. Verification happens on your device; this tool does not upload the file. It checks page hashes, ownership consistency, pagination and duplicate records.

A matching hash is not a digital signature. Someone who changes a file can also replace its hash. Keep a trusted original separately.

What comes next

  1. Inventory databases, source objects and configurations; assign custodians and retention rules for each category.
  2. Create encrypted, access-controlled copies in an independent failure domain. Restore into an isolated environment and record measured recovery results.
  3. Version data contracts and build validated importers with dry runs, authorization checks and rollback.
  4. Separate AI providers from institutional knowledge. Test citations, permissions, cancellation and human approval before enabling autonomous actions.
  5. Run recurring recovery and accessibility exercises; document domain, identifier, funding and governance succession.

Readiness is demonstrated by successful exercises and maintained evidence, not a score or a promise.