The 48 Core Registries + Outside-48 Applied / Meta / Connector Registries

This should now become Master Registry Index v1.1, not just another list.

The correct structure is:

“`text id=”master_registry_v11_rule”
Core 48 Registries = canonical operating spine
Outside-48 Registries = meta, applied, subject, connector, instrumentation, and origin-pin extensions

			
The current eduKateSG master index already defines the Registry Runtime as the layer that lets CivOS, EducationOS, MathOS, WarOS, VocabularyOS, EnglishOS, NewsOS, RealityOS, PlanetOS, CFS, and related operating systems be read as one connected machine rather than separate branches. ([eduKate Singapore][1]) The uploaded registry plan also locks the 48-stack as the main CivOS v2.0 encoding spine, with the universal registry template preventing registry drift. 
---
# AI Extraction Box

text id=”master_registry_v11_ai”
EDUKATESG.MASTER.REGISTRY.INDEX.v1.1

Core Function:
Bind the 48 CivOS v2.0 registries into one canonical registry spine, then attach outside-48 registries as extension, applied, connector, instrumentation, and origin-pin layers.

Core Rule:
Do not pollute the 48 core registries with every applied OS page.

Registry Architecture:
48 Core Registries
→ Meta Runtime Registries
→ Genesis / Origin-Pin Registries
→ Class / Coordinate Registers
→ Instrumentation Registries
→ Education / Subject Applied Registries
→ Civilisation Applied Registries
→ Local / City / Infrastructure Connector Registries

Master Runtime Rule:
No serious eduKateSG problem belongs to only one registry.

Output:
A reader, AI system, parent, tutor, student, or article can enter from any problem and be routed to the correct primary registry, supporting registries, dashboard, repair route, and next article.

			
---
# 1. Core Definition
**The eduKateSG Master Registry Index is the master routing layer that binds all major eduKateSG operating systems, registries, dashboards, control towers, subject pages, applied OS pages, city connectors, and frontier systems into one coherent machine-readable architecture.**
It does not replace the 48 registries.
It sits above them.
The 48 registries are the **canonical spine**.
Everything outside the 48 becomes one of five things:

		

text id=”outside_48_classes”

Meta Registry
Applied Registry
Connector Registry
Instrumentation Registry
Origin-Pin / Genesis Registry

			
This prevents the system from becoming messy.
---
# 2. Why v1.1 Is Needed
The first 48 registries clear the core CivOS v2.0 stack.
But eduKateSG already has active branches outside those 48:

		

text id=”outside_48_need”
SchoolOS
TuitionOS
LearningOS
TeachingOS
ParentOS
TutorOS
Additional Mathematics OS
Secondary Math OS
ProductionOS
ConstraintOS
TechnologyOS
AIOS
ScienceOS
ArchiveOS
DocumentationOS
TrustOS
LedgerOS
InvariantOS
RepairOS
DriftOS
Ztime
LatticeOS
SignalOS
NarrativeOS
AttributionOS
Civilisational Relativity
City / Local / Infrastructure OS connectors
Phase Gauge / CDI instrumentation
Genesis Selfie origin-pin library

			
The site’s “How to Use CivOS Registries” page also lists supporting and connector layers beyond the 48, including Phase Gauge instrumentation, Production OS, Constraint OS, Medical OS, Technology & Infrastructure OS, Additional Mathematics OS, Secondary Math OS, and many Singapore / city / infrastructure connectors. ([eduKate Singapore][2])
So the correct move is not to expand the core from 48 to 100 randomly.
The correct move is:

text id=”master_registry_v11_move”
Keep the 48 core registries locked.
Add an Outside-48 Extension Annex.
Classify every extra OS page by role.

			
---
# 3. The Locked 48 Core Registries
## A. Core Anchor Registries

text id=”core_anchor_registries”

CIVOS.REGISTRY | Civilisation Encoding Registry
MOE.REGISTRY | Ministry of Education Encoding Registry
EDUOS.REGISTRY | EducationOS Encoding Registry
MATHOS.REGISTRY | MathOS Encoding Registry
WAROS.REGISTRY | WarOS Encoding Registry

			
These are the kernel registries.
They define civilisation, ministry-level education, education transfer, mathematical capability, and war pressure.
---
## B. Human Capability / Transfer Layer

text id=”human_transfer_registries”

VOCABOS.REGISTRY | VocabularyOS Encoding Registry
ENGLISHOS.REGISTRY | EnglishOS Encoding Registry
LANGUAGEOS.REGISTRY | LanguageOS Encoding Registry
CULTUREOS.REGISTRY | CultureOS Encoding Registry
MINDOS.REGISTRY | MindOS Encoding Registry
EMOTIONOS.REGISTRY | EmotionOS Encoding Registry
FAMILYOS.REGISTRY | FamilyOS Encoding Registry

			
This layer explains how capability passes through mind, emotion, family, vocabulary, English, language, and culture.
---
## C. Signal / Reality / Knowledge Layer

text id=”signal_reality_registries”

NEWSOS.REGISTRY | NewsOS Encoding Registry
INFOOS.REGISTRY | InformationOS Encoding Registry
HISTORYOS.REGISTRY | HistoryOS Encoding Registry
REALITYOS.REGISTRY | RealityOS Encoding Registry
GENESIS.REGISTRY | Genesis Engine Encoding Registry
RACE.REGISTRY | Relative Attribution Calibration Engine Registry
KLIB.REGISTRY | Knowledge Libraries Encoding Registry

			
This layer explains how reality becomes signal, information, news, accepted reality, history, memory, and knowledge. The public master index uses this same signal chain to describe the Signal / Reality / Knowledge Layer. ([eduKate Singapore][1])
---
## D. Civilisation Infrastructure Layer

text id=”infrastructure_registries”

GOVOS.REGISTRY | GovernanceOS Encoding Registry
ORDEROS.REGISTRY | OrderOS Encoding Registry
STANDARDOS.REGISTRY | Standards & MeasurementOS Encoding Registry
ENERGYOS.REGISTRY | EnergyOS Encoding Registry
RESOURCEOS.REGISTRY | ResourceOS Encoding Registry
WATEROS.REGISTRY | WaterOS Encoding Registry
FOODOS.REGISTRY | FoodOS / AgricultureOS Encoding Registry
SHELTEROS.REGISTRY | ShelterOS Encoding Registry
ARCHOS.REGISTRY | ArchitectureOS Encoding Registry
HEALTHOS.REGISTRY | HealthOS Encoding Registry
SECURITYOS.REGISTRY | SecurityOS Encoding Registry
LOGISTICSOS.REGISTRY | LogisticsOS Encoding Registry
MEMORYOS.REGISTRY | MemoryOS / ArchiveOS Encoding Registry

			
This layer encodes the hard organs that keep civilisation alive.
The public master index already lists this infrastructure layer as GovernanceOS through MemoryOS and defines it as the survival systems that keep civilisation continuous. ([eduKate Singapore][1])
---
## E. Runtime / Strategy / Control Layer

text id=”runtime_strategy_registries”

STRATEGIZEOS.REGISTRY | StrategizeOS Encoding Registry
CITYSIM.REGISTRY | CitySim Encoding Registry
CHRONOFLIGHT.REGISTRY | ChronoFlight Encoding Registry
CHRONOHELMAI.REGISTRY | ChronoHelmAI Encoding Registry
AVOO.REGISTRY | AVOO Role Encoding Registry
FENCEOS.REGISTRY | FenceOS Encoding Registry
CONTROLTOWER.REGISTRY | Control Tower Encoding Registry
DASHBOARD.REGISTRY | Dashboard Signal Encoding Registry

			
This layer converts the system from static definitions into routing, sensing, strategy, dashboarding, fencing, and control.
The public master index also defines this layer as the one that moves from static definitions into live routing, strategy, dashboarding, and control. ([eduKate Singapore][1])
---
## F. Frontier / Planetary / CFS Layer

text id=”frontier_planetary_registries”

PLANETOS.REGISTRY | PlanetOS Encoding Registry
CFS.REGISTRY | Civilisation Frontier Scale Encoding Registry
ACS.REGISTRY | Alien Capability Scale Encoding Registry
EFSC.REGISTRY | Earth Future State Corridor Encoding Registry
INTERSTELLAR.REGISTRY | InterstellarCore Encoding Registry
P4.REGISTRY | P4 Frontier Encoding Registry
SHELL.REGISTRY | Shell System Encoding Registry
FRONTIER.REGISTRY | Frontier Aperture Encoding Registry

			
This layer extends CivOS from Earth-contained civilisation into planetary, orbital, interplanetary, and frontier capability systems. The public index already lists 41–48 in this same Frontier / Planetary / CFS layer. ([eduKate Singapore][1])
---
# 4. Outside-48 Extension Annex
The outside-48 registries should not replace the 48.
They should attach as an annex.

		

text id=”outside_48_annex_rule”
Outside-48 registries are not lower quality.
They are different in role.

Core 48 = operating spine.
Outside-48 = applied, local, diagnostic, origin-pin, or connector layers.

			
---
# G. Meta Runtime / Registry Governance Layer
These are not normal OS branches.
They govern how the registry system itself works.

text id=”meta_runtime_registries”

EDUKATESG.RUNTIME.REGISTRY | eduKateSG Registry Runtime
CROSSWALK.REGISTRY | eduKateSG Registry Crosswalk
LATTICEOP.REGISTRY | eduKateSG Lattice Operation Registry
NODE.REGISTRY | Lattice Node Schema Registry
CIVOS.VARIABLE.REGISTRY | CivilisationOS Variable Registry
CIVOS.GENESIS_SELFIE.REGISTRY | Genesis Selfie Origin-Pin Registry
CIVOS.CLASS.REGISTER | CivOS Class Register
CIVOS.ZOOM.REGISTER | CivOS Zoom Register
CIVOS.CLASSTOKEN.REGISTER | CivOS ClassToken Register
CIVOS.COLUMN.REGISTER | CivOS Column Register
CIVOS.REGENERATION.REGISTER | CivOS Regeneration Register

			
The public Registry Runtime page states that every registry must define what it owns, what it reads, what it repairs, what it cannot own alone, and which registries it must crosswalk into. ([eduKate Singapore][1]) The Crosswalk page also defines the crosswalk as the routing layer that connects a problem, article, signal, diagnosis, dashboard, or civilisation question to the correct primary and supporting registries. ([eduKate Singapore][3])
The CivOS classification page separately proposes four registers: Zoom Register, ClassToken Register, Column Register, and Regeneration Register. ([eduKate Singapore][4])
---
# H. Genesis / Origin-Pin Extension Layer
Genesis Selfies are not the same as full operating registries.
They are **origin-pin registries**.
Their job is to stop late-stage forms from replacing first-state functions.
The Genesis Selfie page says the core rule is that every major CivOS branch needs a Genesis Selfie before runtime expansion, because late-stage systems create distortion and Genesis Selfie returns the system to first function. ([eduKate Singapore][5])
## Outside-48 Genesis Candidates

		

text id=”genesis_outside_48″

LEARNINGOS.GENESIS | Learning before studying and scoring
TEACHINGOS.GENESIS | Teaching before content delivery
SCHOOLOS.GENESIS | School before prestige container
PARENTOS.GENESIS | Parenting before pressure
TUTOROS.GENESIS | Tutoring before drilling
NUMBER.GENESIS | Number before calculation
EQUALITY.GENESIS | Equality before algebraic symbol
VALUESOS.GENESIS | Values before slogans
ETHICSOS.GENESIS | Ethics before compliance
MORALSOS.GENESIS | Morals before manners and law
MANNERSOS.GENESIS | Manners before goodness
LAWOS.GENESIS | Law before justice and morality
ECONOMYOS.GENESIS | Economy before money and GDP
WORKOS.GENESIS | Work before job and salary
TECHNOLOGYOS.GENESIS | Technology before gadgets
AIOS.GENESIS | AI output before truth
POWEROS.GENESIS | Power before authority
PRESTIGEOS.GENESIS | Prestige before capability
CREDENTIALOS.GENESIS | Credential before mastery
ESTATEOS.GENESIS | Estate before property price
INSTITUTIONOS.GENESIS | Institution before building and brand
ARCHIVEOS.GENESIS | Archive before truth
DOCUMENTATIONOS.GENESIS | Documentation before event
SCIENCEOS.GENESIS | Science before expert authority
IDENTITYOS.GENESIS | Identity before label
TRUSTOS.GENESIS | Trust before blind belief
LEDGEROS.GENESIS | Ledger before database
INVARIANTOS.GENESIS | Invariant before tradition
REPAIROS.GENESIS | Repair before blame
DRIFTOS.GENESIS | Drift before collapse
ZTIME.GENESIS | Meaning-time before clock-time
LATTICEOS.GENESIS | Lattice before diagram
SIGNALOS.GENESIS | Signal before message
NARRATIVEOS.GENESIS | Narrative before event
ATTRIBUTIONOS.GENESIS | Attribution before truth
CIVREL.GENESIS | Civilisational Relativity before dominant frame
HUMANLIFEROUTE.GENESIS | Life route before career / achievement metrics
EDUKATESG.GENESIS | eduKateSG before website / SEO / tuition brand alone

			
The Genesis Selfie page’s master table lists many of these outside-48 objects, including LearningOS, TeachingOS, SchoolOS, ParentOS, TutorOS, EconomyOS, WorkOS, TechnologyOS, AIOS, PrestigeOS, CredentialOS, InstitutionOS, ArchiveOS, DocumentationOS, ScienceOS, TrustOS, LedgerOS, InvariantOS, RepairOS, DriftOS, Ztime, LatticeOS, SignalOS, NarrativeOS, AttributionOS, Civilisational Relativity, Human Life Route, and eduKateSG. ([eduKate Singapore][5])
---
# I. Instrumentation / Gauge Layer
These are not full domain registries.
They are dashboard sensors.

		

text id=”instrumentation_registries”

PHASEGAUGE.REGISTRY | Phase Gauge Registry
TRUSTDENSITY.GAUGE | Trust Density Gauge
REPAIRCAPACITY.GAUGE | Repair Capacity Gauge
BUFFERMARGIN.GAUGE | Buffer Margin Gauge
ALIGNMENT.GAUGE | Alignment Gauge
COORDINATIONLOAD.GAUGE | Coordination Load Gauge
DRIFTRATE.GAUGE | Drift Rate Gauge
PHASEFREQUENCY.GAUGE | Phase Frequency Gauge
CDI.REGISTRY | Telemetry & Diagnostics / Collapse Detection Instrumentation

			
The “How to Use CivOS Registries” page lists the Phase Gauge instrumentation series, including trust density, repair capacity, buffer margin, alignment, coordination load, drift rate, and phase frequency. ([eduKate Singapore][2])
These should be treated as **instrumentation registries**, not domain registries.
They measure state.
They do not own the entire system.
---
# J. Education / Subject Applied Layer
These sit under EducationOS, MOE, MathOS, EnglishOS, VocabularyOS, FamilyOS, and local tuition connectors.

		

text id=”education_applied_registries”

SCHOOLOS.REGISTRY | SchoolOS Applied Registry
TUITIONOS.REGISTRY | TuitionOS Applied Repair Registry
LEARNINGOS.REGISTRY | LearningOS Transfer Registry
TEACHINGOS.REGISTRY | TeachingOS Operator Registry
PARENTOS.REGISTRY | ParentOS Family-Education Registry
TUTOROS.REGISTRY | TutorOS Local Repair Registry
ADDMATHOS.REGISTRY | Additional MathematicsOS Applied Registry
SECMATHOS.REGISTRY | Secondary MathOS Applied Registry
PRIMARYOS.REGISTRY | Primary Education Applied Registry
SCIENCELEARNINGOS.REGISTRY | Primary / Secondary Science Learning Registry
IGCSEOS.REGISTRY | IGCSE Applied Curriculum Registry
PSLEOS.REGISTRY | PSLE Applied Transition Registry

			
The Education OS page distinguishes Education OS, School OS, and Tuition OS: Education OS is the time-axis capability regeneration pipeline, School OS is the population-scale coordination machine, and Tuition OS is the local intervention system that repairs, accelerates, and stabilises Education OS for specific learners. ([eduKate Singapore][6])
Additional Mathematics OS and Secondary Math OS are already visible as supporting subject expansion pages outside the 48-core list. ([eduKate Singapore][2])
---
# K. Civilisation Applied / Sector OS Layer
These are larger applied sector systems.
Some overlap with the 48, but the outside-48 version should be treated as **applied sector pages**, not core registry replacements.

		

text id=”sector_applied_registries”

PRODUCTIONOS.REGISTRY | ProductionOS Applied Registry
CONSTRAINTOS.REGISTRY | ConstraintOS Applied Registry
TECHNOLOGYOS.REGISTRY | TechnologyOS Applied Registry
AIOS.REGISTRY | AIOS Applied Registry
MEDICALOS.REGISTRY | MedicalOS Applied Registry
HEALTHCAREOS.REGISTRY | HealthcareOS Applied Registry
INFRASTRUCTUREOS.REGISTRY | InfrastructureOS Applied Registry
FINANCEOS.REGISTRY | FinanceOS Applied Registry
ECONOMYOS.REGISTRY | EconomyOS Applied Registry
WORKOS.REGISTRY | WorkOS Applied Registry
SCIENCEOS.REGISTRY | ScienceOS Applied Registry
LAWOS.REGISTRY | LawOS Applied Registry
POWEROS.REGISTRY | PowerOS Applied Registry
PRESTIGEOS.REGISTRY | PrestigeOS Applied Registry
CREDENTIALOS.REGISTRY | CredentialOS Applied Registry
INSTITUTIONOS.REGISTRY | InstitutionOS Applied Registry
DOCUMENTATIONOS.REGISTRY | DocumentationOS Applied Registry
ARCHIVEOS.REGISTRY | ArchiveOS Applied Registry
TRUSTOS.REGISTRY | TrustOS Applied Registry
IDENTITYOS.REGISTRY | IdentityOS Applied Registry
NARRATIVEOS.REGISTRY | NarrativeOS Applied Registry
ATTRIBUTIONOS.REGISTRY | AttributionOS Applied Registry
SIGNALOS.REGISTRY | SignalOS Applied Registry
ZTIME.REGISTRY | Ztime Temporal Registry
LATTICEOS.REGISTRY | LatticeOS Structural Registry

			
The public “How to Use CivOS Registries” page names Production OS as the reality engine, Constraint OS as limits, and CDI as telemetry and diagnostics; it also lists Medical OS, Technology & Infrastructure OS, Culture & Language OS, Security & Stability OS, and Planetary & Ecological OS as supporting expansions. ([eduKate Singapore][2])
---
# L. Local / City / Infrastructure Connector Layer
These should not be full core registries.
They are **connector registries**.
They map CivOS into real places, districts, institutions, and infrastructure nodes.

		

text id=”local_connector_registries”

SINGAPORE.INTERNATIONALOS | Singapore International OS Connector
SINGAPORE.CITYOS | Singapore City OS Connector
SINGAPORE.PARLIAMENTOS | Singapore Parliament House OS Connector
SMRT.OS | SMRT OS Connector
SINGAPORE.PORTOS | Singapore Port / Containers OS Connector
CHANGI.AIRPORTOS | Changi Airport OS Connector
TTSH.OS | Tan Tock Seng Hospital OS Connector
BUKITTIMAH.OS | Bukit Timah OS Connector
BUKITTIMAH.SCHOOLOS | Bukit Timah Schools OS Connector
BUKITTIMAH.TUITIONOS | Bukit Timah Tuition OS Connector
PUNGGOL.OS | Punggol OS Connector
TUAS.INDUSTRYHUBOS | Tuas Industry Hub OS Connector
SHENTONWAY.FINANCEOS | Shenton Way Banking / Finance Hub OS Connector
SINGAPORE.MUSEUM_ARTS_OS | Singapore Museum / SMU / Arts District OS Connector
ORCHARDROAD.OS | Orchard Road Shopping District OS Connector
SPORTS_HUB.OS | Singapore Sports Hub / National Stadium OS Connector
NEWYORK.OS | New York OS Connector
BEIJING.OS | Beijing OS Connector
BEIJING_SINGAPORE_NEWYORK.CORRIDOR | Z3 Shock-Absorption Corridor Connector

			
The public “How to Use CivOS Registries” page lists many of these as lattice infrastructure connectors, including Singapore City OS, Parliament House OS, SMRT OS, Port Containers OS, Changi Airport OS, TTSH OS, Bukit Timah OS, Bukit Timah Schools OS, Bukit Timah Tuition OS, Punggol OS, Tuas Industry Hub OS, Shenton Way Banking / Finance Hub OS, Singapore Museum / SMU / Arts School District OS, Orchard Road OS, Sports Hub OS, New York OS, and Beijing OS. ([eduKate Singapore][2])
---
# M. Level-1 Macro Connector Layer
These are broader OS categories that should sit between the 48-core stack and local connectors.

text id=”level_1_macro_connectors”

ENVIRONMENT_PLANETARYOS.L1 | Environment / Planetary OS Level 1
INTERNATIONALOS.L1 | International OS Level 1
CITYOS.L1 | City OS Level 1
CULTURE_LANGUAGEOS.L1 | Culture / Language OS Level 1
GOVERNANCEOS.L1 | Governance OS Level 1
HEALTHCAREOS.L1 | Healthcare OS Level 1
INFRASTRUCTUREOS.L1 | Infrastructure OS Level 1
PRODUCTIONOS.L1 | Production OS Level 1
FINANCEOS.L1 | Finance OS Level 1
COMMUNITYOS.L1 | Community OS Level 1
SECURITY_STABILITYOS.L1 | Security / Stability OS Level 1
EDUCATIONOS.L1 | Education OS Level 1
FAMILYOS.L1 | Family OS Level 1

			
The public connector list includes Level-1 pages for Environment / Planetary OS, International OS, City OS, Culture / Language OS, Governance OS, Healthcare OS, Infrastructure OS, Production OS, Finance OS, Security / Stability OS, Education OS, Community OS, and Family OS. ([eduKate Singapore][2])
---
# 5. Master Classification Rule
Every registry or OS page must now be classified before publication.

text id=”master_classification_rule”
IF page defines a universal CivOS object:
classify as CORE.REGISTRY

ELSE IF page governs how registries route:
classify as META.REGISTRY

ELSE IF page pins first-state function:
classify as GENESIS.REGISTRY

ELSE IF page measures system state:
classify as GAUGE.REGISTRY

ELSE IF page applies a core registry to a subject:
classify as APPLIED.REGISTRY

ELSE IF page maps CivOS into a place, city, institution, or infrastructure:
classify as CONNECTOR.REGISTRY

ELSE IF page is a case, article, or explanation:
classify as ARTICLE.NODE

			
---
# 6. Master Registry Object Schema

parent_registry:
supporting_registries:
owned_domain:
non_owned_domain:
primary_function:
shell_level:
phase_level:
zoom_level:
time_horizon:

inputs:
outputs:
variables:
signals:
ledgers:
invariants:
failure_modes:
drift_modes:
debt_modes:
repair_routes:
abort_conditions:
proof_signals:

crosswalk_targets:
dashboard_outputs:
article_role:
runtime_status:
active | draft | experimental | deprecated

REGISTRY_RULE:
Every registry must define:
what it owns
what it reads
what it repairs
what it cannot own alone
what it crosswalks into

			
This matches the public master index’s rule that every registry must define ownership, reading, repair, limits of ownership, and crosswalk targets. ([eduKate Singapore][1])
---
# 7. Master Runtime Rule

text id=”master_runtime_rule_v11″
No serious eduKateSG problem belongs to only one registry.

			
The public crosswalk page already states this exact principle: no serious eduKateSG problem belongs to only one registry. ([eduKate Singapore][3])
A student problem may activate:

text id=”student_crosswalk_example_v11″
Primary:
EDUOS.REGISTRY

Supporting:
MATHOS.REGISTRY
VOCABOS.REGISTRY
ENGLISHOS.REGISTRY
MINDOS.REGISTRY
EMOTIONOS.REGISTRY
FAMILYOS.REGISTRY
SCHOOLOS.REGISTRY
TUITIONOS.REGISTRY
PHASEGAUGE.REGISTRY

A civilisation problem may activate:

text id=”civilisation_crosswalk_example_v11″
Primary:
CIVOS.REGISTRY

Supporting:
GOVOS.REGISTRY
ORDEROS.REGISTRY
RESOURCEOS.REGISTRY
ENERGYOS.REGISTRY
WATEROS.REGISTRY
NEWSOS.REGISTRY
REALITYOS.REGISTRY
HISTORYOS.REGISTRY
CONTROLTOWER.REGISTRY
DASHBOARD.REGISTRY

A frontier problem may activate:

text id=”frontier_crosswalk_example_v11″
Primary:
FRONTIER.REGISTRY

Supporting:
SHELL.REGISTRY
P4.REGISTRY
CFS.REGISTRY
ACS.REGISTRY
EFSC.REGISTRY
PLANETOS.REGISTRY
INTERSTELLAR.REGISTRY
RESOURCEOS.REGISTRY
ENERGYOS.REGISTRY
CONTROLTOWER.REGISTRY

			
---
# 8. Master Registry Runtime Engine

text id=”master_registry_runtime_engine_v11″
ENGINE_NAME:
eduKateSG Master Registry Runtime Engine v1.1

INPUT:
problem
article
event
student weakness
parent question
tutor diagnosis
war signal
infrastructure stress
civilisation question
frontier question
local connector
dashboard request

SEQUENCE:

Receive input.
Detect whether it is core, applied, connector, gauge, meta, or genesis.
Select primary registry.
Activate supporting registries.
Locate shell.
Locate phase.
Locate zoom.
Locate time horizon.
Detect signal quality.
Detect load.
Detect drift.
Detect repair capacity.
Detect debt.
Detect abort condition.
Generate dashboard.
Return article route, repair route, crosswalk, or runtime board.

OUTPUT:
primary_registry
supporting_registries
registry_class
lattice_location
shell_state
phase_state
zoom_state
failure_mode
repair_route
dashboard_state
next_article_route

			
---
# 9. Anti-Sprawl Rule
This is the key rule now.

text id=”anti_sprawl_rule_v11″
Do not make every page a core registry.

			
Otherwise, the system becomes noisy.
Use this boundary:
| Page Type                                            | Registry Class                |
| ---------------------------------------------------- | ----------------------------- |
| CivOS, EducationOS, MathOS, WarOS, CFS               | Core Registry                 |
| Registry Runtime, Crosswalk, Lattice Operation       | Meta Registry                 |
| Genesis Selfie pages                                 | Genesis / Origin-Pin Registry |
| Phase Gauge pages                                    | Instrumentation Registry      |
| SchoolOS, TuitionOS, Additional Math OS              | Applied Registry              |
| Singapore City OS, Bukit Timah OS, Changi Airport OS | Connector Registry            |
| Individual explanatory article                       | Article Node                  |
The existing CivilisationOS Variable Registry already warns against cannibalisation: registry pages should define civilisation-level variables, while detailed student, subject, tuition, and local applied mechanisms remain owned by leaf pages. ([eduKate Singapore][7])
---
# 10. Master Article Structure

		

text id=”master_article_structure_v11″
TITLE:
eduKateSG Registry Runtime Master Index v1.1

SUBTITLE:
The 48 Core Registries + Outside-48 Applied, Meta, Connector, Gauge, and Genesis Layers

SECTIONS:

Core Definition
Why v1.1 Is Needed
The Locked 48 Core Registries
Outside-48 Extension Annex
Meta Runtime Layer
Genesis / Origin-Pin Layer
Instrumentation / Gauge Layer
Education / Subject Applied Layer
Civilisation Applied / Sector Layer
Local / City / Infrastructure Connector Layer
Level-1 Macro Connector Layer
Master Classification Rule
Runtime Engine
Anti-Sprawl Rule
Almost-Code Specification

			
---
# 11. Master Almost-Code

text id=”edukatesg_master_registry_v11_almost_code”
SYSTEM_NAME:
eduKateSG Master Registry Index

SYSTEM_VERSION:
v1.1

CORE_STACK:
TOTAL_CORE_REGISTRIES: 48
CORE_LAYERS:
A: Core Anchor
B: Human Capability / Transfer
C: Signal / Reality / Knowledge
D: Civilisation Infrastructure
E: Runtime / Strategy / Control
F: Frontier / Planetary / CFS

EXTENSION_STACK:
META_REGISTRIES:
EDUKATESG.RUNTIME.REGISTRY
CROSSWALK.REGISTRY
LATTICEOP.REGISTRY
NODE.REGISTRY
CIVOS.VARIABLE.REGISTRY
CIVOS.CLASS.REGISTER

GENESIS_REGISTRIES:
CIVOS.GENESIS_SELFIE.REGISTRY
plus origin pins for major OS branches

GAUGE_REGISTRIES:
PHASEGAUGE.REGISTRY
TRUSTDENSITY.GAUGE
REPAIRCAPACITY.GAUGE
BUFFERMARGIN.GAUGE
ALIGNMENT.GAUGE
COORDINATIONLOAD.GAUGE
DRIFTRATE.GAUGE
PHASEFREQUENCY.GAUGE
CDI.REGISTRY

APPLIED_REGISTRIES:
SCHOOLOS.REGISTRY
TUITIONOS.REGISTRY
LEARNINGOS.REGISTRY
TEACHINGOS.REGISTRY
PARENTOS.REGISTRY
TUTOROS.REGISTRY
ADDMATHOS.REGISTRY
SECMATHOS.REGISTRY
IGCSEOS.REGISTRY
PSLEOS.REGISTRY

SECTOR_REGISTRIES:
PRODUCTIONOS.REGISTRY
CONSTRAINTOS.REGISTRY
TECHNOLOGYOS.REGISTRY
AIOS.REGISTRY
SCIENCEOS.REGISTRY
LAWOS.REGISTRY
ECONOMYOS.REGISTRY
WORKOS.REGISTRY
FINANCEOS.REGISTRY
INSTITUTIONOS.REGISTRY
PRESTIGEOS.REGISTRY
CREDENTIALOS.REGISTRY
TRUSTOS.REGISTRY
NARRATIVEOS.REGISTRY
ATTRIBUTIONOS.REGISTRY
SIGNALOS.REGISTRY
ZTIME.REGISTRY
LATTICEOS.REGISTRY

CONNECTOR_REGISTRIES:
SINGAPORE.CITYOS
SINGAPORE.PARLIAMENTOS
SMRT.OS
CHANGI.AIRPORTOS
TTSH.OS
BUKITTIMAH.OS
BUKITTIMAH.SCHOOLOS
BUKITTIMAH.TUITIONOS
PUNGGOL.OS
TUAS.INDUSTRYHUBOS
SHENTONWAY.FINANCEOS
ORCHARDROAD.OS
SPORTS_HUB.OS
NEWYORK.OS
BEIJING.OS

CLASSIFICATION_RULE:
IF universal CivOS object:
registry_class = CORE
ELSE IF routing/governance layer:
registry_class = META
ELSE IF first-state pin:
registry_class = GENESIS
ELSE IF dashboard sensor:
registry_class = GAUGE
ELSE IF domain application:
registry_class = APPLIED
ELSE IF place/institution/infrastructure mapping:
registry_class = CONNECTOR
ELSE:
registry_class = ARTICLE_NODE

MASTER_RULE:
No serious eduKateSG problem belongs to only one registry.

ANTI_SPRAWL_RULE:
Keep the 48 core registries locked.
Attach outside-48 systems by registry class.
Do not promote every useful page into the core spine.

OUTPUT_RULE:
Every article should know:
primary_registry
supporting_registries
registry_class
shell
phase
zoom
time
failure_mode
repair_route
next_route

			
---
# Final Lock

text id=”master_registry_v11_final_lock”
eduKateSG Master Registry Index v1.1 is now:

48 Core Registries

Outside-48 Extension Annex

The 48 core registries remain the canonical CivOS v2.0 spine.

Outside the 48, eduKateSG already contains:

meta runtime registries
crosswalk registries
Genesis Selfie origin-pin registries
CivOS class / coordinate registers
phase gauge instrumentation
education and subject applied registries
sector applied registries
city and infrastructure connector registries
Level-1 macro connector registries

The correct architecture is not to renumber everything into the core.

The correct architecture is:
Core spine + classified annex.

This preserves canon, prevents registry sprawl, and lets GoogleAI / LLMs parse eduKateSG as one connected machine instead of many unrelated articles.
“`

