domain doctrineThe Codices
Codex 5 — Shared Data Model and API Boundaries
Data doctrine and the boundaries through which data moves.
- Authority rank
- 3
- Version
- v1.0
- Adopted
- unrecorded
- Held by
- Stewardship Office
- System
- SYS-12
Source · docs/codices/CODEX-5-data-and-apis.md
Canonical entities
One definition per concept, institution-wide. No division may redefine an entity for local convenience.
| Entity | Definition | Owner |
|---|---|---|
| Person | A human being known to the institution, once and forever | Technology |
| Identity | An authentication method bound to a Person | Technology |
| Organization | A company, university, government body, or partner | Technology |
| Membership | A Person's relationship to the institution or an Organization | Technology |
| Role | A scoped grant of authority to a Person | Technology |
| Capability | A named, describable human capability | Research Institute |
| CapabilityAssessment | Evidence that a Person demonstrated a Capability at a level | Academy |
| Credential | An issued, verifiable statement of demonstrated capability | Academy |
| Curriculum | School, program, course, module, lesson hierarchy | Academy |
| Enrolment | A Person's participation in a Curriculum unit or cohort | Academy |
| Cohort | A time-bound group moving through curriculum together | Academy |
| Engagement | An advisory relationship with an Organization or executive | Advisory |
| Publication | A research output with methodology and sources | Research Institute |
| Index | A published, versioned measurement series | Research Institute |
| Venture | A company in the incubator, accelerator, or studio | Ventures |
| Investment | A capital relationship to a Venture | Ventures |
| Artifact | Any produced work: submission, memo, model, paper | shared |
| Event | Something that happened, with actor, subject, and time | Technology |
| AuditRecord | An immutable record of a consequential action | Technology |
Normalization rules
- 1One canonical row per real-world thing; references, never copies.
- 2No entity duplicates another's fields for read convenience; derive or join.
- 3History is additive. Assessments, credentials, and index values are versioned rather than overwritten.
- 4Anonymized research data is a derived dataset, never the primary record.
- 5Deletion of a Person cascades to personal content and severs identity, while preserving anonymized aggregates and the fact of issued credentials.
- 6Every table carrying member data has row-level access rules and explicit grants. No table ships without them.
Relationships (abridged)
Person 1—n Identity
Person 1—n Membership n—1 Organization
Person 1—n Role (scoped)
Person 1—n Enrolment n—1 Curriculum unit
Person 1—n CapabilityAssessment n—1 Capability
Person 1—n Credential (Credential n—n Capability)
Organization 1—n Engagement n—n Person (advisors)
Person 1—n Venture (founder) Venture 1—n Investment n—1 Person/Organization
Publication n—n Capability Index 1—n IndexValue (versioned)
Everything 1—n Event 1—0..1 AuditRecordAPI boundaries
Division-owned service surfaces. A boundary must be stable before any integration is written against it.
| Boundary | Owner | Serves |
|---|---|---|
| Identity & Access | Technology | everything |
| Person & Membership | Technology | everything |
| Curriculum | Academy | Adaptive engine, enterprise cohorts, partners |
| Progress & Assessment | Academy | dashboards, credentialing |
| Credential & Verification | Academy | public verification, employers, partners |
| Engagement | Advisory | advisor tooling, enterprise dashboard |
| Publication & Index | Research Institute | public site, annual report, curriculum |
| Venture & Capital | Ventures | founder and investor portals |
| Knowledge Graph | Technology | Adaptive, Research, Tutor agent |
| Reporting & Analytics | Technology | executive, steward, enterprise dashboards |
| Audit | Technology | governance, security review |
Contract rules
- Public verification of credentials is a permanent, versioned, backwards-compatible endpoint. It must still resolve in twenty years.
- Internal contracts are typed and validated at the edge; no unvalidated input reaches a handler.
- Breaking changes require a version, a migration window, and a decision record.
- Webhooks and externally-called endpoints verify their caller before doing work.
- No hardcoded environment-specific values; configuration over custom code.