eduKate Singapore

VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Next useful routeCanonical hubHELP

ARTICLE 3 (V1.1 Canonical) — Bukit Timah Lattice Coordinate Standard (Definition Lock)

Three learners review open books together at a classroom table, with stacks of textbooks, stationery and a whiteboard in the bright room.

Definition Lock

Bukit Timah Lattice Coordinates are a function-first addressing system that encodes human interaction, regeneration, and flow using a stable grammar:

Region × Lane × Zoom × Role × Type × ID

They are not geographic maps. They are a substitute layer that makes systemic connections explicit and machine-readable, so the district can be indexed as a graph (nodes + binds + pipelines + sensors).

Canonical rule: the same coordinate string must be reused across all pages and linked as edges (“Binds To”).

Start Here:

Why Lattice Coordinates (Not Location Maps)

A location map encodes: where something is.
A lattice coordinate encodes: what it does, what it binds to, and how failure propagates.

This matters because districts don’t fail by losing a point on a map.
They fail by losing a function (school access, clinic entry, food buffers, payment flow, transport binds).

Canonical Grammar

Format

<REGION>.<LANE>.Z<ZOOM>.<ROLE>.<TYPE>.<ID>

Region (scope anchors)

  • BT — Bukit Timah (district system)
  • SG — Singapore (city system)
  • MY — Malaysia (cross-border system)
    (You can add more later. Do not start with more.)

Lane Codes (Function Lanes)

Use only these at the start. Do not rename.

CodeLaneMeaning
FAMFamilyhousehold regeneration + care + daily execution
EDUEducationschooling pipeline + tuition/enrichment support loops
TRNTransportbind layer: MRT/bus/road/walk routes and interfaces
FODFoodenergy/time buffers: hawker/supermarket/meals
MEDHealthcarerepair loops: clinic entry → hospital interface
FINFinancepayments, liquidity, affordability, trust routing
GOVGovernancezoning/policy/control loops

Zoom Codes (Nesting Level)

ZoomMeaningExample
Z0household / execution pocketa single family’s daily pipeline
Z1local clustera hawker + nearby clinics + bus stops
Z2districtBukit Timah as a system
Z3citySingapore as system
Z4cross-border/globalcauseway, regional logistics, global interfaces

Role Codes (Graph Roles)

RoleMeaningWhat it is
NNodean entity that performs work (school, clinic, bank, hawker)
BBinda connector/interface (MRT station, interchange, causeway)
PPipelineordered flow (PRI→SEC; clinic→hospital)
SSensora measure (TTC, queue time, load signature)

Type Codes (Controlled Vocabulary)

Keep the type list small and stable.

Transport (TRN)

  • MRT — MRT bind
  • BUS — bus bind
  • RD — road connector
  • INT — interchange

Education (EDU)

  • PRI — primary school node
  • SEC — secondary school node
  • TUI — tuition cluster node
  • SCH — schooling pipeline

Food (FOD)

  • HWK — hawker buffer node
  • SUP — supermarket buffer node

Healthcare (MED)

  • CLN — clinic entry node
  • HSP — hospital interface (usually Z3)

Finance (FIN)

  • BNK — bank node
  • PAY — payments interface (usually Z3)

Governance (GOV)

  • ZON — zoning/control node
  • POL — policy interface (usually Z3)

Family (FAM)

  • LIF — household life pipeline
  • TTC — TTC sensor pack

ID Rules (So the System Doesn’t Rot)

  • Use stable IDs: never recycle.
  • Prefer simple numeric IDs for nodes: 001–999.
  • For well-known binds you may use human-recognisable codes (e.g., DTL.06A) but keep the coordinate grammar unchanged.

The Required Edge Block (How Pages Connect)

Every lane page and node page must include a Binds To section listing outgoing edges as coordinates.

Example:

  • BT.TRN.Z2.B.MRT.DTL.06A → BT.EDU.Z2.N.PRI.001, BT.FOD.Z1.N.HWK.001, SG.TRN.Z3.B.AIR.CHG.001

This is how the lattice becomes an indexable graph.

