Verified deployment · scale under review
Oasis
Infrastructure is only useful when knowledge can move through it.
A connected campus knowledge system joining infrastructure, archives, documentation, access and learning enablement.
What was true before the work?
Important academic and institutional knowledge was scattered across people, chats and fragile informal stores. Every cohort risked reconstructing the same context.
The loss was larger than missing files: students lost the ability to prepare, discover prior work, contribute and maintain a shared institutional record.
Not one feature. A working system.
CRISPR combined server infrastructure with curation, documentation, access, a previous-year question archive, Morphosis, a resource directory, workshops and interface evolution.
What can be defended today.
Public and organization-owned artifacts verify deployment and a later relaunch. Storage, usage, reliability, workshop delivery and individual contribution figures remain in evidence recovery.
Attribution
Credit the actual system.
Founder-era CRISPR team work with later relaunch and maintenance by successor cohorts. Individual roles remain under project-level verification.
After handover
What happened next?
Later cohorts publicly relaunched and extended the server experience. That continuity is evidence of the institution, not personal authorship by the original founder.
What we will not pretend to know.
No public scale or usage number is cleared for publication.
Private campus topology and student data must remain redacted.
Workshop delivery and project-level credits need primary records.
Capability demonstrated
A similar condition?
Bring us the operational knot.
We will begin with the workflow, the people and the constraint—not with a predetermined technology.