Cortex (legacy Hub preference layer) · cortex
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
Cortex is the legacy personalization/preference layer of the Mainland Hub. Canon position: "likewise cortex is not a first-class canonical concept; personalization/preferences belong to the instance genome and centralized settings" [src: wiki/reference/legacy-systems.md:32].
Historical meaning: in the CLand-era notes, "CORTEX = Permissions" — "REGION CODEX (Datasets) CORTEX (Permissions)" [src: wiki/GLOSSARY.md:577]; legacy-systems records it as "Historically CORTEX = Permissions/preferences" [src: wiki/reference/legacy-systems.md:34]. The spelling "Cortext" survives inside the canonical D3 PAD definition — a pad holds "raw data + Cortext preferences + encrypted Vault keys" [src: HOS-Webdoc/web/src/data/hos-specification.ts:517] — a legacy echo to read as preference data carried by the PAD, not as a live Cortex dependency.
Code reality (still live, deliberately): CORTEX_SYSTEM in lib/districts/hub/systems/cortex.ts, the Hub route app/mainland/hub/cortex/page.tsx, plus app/bastion/codex-cortex/page.tsx, the registry system id cortex under the Mainland Hub [src: HOS-Webdoc/web/src/lib/hos-architecture.ts:179], lib/instance/commit-generator.ts and data files. In the Mainland Hub it is the "Preference Available — personalization" system [src: wiki/reference/legacy-systems.md:34].
Handling rule (build-forward): "retain the Hub surface; fold preference state into the Genome + centralized settings. Not removed. (Part of flaw #1.)" [src: wiki/reference/legacy-systems.md:36] Canonical successors for what Cortex held: preferences → the entity genome / genome-strand; access permissions → remotica Portals ("strict, precise Permissions" [src: wiki/engines/cognis-and-kernels.md:34]).
Variants
| # | Definition (verbatim) | Source | Ruling | Status |
|---|---|---|---|---|
| A | "CORTEX (Permissions)" — the CLand-era historical meaning | [src: wiki/GLOSSARY.md:577] | Historical; superseded by OWNER-2026-06-13 ("cortex doesnt exist"); the permission role now belongs to remotica Portals | deprecated |
| B | "Preference Available — personalization" — the live Hub system | [src: wiki/reference/legacy-systems.md:34] [src: HOS-Webdoc/web/src/lib/hos-architecture.ts:179] | Legacy-but-live per the build-forward rule; preference state folds into the genome + centralized settings | deprecated (live in code) |
Composition
- uses: — (legacy leaf; its roles are absorbed upstream)
- used-by: districts (Mainland Hub still ships the surface), genome / genome-strand (canonical successor for preferences), remotica (canonical successor for permissions), codex (sibling legacy layer, same Hub)