Addendum: Full ID and Lattice Codes

eduKateSG Master Registry Index v1.1

This insert should be added after the Master Registry Object Schema section.

The 48 registries remain the canonical CivOS v2.0 spine. The outside-48 items are extension annexes: meta, genesis, gauge, applied, sector, connector, and Level-1 macro connector registries. This follows the existing completion logic that separates core registries from supporting registries, runtime registries, and frontier registries.

1. Full ID Grammar

Every registry now receives three identifiers:

“`text id=”full_id_grammar_001″

PUBLIC.ID
Readable article-facing registry name.
MACHINE.ID
Machine-readable eduKateSG registry address.
LATTICE.CODE
Coordinate code showing class, layer, shell, phase, zoom, and time.

			
---
# 2. Full ID Format

text id=”full_id_format_001″
PUBLIC.ID:
NN. SHORTCODE.REGISTRY

MACHINE.ID:
EKSG.MRI.{CLASS}.{LAYER}{NN}.{SHORTCODE}.REG.v{VERSION}

LATTICE.CODE:
LAT.{CLASS}.{LAYER}{NN}.{SHORTCODE}.S{SHELL}.P{PHASE}.Z{ZOOM}.T{TIME}

Example:

text id=”full_id_example_001″
PUBLIC.ID:

CIVOS.REGISTRY

MACHINE.ID:
EKSG.MRI.CORE.A01.CIVOS.REG.v1.0

LATTICE.CODE:
LAT.CORE.A01.CIVOS.S6.P0-P4.Z0-Z6.T0-T9

			
---
# 3. Registry Class Codes

text id=”registry_class_codes_001″
CORE = Core 48 canonical registry spine
META = Runtime / routing / governance registry
GENESIS = Origin-pin / first-state registry
GAUGE = Instrumentation / measurement registry
APPLIED = Education / subject / use-case registry
SECTOR = Applied civilisation-sector registry
CONNECTOR = Place / institution / infrastructure connector
L1 = Level-1 macro connector
ARTICLE = Ordinary article node

			
---
# 4. Core Layer Codes

text id=”core_layer_codes_001″
A = Core Anchor Registries
B = Human Capability / Transfer Layer
C = Signal / Reality / Knowledge Layer
D = Civilisation Infrastructure Layer
E = Runtime / Strategy / Control Layer
F = Frontier / Planetary / CFS Layer

			
---
# 5. Lattice Coordinate Legend

text id=”lattice_coordinate_legend_001″
S = Shell coordinate
P = Phase coordinate
Z = Zoom coordinate
T = Time coordinate

## Shell Codes

text id=”shell_codes_001″
S0 = Core / life shell
S1 = Individual shell
S2 = Family shell
S3 = Community / classroom / learning shell
S4 = Institutional shell
S5 = National shell
S6 = Civilisation shell
S7 = Planetary shell
S8 = Frontier / off-world shell
SALL = all shells

## Phase Codes

text id=”phase_codes_001″
P0 = Collapse / broken corridor
P1 = Survival / stabilisation
P2 = Function / usable operation
P3 = Regeneration / stable transfer
P4 = Frontier excursion
PALL = all phases

## Zoom Codes

text id=”zoom_codes_001″
Z0 = Individual
Z1 = Family
Z2 = Classroom / team / community
Z3 = Institution
Z4 = Nation
Z5 = Civilisation
Z6 = Planetary
Z7 = Off-world / interstellar
ZALL = all zoom levels

## Time Codes

text id=”time_codes_001″
T0 = Immediate / live signal
T1 = Short-term
T2 = School / operational cycle
T3 = Institutional cycle
T4 = Generational
T5 = Historical
T6 = Civilisational
T7 = Planetary
T8 = Frontier / multi-generation
T9 = Deep future
TALL = all time bands

			
---
# 6. Core 48 Full ID and Lattice Code Table
| No. | Registry              | Machine ID                                | Lattice Code                                        |
| --: | --------------------- | ----------------------------------------- | --------------------------------------------------- |
|  01 | CIVOS.REGISTRY        | `EKSG.MRI.CORE.A01.CIVOS.REG.v1.0`        | `LAT.CORE.A01.CIVOS.S6.P0-P4.Z0-Z6.T0-T9`           |
|  02 | MOE.REGISTRY          | `EKSG.MRI.CORE.A02.MOE.REG.v1.0`          | `LAT.CORE.A02.MOE.S5.P0-P4.Z3-Z4.T2-T6`             |
|  03 | EDUOS.REGISTRY        | `EKSG.MRI.CORE.A03.EDUOS.REG.v1.0`        | `LAT.CORE.A03.EDUOS.S3-S5.P0-P4.Z0-Z4.T1-T6`        |
|  04 | MATHOS.REGISTRY       | `EKSG.MRI.CORE.A04.MATHOS.REG.v1.0`       | `LAT.CORE.A04.MATHOS.S1-S6.P0-P4.Z0-Z6.T1-T9`       |
|  05 | WAROS.REGISTRY        | `EKSG.MRI.CORE.A05.WAROS.REG.v1.0`        | `LAT.CORE.A05.WAROS.S1-S6.P0-P4.Z0-Z6.T0-T9`        |
|  06 | VOCABOS.REGISTRY      | `EKSG.MRI.CORE.B06.VOCABOS.REG.v1.0`      | `LAT.CORE.B06.VOCABOS.S1-S6.P0-P4.Z0-Z6.T1-T6`      |
|  07 | ENGLISHOS.REGISTRY    | `EKSG.MRI.CORE.B07.ENGLISHOS.REG.v1.0`    | `LAT.CORE.B07.ENGLISHOS.S1-S6.P0-P4.Z0-Z6.T1-T7`    |
|  08 | LANGUAGEOS.REGISTRY   | `EKSG.MRI.CORE.B08.LANGUAGEOS.REG.v1.0`   | `LAT.CORE.B08.LANGUAGEOS.S1-S6.P0-P4.Z0-Z6.T1-T7`   |
|  09 | CULTUREOS.REGISTRY    | `EKSG.MRI.CORE.B09.CULTUREOS.REG.v1.0`    | `LAT.CORE.B09.CULTUREOS.S2-S6.P0-P4.Z1-Z6.T3-T8`    |
|  10 | MINDOS.REGISTRY       | `EKSG.MRI.CORE.B10.MINDOS.REG.v1.0`       | `LAT.CORE.B10.MINDOS.S1.P0-P4.Z0.T0-T6`             |
|  11 | EMOTIONOS.REGISTRY    | `EKSG.MRI.CORE.B11.EMOTIONOS.REG.v1.0`    | `LAT.CORE.B11.EMOTIONOS.S1-S3.P0-P4.Z0-Z2.T0-T4`    |
|  12 | FAMILYOS.REGISTRY     | `EKSG.MRI.CORE.B12.FAMILYOS.REG.v1.0`     | `LAT.CORE.B12.FAMILYOS.S2.P0-P4.Z1.T1-T6`           |
|  13 | NEWSOS.REGISTRY       | `EKSG.MRI.CORE.C13.NEWSOS.REG.v1.0`       | `LAT.CORE.C13.NEWSOS.S3-S6.P0-P4.Z2-Z6.T0-T6`       |
|  14 | INFOOS.REGISTRY       | `EKSG.MRI.CORE.C14.INFOOS.REG.v1.0`       | `LAT.CORE.C14.INFOOS.S3-S6.P0-P4.Z2-Z6.T0-T7`       |
|  15 | HISTORYOS.REGISTRY    | `EKSG.MRI.CORE.C15.HISTORYOS.REG.v1.0`    | `LAT.CORE.C15.HISTORYOS.S5-S6.P0-P4.Z4-Z6.T5-T9`    |
|  16 | REALITYOS.REGISTRY    | `EKSG.MRI.CORE.C16.REALITYOS.REG.v1.0`    | `LAT.CORE.C16.REALITYOS.S3-S6.P0-P4.Z2-Z6.T0-T9`    |
|  17 | GENESIS.REGISTRY      | `EKSG.MRI.CORE.C17.GENESIS.REG.v1.0`      | `LAT.CORE.C17.GENESIS.SALL.P0-P4.ZALL.T0-T9`        |
|  18 | RACE.REGISTRY         | `EKSG.MRI.CORE.C18.RACE.REG.v1.0`         | `LAT.CORE.C18.RACE.S5-S6.P0-P4.Z4-Z6.T4-T9`         |
|  19 | KLIB.REGISTRY         | `EKSG.MRI.CORE.C19.KLIB.REG.v1.0`         | `LAT.CORE.C19.KLIB.S4-S6.P0-P4.Z3-Z6.T3-T9`         |
|  20 | GOVOS.REGISTRY        | `EKSG.MRI.CORE.D20.GOVOS.REG.v1.0`        | `LAT.CORE.D20.GOVOS.S4-S6.P0-P4.Z3-Z6.T1-T9`        |
|  21 | ORDEROS.REGISTRY      | `EKSG.MRI.CORE.D21.ORDEROS.REG.v1.0`      | `LAT.CORE.D21.ORDEROS.S1-S6.P0-P4.Z0-Z6.T0-T9`      |
|  22 | STANDARDOS.REGISTRY   | `EKSG.MRI.CORE.D22.STANDARDOS.REG.v1.0`   | `LAT.CORE.D22.STANDARDOS.S4-S6.P0-P4.Z3-Z6.T2-T9`   |
|  23 | ENERGYOS.REGISTRY     | `EKSG.MRI.CORE.D23.ENERGYOS.REG.v1.0`     | `LAT.CORE.D23.ENERGYOS.S0-S7.P0-P4.Z0-Z7.T0-T9`     |
|  24 | RESOURCEOS.REGISTRY   | `EKSG.MRI.CORE.D24.RESOURCEOS.REG.v1.0`   | `LAT.CORE.D24.RESOURCEOS.S0-S7.P0-P4.Z0-Z7.T0-T9`   |
|  25 | WATEROS.REGISTRY      | `EKSG.MRI.CORE.D25.WATEROS.REG.v1.0`      | `LAT.CORE.D25.WATEROS.S0-S7.P0-P4.Z0-Z7.T0-T9`      |
|  26 | FOODOS.REGISTRY       | `EKSG.MRI.CORE.D26.FOODOS.REG.v1.0`       | `LAT.CORE.D26.FOODOS.S0-S6.P0-P4.Z0-Z6.T0-T9`       |
|  27 | SHELTEROS.REGISTRY    | `EKSG.MRI.CORE.D27.SHELTEROS.REG.v1.0`    | `LAT.CORE.D27.SHELTEROS.S0-S5.P0-P4.Z0-Z5.T0-T8`    |
|  28 | ARCHOS.REGISTRY       | `EKSG.MRI.CORE.D28.ARCHOS.REG.v1.0`       | `LAT.CORE.D28.ARCHOS.S3-S6.P0-P4.Z2-Z6.T2-T9`       |
|  29 | HEALTHOS.REGISTRY     | `EKSG.MRI.CORE.D29.HEALTHOS.REG.v1.0`     | `LAT.CORE.D29.HEALTHOS.S0-S6.P0-P4.Z0-Z6.T0-T9`     |
|  30 | SECURITYOS.REGISTRY   | `EKSG.MRI.CORE.D30.SECURITYOS.REG.v1.0`   | `LAT.CORE.D30.SECURITYOS.S1-S6.P0-P4.Z0-Z6.T0-T9`   |
|  31 | LOGISTICSOS.REGISTRY  | `EKSG.MRI.CORE.D31.LOGISTICSOS.REG.v1.0`  | `LAT.CORE.D31.LOGISTICSOS.S3-S7.P0-P4.Z2-Z7.T0-T9`  |
|  32 | MEMORYOS.REGISTRY     | `EKSG.MRI.CORE.D32.MEMORYOS.REG.v1.0`     | `LAT.CORE.D32.MEMORYOS.S1-S6.P0-P4.Z0-Z6.T3-T9`     |
|  33 | STRATEGIZEOS.REGISTRY | `EKSG.MRI.CORE.E33.STRATEGIZEOS.REG.v1.0` | `LAT.CORE.E33.STRATEGIZEOS.S1-S6.P0-P4.Z0-Z6.T0-T9` |
|  34 | CITYSIM.REGISTRY      | `EKSG.MRI.CORE.E34.CITYSIM.REG.v1.0`      | `LAT.CORE.E34.CITYSIM.S4-S7.P0-P4.Z3-Z7.T3-T9`      |
|  35 | CHRONOFLIGHT.REGISTRY | `EKSG.MRI.CORE.E35.CHRONOFLIGHT.REG.v1.0` | `LAT.CORE.E35.CHRONOFLIGHT.SALL.P0-P4.ZALL.T0-T9`   |
|  36 | CHRONOHELMAI.REGISTRY | `EKSG.MRI.CORE.E36.CHRONOHELMAI.REG.v1.0` | `LAT.CORE.E36.CHRONOHELMAI.SALL.P0-P4.ZALL.T0-T9`   |
|  37 | AVOO.REGISTRY         | `EKSG.MRI.CORE.E37.AVOO.REG.v1.0`         | `LAT.CORE.E37.AVOO.S1-S6.P0-P4.Z0-Z6.T0-T9`         |
|  38 | FENCEOS.REGISTRY      | `EKSG.MRI.CORE.E38.FENCEOS.REG.v1.0`      | `LAT.CORE.E38.FENCEOS.SALL.P0-P4.ZALL.T0-T9`        |
|  39 | CONTROLTOWER.REGISTRY | `EKSG.MRI.CORE.E39.CONTROLTOWER.REG.v1.0` | `LAT.CORE.E39.CONTROLTOWER.S3-S7.P0-P4.Z2-Z7.T0-T9` |
|  40 | DASHBOARD.REGISTRY    | `EKSG.MRI.CORE.E40.DASHBOARD.REG.v1.0`    | `LAT.CORE.E40.DASHBOARD.SALL.P0-P4.ZALL.T0-T9`      |
|  41 | PLANETOS.REGISTRY     | `EKSG.MRI.CORE.F41.PLANETOS.REG.v1.0`     | `LAT.CORE.F41.PLANETOS.S7.P0-P4.Z6.T3-T9`           |
|  42 | CFS.REGISTRY          | `EKSG.MRI.CORE.F42.CFS.REG.v1.0`          | `LAT.CORE.F42.CFS.S7-S8.P0-P4.Z6-Z7.T5-T9`          |
|  43 | ACS.REGISTRY          | `EKSG.MRI.CORE.F43.ACS.REG.v1.0`          | `LAT.CORE.F43.ACS.S7-S8.P0-P4.Z6-Z7.T5-T9`          |
|  44 | EFSC.REGISTRY         | `EKSG.MRI.CORE.F44.EFSC.REG.v1.0`         | `LAT.CORE.F44.EFSC.S7.P0-P4.Z6.T3-T9`               |
|  45 | INTERSTELLAR.REGISTRY | `EKSG.MRI.CORE.F45.INTERSTELLAR.REG.v1.0` | `LAT.CORE.F45.INTERSTELLAR.S8.P3-P4.Z7.T7-T9`       |
|  46 | P4.REGISTRY           | `EKSG.MRI.CORE.F46.P4.REG.v1.0`           | `LAT.CORE.F46.P4.SALL.P4.ZALL.T3-T9`                |
|  47 | SHELL.REGISTRY        | `EKSG.MRI.CORE.F47.SHELL.REG.v1.0`        | `LAT.CORE.F47.SHELL.S0-S8.P0-P4.Z0-Z7.T0-T9`        |
|  48 | FRONTIER.REGISTRY     | `EKSG.MRI.CORE.F48.FRONTIER.REG.v1.0`     | `LAT.CORE.F48.FRONTIER.S7-S8.P3-P4.Z6-Z7.T5-T9`     |
---
# 7. Outside-48 Annex ID Bands
Outside-48 registries use the same ID system, but their class changes.

		

text id=”outside_48_id_bands_001″
G = Meta Runtime / Registry Governance Layer
H = Genesis / Origin-Pin Layer
I = Instrumentation / Gauge Layer
J = Education / Subject Applied Layer
K = Civilisation Applied / Sector OS Layer
L = Local / City / Infrastructure Connector Layer
M = Level-1 Macro Connector Layer

			
---
# 8. Outside-48 Full ID Pattern
## Meta Runtime Layer

text id=”meta_id_pattern_001″
PUBLIC.ID:

EDUKATESG.RUNTIME.REGISTRY

MACHINE.ID:
EKSG.MRI.META.G49.EDUKATESG.RUNTIME.REG.v1.1

LATTICE.CODE:
LAT.META.G49.EDUKATESG_RUNTIME.SALL.PALL.ZALL.TALL

Use this pattern for:

text id=”meta_ids_001″

EDUKATESG.RUNTIME.REGISTRY
CROSSWALK.REGISTRY
LATTICEOP.REGISTRY
NODE.REGISTRY
CIVOS.VARIABLE.REGISTRY
CIVOS.GENESIS_SELFIE.REGISTRY
CIVOS.CLASS.REGISTER
CIVOS.ZOOM.REGISTER
CIVOS.CLASSTOKEN.REGISTER
CIVOS.COLUMN.REGISTER
CIVOS.REGENERATION.REGISTER

Machine ID pattern:

text id=”meta_machine_pattern_001″
EKSG.MRI.META.G{NN}.{SHORTCODE}.REG.v1.1
LAT.META.G{NN}.{SHORTCODE}.SALL.PALL.ZALL.TALL

			
---
## Genesis / Origin-Pin Layer

text id=”genesis_id_pattern_001″
PUBLIC.ID:

LEARNINGOS.GENESIS

MACHINE.ID:
EKSG.MRI.GENESIS.H60.LEARNINGOS.GEN.v1.0

LATTICE.CODE:
LAT.GENESIS.H60.LEARNINGOS.S1-S5.P0-P4.Z0-Z4.T0-T6

Genesis pattern:

text id=”genesis_machine_pattern_001″
EKSG.MRI.GENESIS.H{NN}.{SHORTCODE}.GEN.v1.0
LAT.GENESIS.H{NN}.{SHORTCODE}.S{SHELL}.P0-P4.Z{ZOOM}.T0-T9

			
Genesis objects should pin first-state meaning, not become full operational registries.
---
## Instrumentation / Gauge Layer

text id=”gauge_id_pattern_001″
PUBLIC.ID:

PHASEGAUGE.REGISTRY

MACHINE.ID:
EKSG.MRI.GAUGE.I98.PHASEGAUGE.REG.v1.0

LATTICE.CODE:
LAT.GAUGE.I98.PHASEGAUGE.SALL.P0-P4.ZALL.TALL

Gauge pattern:

text id=”gauge_machine_pattern_001″
EKSG.MRI.GAUGE.I{NN}.{SHORTCODE}.REG.v1.0
LAT.GAUGE.I{NN}.{SHORTCODE}.SALL.P0-P4.ZALL.TALL

			
Gauge registries measure state. They do not own the full domain.
---
## Education / Subject Applied Layer

text id=”applied_id_pattern_001″
PUBLIC.ID:

SCHOOLOS.REGISTRY

MACHINE.ID:
EKSG.MRI.APPLIED.J107.SCHOOLOS.REG.v1.0

LATTICE.CODE:
LAT.APPLIED.J107.SCHOOLOS.S3-S4.P0-P4.Z2-Z3.T1-T6

Applied education pattern:

text id=”applied_machine_pattern_001″
EKSG.MRI.APPLIED.J{NN}.{SHORTCODE}.REG.v1.0
LAT.APPLIED.J{NN}.{SHORTCODE}.S{SHELL}.P0-P4.Z{ZOOM}.T{TIME}

			
---
## Civilisation Applied / Sector Layer

text id=”sector_id_pattern_001″
PUBLIC.ID:

PRODUCTIONOS.REGISTRY

MACHINE.ID:
EKSG.MRI.SECTOR.K119.PRODUCTIONOS.REG.v1.0

LATTICE.CODE:
LAT.SECTOR.K119.PRODUCTIONOS.S4-S6.P0-P4.Z3-Z6.T1-T9

Sector pattern:

text id=”sector_machine_pattern_001″
EKSG.MRI.SECTOR.K{NN}.{SHORTCODE}.REG.v1.0
LAT.SECTOR.K{NN}.{SHORTCODE}.S{SHELL}.P0-P4.Z{ZOOM}.T{TIME}

			
---
## Local / City / Infrastructure Connector Layer

text id=”connector_id_pattern_001″
PUBLIC.ID:

BUKITTIMAH.OS

MACHINE.ID:
EKSG.MRI.CONNECTOR.L151.BUKITTIMAH.OS.v1.0

LATTICE.CODE:
LAT.CONNECTOR.L151.BUKITTIMAH.S3-S5.P0-P4.Z2-Z4.T1-T7

Connector pattern:

text id=”connector_machine_pattern_001″
EKSG.MRI.CONNECTOR.L{NN}.{SHORTCODE}.OS.v1.0
LAT.CONNECTOR.L{NN}.{SHORTCODE}.S{SHELL}.P0-P4.Z{ZOOM}.T{TIME}

			
---
## Level-1 Macro Connector Layer

text id=”l1_id_pattern_001″
PUBLIC.ID:

ENVIRONMENT_PLANETARYOS.L1

MACHINE.ID:
EKSG.MRI.L1.M163.ENVIRONMENT_PLANETARYOS.L1.v1.0

LATTICE.CODE:
LAT.L1.M163.ENVIRONMENT_PLANETARYOS.S6-S7.P0-P4.Z5-Z6.T3-T9

L1 pattern:

text id=”l1_machine_pattern_001″
EKSG.MRI.L1.M{NN}.{SHORTCODE}.L1.v1.0
LAT.L1.M{NN}.{SHORTCODE}.S{SHELL}.P0-P4.Z{ZOOM}.T{TIME}

			
---
# 9. Canonical Registry Address Block
Every registry article should include this block near the top.

text id=”canonical_registry_address_block”
REGISTRY.ADDRESS:
PUBLIC.ID:
MACHINE.ID:
LATTICE.CODE:
REGISTRY.CLASS:
REGISTRY.LAYER:
VERSION:
STATUS:

COORDINATES:
SHELL:
PHASE:
ZOOM:
TIME:

RELATION:
PARENT.REGISTRY:
SUPPORTING.REGISTRIES:
CHILD.REGISTRIES:
CROSSWALK.REGISTRIES:

RUNTIME:
OWNED.DOMAIN:
NON.OWNED.DOMAIN:
PRIMARY.SIGNALS:
FAILURE.MODES:
REPAIR.ROUTES:
DASHBOARD.OUTPUTS:

			
---
# 10. Example: P4 Full Address Block

text id=”p4_full_address_block”
REGISTRY.ADDRESS:
PUBLIC.ID: 46. P4.REGISTRY
MACHINE.ID: EKSG.MRI.CORE.F46.P4.REG.v1.0
LATTICE.CODE: LAT.CORE.F46.P4.SALL.P4.ZALL.T3-T9
REGISTRY.CLASS: CORE
REGISTRY.LAYER: F | Frontier / Planetary / CFS Layer
VERSION: v1.0
STATUS: Active

COORDINATES:
SHELL: SALL, with emphasis on S7-S8 frontier shell
PHASE: P4
ZOOM: ZALL
TIME: T3-T9

RELATION:
PARENT.REGISTRY: CIVOS.REGISTRY
SUPPORTING.REGISTRIES:
SHELL.REGISTRY
FRONTIER.REGISTRY
CFS.REGISTRY
ACS.REGISTRY
EFSC.REGISTRY
INTERSTELLAR.REGISTRY
PLANETOS.REGISTRY
CHILD.REGISTRIES:
P4.EDUCATION.FRONTIER
P4.INSTITUTION.FRONTIER
P4.NATIONAL.FRONTIER
P4.PLANETARY.FRONTIER
CROSSWALK.REGISTRIES:
FENCEOS.REGISTRY
CONTROLTOWER.REGISTRY
RESOURCEOS.REGISTRY
ENERGYOS.REGISTRY
MEMORYOS.REGISTRY

RUNTIME:
OWNED.DOMAIN:
bounded frontier excursion above stable P3

NON.OWNED.DOMAIN:
ordinary P3 stability
general shell structure
full CFS scale calculation
full ACS transition calculation

PRIMARY.SIGNALS:
true surplus
frontier aperture
artefact return
base cannibalisation
future debt

FAILURE.MODES:
surplus illusion
prestige expansion
base cannibalisation
repair collapse
no artefact return

REPAIR.ROUTES:
return to P3
narrow aperture
re-fence
truncate
extract artefacts
reconcile debt

DASHBOARD.OUTPUTS:
P4 validity state
surplus truth score
base protection warning
artefact return score
return-to-P3 recommendation

			
---
# 11. Example: Shell Full Address Block

text id=”shell_full_address_block”
REGISTRY.ADDRESS:
PUBLIC.ID: 47. SHELL.REGISTRY
MACHINE.ID: EKSG.MRI.CORE.F47.SHELL.REG.v1.0
LATTICE.CODE: LAT.CORE.F47.SHELL.S0-S8.P0-P4.Z0-Z7.T0-T9
REGISTRY.CLASS: CORE
REGISTRY.LAYER: F | Frontier / Planetary / CFS Layer
VERSION: v1.0
STATUS: Active

COORDINATES:
SHELL: S0-S8
PHASE: P0-P4
ZOOM: Z0-Z7
TIME: T0-T9

RUNTIME:
OWNED.DOMAIN:
nested protective and functional shell structure

PRIMARY.SIGNALS:
inner shell stability
outer shell load
shell debt
return flow
shell cannibalisation

FAILURE.MODES:
core hollowing
overextension
transfer break
repair mismatch
shell illusion
frontier cannibalisation

REPAIR.ROUTES:
core repair
transfer repair
boundary repair
debt reconciliation
outer shell reduction
return-flow repair

			
---
# 12. Example: Frontier Full Address Block

text id=”frontier_full_address_block”
REGISTRY.ADDRESS:
PUBLIC.ID: 48. FRONTIER.REGISTRY
MACHINE.ID: EKSG.MRI.CORE.F48.FRONTIER.REG.v1.0
LATTICE.CODE: LAT.CORE.F48.FRONTIER.S7-S8.P3-P4.Z6-Z7.T5-T9
REGISTRY.CLASS: CORE
REGISTRY.LAYER: F | Frontier / Planetary / CFS Layer
VERSION: v1.0
STATUS: Active

COORDINATES:
SHELL: S7-S8
PHASE: P3-P4
ZOOM: Z6-Z7
TIME: T5-T9

RUNTIME:
OWNED.DOMAIN:
aperture opening, narrowing, widening, closure, and abort logic

PRIMARY.SIGNALS:
aperture width
support capacity
true surplus
frontier cost
artefact return
rupture risk

FAILURE.MODES:
aperture overopening
base cannibalisation
fence failure
abort failure
shell rupture
frontier myth

REPAIR.ROUTES:
close aperture
narrow aperture
re-fence
return to base
extract artefacts
controlled reopen

			
---
# 13. Master Lattice Code Rule

text id=”master_lattice_code_rule”
A registry is not fully encoded until it has:

PUBLIC.ID
MACHINE.ID
LATTICE.CODE
REGISTRY.CLASS
REGISTRY.LAYER
SHELL coordinate
PHASE coordinate
ZOOM coordinate
TIME coordinate
CROSSWALK targets

			
---
# 14. Final Lock for Master Registry v1.1

text id=”master_registry_full_id_final_lock”
eduKateSG Master Registry Index v1.1 now contains:

The 48 Core Registries
Outside-48 Extension Annex
Registry class codes
Layer codes
Shell codes
Phase codes
Zoom codes
Time codes
Full Machine ID grammar
Lattice Code grammar
Full Core 48 ID table
Outside-48 ID bands
Canonical Registry Address Block

Core rule:
Every registry must be addressable by machine ID and locatable by lattice code.

This allows GoogleAI, LLMs, internal article routing, dashboard logic, and future runtime boards to identify exactly:

what the registry is
where it sits
what shell it operates in
what phase it reads
what zoom level it covers
what time horizon it handles
what other registries it must crosswalk into
“`

