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

FENCE™ → Unified Registry Alignment (Canonical Binding Spec v0.2)

FENCE™ → Unified Registry Alignment

(Canonical Binding Spec v0.2)

1️⃣ FENCE Is NOT Its Own Lane

Correction Lock

FENCE is not a separate grammar.

It is:

FENCE = Execution Architecture for ENG Lane

So instead of:

FENCE-ENG-Z1-PAR-ROLE

We standardise to:

ENG-PRI-Z1-CMP-PARROLE
ENG-SEC-Z1-WRT-PARROLE

FENCE becomes the training protocol, not the coordinate system.

This prevents fragmentation.

2️⃣ Module Binding Map (Old → Unified)

Engineered Sentence System

Old:

FENCE-ENG-Z0-ESS-CORE
FENCE-ENG-Z0-ESS-DETAIL
FENCE-ENG-Z0-ESS-CAUSE

Unified:

ENG-PRI-Z0-CMP-SENTSTRUCT
ENG-SEC-Z0-WRT-SENTSTRUCT
ENG-PRI-Z1-CMP-SENTEXPAND
ENG-SEC-Z1-WRT-SENTEXPAND

Why:
Sentence architecture belongs under CMP/WRT module.

Vocabulary Loop

Old:

FENCE-ENG-Z0-VOC-ACQUIRE
FENCE-ENG-Z0-VOC-FORGE
FENCE-ENG-Z1-VOC-SPAR
FENCE-ENG-Z2-VOC-MATCH

Unified:

Primary:

VOC-PRI-Z0-SEM-MEANING
VOC-PRI-Z1-COL-COLLOC
VOC-PRI-Z2-SCN-DEPLOY
VOC-PRI-Z3-TIM-STABLE

Secondary:

VOC-SEC-Z0-SEM-MEANING
VOC-SEC-Z1-REG-REGISTER
VOC-SEC-Z2-CTX-CONTEXT
VOC-SEC-Z3-TIM-STABLE

Why:
Vocabulary is its own lane. FENCE just routes into it.

Comprehension Engine

Old:

FENCE-ENG-Z1-CNE-EXPLAIN
FENCE-ENG-Z1-CNE-PEE

Unified:

Primary:

ENG-PRI-Z1-RDN-EVD
ENG-PRI-Z2-RDN-INF

Secondary:

ENG-SEC-Z1-RDN-EVD
ENG-SEC-Z2-RDN-INF
ENG-SEC-Z2-RDN-SYN

Why:
Reading belongs under RDN module.

Performance Under Pressure

Old:

FENCE-ENG-Z2-PUP-FULLSIM

Unified:

Primary:

PSLE-Z3-SIM-FULLPAPER
PSLE-Z3-PAC-BUDGET
PSLE-Z3-REC-RESET

Secondary:

OLEVEL-Z3-SIM-FULLPAPER
OLEVEL-Z3-PAC-BUDGET
OLEVEL-Z3-REC-RESET

Why:
Stress behavior belongs to Exam Wrapper OS, not ENG lane.

3️⃣ Sensor Panel Alignment

Old metrics:

  • SSI
  • VDR
  • ERR
  • TAE
  • PDS

We keep them — but bind them.

SSI (Sentence Stability Index)

Binds to:

ENG-PRI-Z0-CMP-SENTSTRUCT
ENG-SEC-Z0-WRT-SENTSTRUCT

Trigger:
If SSI < threshold → route to sentence drills

VDR (Vocabulary Deployment Ratio)

Binds to:

VOC-PRI-Z2-SCN-DEPLOY
VOC-SEC-Z2-CTX-CONTEXT

Trigger:
If VDR low → run Forge → Spar → Match

ERR (Error Recurrence Rate)

Binds to:

PSLE-Z1-ERR-CLASS
OLEVEL-Z1-ERR-CLASS

TAE (Time Allocation Efficiency)

Binds to:

PSLE-Z3-PAC-BUDGET
OLEVEL-Z3-PAC-BUDGET

PDS (Paragraph Density Score)

Binds to:

ENG-PRI-Z1-CMP-PARROLE
ENG-SEC-Z1-WRT-STRUCT

4️⃣ What Changes On the Live Page

Minimal visible change.

But internally:

Instead of inventing FENCE codes, the page should say:

“FENCE trains these registry coordinates:”

Example rewrite block:

FENCE trains:
• ENG-PRI-Z0-CMP-SENTSTRUCT
• VOC-PRI-Z2-SCN-DEPLOY
• ENG-PRI-Z2-RDN-INF
• PSLE-Z3-PAC-BUDGET

This immediately snaps it into the master system.

5️⃣ Structural Upgrade Achieved

Before:
FENCE = separate identity layer.

After:
FENCE = execution protocol bound to ENG + VOC + Exam wrapper.

Now the architecture is:

CivOS
  → Education OS
      → FenceOS (control primitive)
          → ENG Lane
              → Vocabulary Lane
          → Exam Wrapper (PSLE / OLEVEL)

No duplication.
No grammar conflict.
No fragmentation.

6️⃣ What This Fixes

  • eliminates parallel naming systems
  • prevents SEO confusion
  • strengthens AI ontology adoption
  • makes every page machine-compatible
  • enables Unified LLM Master Prompt to read FENCE pages cleanly

7️⃣ Status After Alignment

eduKateSG now has:

✔ Unified coordinate grammar
✔ Exam wrapper separation
✔ Vocabulary as independent lane
✔ ENG lane separated into CMP/RDN/EDT
✔ Registry binding clean
✔ FENCE as execution protocol (not competing OS)

That is architecturally mature.

Start here if you want the full sequence:

Vocabulary OS Series Index:
https://edukatesg.com/vocabulary-os-series-index/

Fence English Learning System: 

eduKateSG Learning Systems: 

Recommended Internal Links (Spine)

Start Here for Lattice Infrastructure Connectors