The Required Sensor Block (How the Lattice Becomes Measurable)

Minimum viable sensor system:

  • TTC.TRN — time to nearest transport bind under peak load
  • TTC.FOD — time to food buffer
  • TTC.MED — time to clinic entry
  • TTC.EDU — time to school pipeline entry

Canonical sensor coordinate:

  • BT.FAM.Z0.S.TTC.001

Canonical Seed Set (v0.1)

These are your first stable entities. Reuse everywhere.

Transport binds

  • BT.TRN.Z2.B.MRT.DTL.06A
  • BT.TRN.Z2.B.MRT.DTL.07A

Education

  • BT.EDU.Z2.N.PRI.001
  • BT.EDU.Z2.N.SEC.001
  • BT.EDU.Z2.P.SCH.001

Food

  • BT.FOD.Z1.N.HWK.001
  • BT.FOD.Z1.N.SUP.001

Healthcare

  • BT.MED.Z1.N.CLN.001
  • BT.MED.Z1.N.CLN.002
  • SG.MED.Z3.B.HSP.001

Finance

  • BT.FIN.Z1.N.BNK.001
  • SG.FIN.Z3.B.PAY.001

Family + Sensors

  • BT.FAM.Z0.P.LIF.001
  • BT.FAM.Z0.S.TTC.001

Singapore interfaces

  • SG.TRN.Z3.B.AIR.CHG.001
  • SG.TRN.Z3.B.PORT.PSA.001
  • SG.TRN.Z3.B.CWY.WDL.001

Lattice Coordinates Referenced (Required)

  • BT.TRN.Z2.B.MRT.DTL.06A
  • BT.TRN.Z2.B.MRT.DTL.07A
  • BT.FAM.Z0.P.LIF.001
  • BT.FAM.Z0.S.TTC.001

Edges Created (Binds To)

  • Coordinate Standard → all node pages must reference this grammar page (link required).

Sensors Mentioned

  • BT.FAM.Z0.S.TTC.001

Recommended Internal Links (Spine)

Master Spine 
https://edukatesg.com/civilisation-os/
https://edukatesg.com/what-is-phase-civilisation-os/
https://edukatesg.com/what-is-drift-civilisation-os/
https://edukatesg.com/what-is-repair-rate-civilisation-os/
https://edukatesg.com/what-are-thresholds-civilisation-os/
https://edukatesg.com/what-is-phase-frequency-civilisation-os/
https://edukatesg.com/what-is-phase-frequency-alignment/
https://edukatesg.com/phase-0-failure/
https://edukatesg.com/phase-1-diagnose-and-recover/
https://edukatesg.com/phase-2-distinction-build/
https://edukatesg.com/phase-3-drift-control/

Block B — Phase Gauge Series (Instrumentation)

Phase Gauge Series (Instrumentation)
https://edukatesg.com/phase-gauge
https://edukatesg.com/phase-gauge-trust-density/
https://edukatesg.com/phase-gauge-repair-capacity/
https://edukatesg.com/phase-gauge-buffer-margin/
https://edukatesg.com/phase-gauge-alignment/
https://edukatesg.com/phase-gauge-coordination-load/
https://edukatesg.com/phase-gauge-drift-rate/
https://edukatesg.com/phase-gauge-phase-frequency/

The Full Stack: Core Kernel + Supporting + Meta-Layers

Core Kernel (5-OS Loop + CDI)

  1. Mind OS Foundation — stabilises individual cognition (attention, judgement, regulation). Degradation cascades upward (unstable minds → poor Education → misaligned Governance).
  2. Education OS Capability engine (learn → skill → mastery).
  3. Governance OS Steering engine (rules → incentives → legitimacy).
  4. Production OS Reality engine (energy → infrastructure → execution).
  5. Constraint OS Limits (physics → ecology → resources).

Control: Telemetry & Diagnostics (CDI) Drift metrics (buffers, cascades), repair triggers (e.g., low legitimacy → Governance fix).

Supporting Layers (Phase 1 Expansions)

Start Here for Lattice Infrastructure Connectors

Start Here