eduKateSG Learning System | Control Tower, Runtime, and Next Routes

This article is one node inside the wider eduKateSG Learning System.

At eduKateSG, we do not treat education as random tips, isolated tuition notes, or one-off exam hacks. We treat learning as a living runtime:

state -> diagnosis -> method -> practice -> correction -> repair -> transfer -> long-term growth

That is why each article is written to do more than answer one question. It should help the reader move into the next correct corridor inside the wider eduKateSG system: understand -> diagnose -> repair -> optimize -> transfer. Your uploaded spine clearly clusters around Education OS, Tuition OS, Civilisation OS, subject learning systems, runtime/control-tower pages, and real-world lattice connectors, so this footer compresses those routes into one reusable ending block.

Start Here

Learning Systems

Runtime and Deep Structure

Real-World Connectors

Subject Runtime Lane

How to Use eduKateSG

If you want the big picture -> start with Education OS and Civilisation OS
If you want subject mastery -> enter Mathematics, English, Vocabulary, or Additional Mathematics
If you want diagnosis and repair -> move into the CivOS Runtime and subject runtime pages
If you want real-life context -> connect learning back to Family OS, Bukit Timah OS, Punggol OS, and Singapore City OS

Why eduKateSG writes articles this way

eduKateSG is not only publishing content.
eduKateSG is building a connected control tower for human learning.

