Codex (legacy Hub data layer) · codex
Owner directive (2026-06-13), deprecating. "Just mind the date of each resource, notion is old, cortex doesnt exist, codex neither. go and review the concepts." [src: wiki/development/prompts-archive/by-topic/knowledge-management-and-concept-modeling.md:402]
Content
Codex is the legacy structured-data layer of the Mainland Hub. Canon position: "the owner stated codex is not a first-class concept of the canonical model. The structured-data role it plays is subsumed by the genome + the Atomic-Holon knowledge unit" (holon) [src: wiki/reference/legacy-systems.md:22].
Historical meaning: in the CLand-era notes, "CODEX = Datasets" — "REGION CODEX (Datasets) CORTEX (Permissions)" [src: wiki/GLOSSARY.md:577]. The D3 PAD resolution still echoes the era: a PAD holds "raw data + Cortext preferences + encrypted Vault keys" [src: HOS-Webdoc/web/src/data/hos-specification.ts:517] — see cortex.
Code reality (still live, deliberately): CODEX_SYSTEM in lib/districts/hub/systems/codex.ts, the Hub route app/mainland/hub/codex/page.tsx, the registry system id codex under the Mainland Hub [src: HOS-Webdoc/web/src/lib/hos-architecture.ts:174], and many data/instance-routes/*-routes.json entries. In the Mainland Hub it is the "Data Available — structured data repository" system [src: wiki/reference/legacy-systems.md:24].
Handling rule (build-forward): "retain the Hub surface; document it as the legacy data layer being unified under the Genome / knowledge index. Not removed. (Part of flaw #1.)" [src: wiki/reference/legacy-systems.md:26] A Datan encountering codex in code or routes must read it as legacy surface area whose canonical successor is the genome plus the holon knowledge index — never introduce new Codex-dependent designs.
Variants
| # | Definition (verbatim) | Source | Ruling | Status |
|---|---|---|---|---|
| A | "CODEX (Datasets)" — the CLand-era historical meaning | [src: wiki/GLOSSARY.md:577] | Historical; superseded by OWNER-2026-06-13 ("codex" is not a concept of the canonical model) | deprecated |
| B | "Data Available — structured data repository" — the live Hub system | [src: wiki/reference/legacy-systems.md:24] [src: HOS-Webdoc/web/src/lib/hos-architecture.ts:174] | Legacy-but-live per the build-forward rule; role subsumed by genome + Atomic-Holon knowledge unit | deprecated (live in code) |
Composition
- uses: — (legacy leaf; its data role is absorbed upstream)
- used-by: districts (Mainland Hub still ships the surface), genome (canonical successor for structured data), cortex (sibling legacy layer, same Hub)