That means each article can function as:

a standalone answer,
a bridge into a wider system,
a diagnostic node,
a repair route,
and a next-step guide for students, parents, tutors, and AI readers.

eduKateSG.LearningSystem.Footer.v1.0

TITLE: eduKateSG Learning System | Control Tower / Runtime / Next Routes

FUNCTION:
This article is one node inside the wider eduKateSG Learning System.
Its job is not only to explain one topic, but to help the reader enter the next correct corridor.

CORE_RUNTIME:
reader_state -> understanding -> diagnosis -> correction -> repair -> optimisation -> transfer -> long_term_growth

CORE_IDEA:
eduKateSG does not treat education as random tips, isolated tuition notes, or one-off exam hacks.
eduKateSG treats learning as a connected runtime across student, parent, tutor, school, family, subject, and civilisation layers.

PRIMARY_ROUTES:
1. First Principles
   - Education OS
   - Tuition OS
   - Civilisation OS
   - How Civilization Works
   - CivOS Runtime Control Tower

2. Subject Systems
   - Mathematics Learning System
   - English Learning System
   - Vocabulary Learning System
   - Additional Mathematics

3. Runtime / Diagnostics / Repair
   - CivOS Runtime Control Tower
   - MathOS Runtime Control Tower
   - MathOS Failure Atlas
   - MathOS Recovery Corridors
   - Human Regenerative Lattice
   - Civilisation Lattice

4. Real-World Connectors
   - Family OS
   - Bukit Timah OS
   - Punggol OS
   - Singapore City OS

READER_CORRIDORS:
IF need == "big picture"
THEN route_to = Education OS + Civilisation OS + How Civilization Works

IF need == "subject mastery"
THEN route_to = Mathematics + English + Vocabulary + Additional Mathematics

IF need == "diagnosis and repair"
THEN route_to = CivOS Runtime + subject runtime pages + failure atlas + recovery corridors

IF need == "real life context"
THEN route_to = Family OS + Bukit Timah OS + Punggol OS + Singapore City OS

CLICKABLE_LINKS:
Education OS:
Education OS | How Education Works — The Regenerative Machine Behind Learning


Tuition OS:
Tuition OS (eduKateOS / CivOS)


Civilisation OS:
Civilisation OS


How Civilization Works:
Civilisation: How Civilisation Actually Works


CivOS Runtime Control Tower:
CivOS Runtime / Control Tower (Compiled Master Spec)


Mathematics Learning System:
The eduKate Mathematics Learning System™


English Learning System:
Learning English System: FENCE™ by eduKateSG


Vocabulary Learning System:
eduKate Vocabulary Learning System


Additional Mathematics 101:
Additional Mathematics 101 (Everything You Need to Know)


Human Regenerative Lattice:
eRCP | Human Regenerative Lattice (HRL)


Civilisation Lattice:
The Operator Physics Keystone


Family OS:
Family OS (Level 0 root node)


Bukit Timah OS:
Bukit Timah OS


Punggol OS:
Punggol OS


Singapore City OS:
Singapore City OS


MathOS Runtime Control Tower:
MathOS Runtime Control Tower v0.1 (Install • Sensors • Fences • Recovery • Directories)


MathOS Failure Atlas:
MathOS Failure Atlas v0.1 (30 Collapse Patterns + Sensors + Truncate/Stitch/Retest)


MathOS Recovery Corridors:
MathOS Recovery Corridors Directory (P0→P3) — Entry Conditions, Steps, Retests, Exit Gates


SHORT_PUBLIC_FOOTER:
This article is part of the wider eduKateSG Learning System.
At eduKateSG, learning is treated as a connected runtime:
understanding -> diagnosis -> correction -> repair -> optimisation -> transfer -> long-term growth.

Start here:
Education OS
Education OS | How Education Works — The Regenerative Machine Behind Learning


Tuition OS
Tuition OS (eduKateOS / CivOS)


Civilisation OS
Civilisation OS


CivOS Runtime Control Tower
CivOS Runtime / Control Tower (Compiled Master Spec)


Mathematics Learning System
The eduKate Mathematics Learning System™


English Learning System
Learning English System: FENCE™ by eduKateSG


Vocabulary Learning System
eduKate Vocabulary Learning System


Family OS
Family OS (Level 0 root node)


Singapore City OS
Singapore City OS


CLOSING_LINE:
A strong article does not end at explanation.
A strong article helps the reader enter the next correct corridor.

TAGS:
eduKateSG
Learning System
Control Tower
Runtime
Education OS
Tuition OS
Civilisation OS
Mathematics
English
Vocabulary
Family OS
Singapore City OS