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

Z6.Runtime.InstallGuide — v1.0 (Almost-Code, 10-Minute Operator Install)

Three students discuss open schoolbooks and handwritten notes during a group study session.

ID: Z6_RUNTIME_INSTALL_GUIDE_v1_0
Status: LOCKED
Purpose: A short, operator-friendly guide to “install” the CivOS runtime on a site without breaking ontology.
Audience: Operator/Oracle (publishers), with Architect optional.

0) META + Safety Fence

“`text id=”qv1z01″
DEFLOCK.INSTALLGUIDE:
This is an install guide for a machine-readable runtime (directory + thresholds + logs).
Not: a rewrite of CivOS theory.
Goal: publish modules in correct order with stable IDs and forward-only versions.

NON-OVERWRITE RULE:

  • Never rename NodeID/BindID/PlaceID/LaneID/ModuleID.
  • Never delete/overwrite structure to “fix”.
  • If a change is needed: publish a new version page (v1.1, v1.2…) and update pointers.
---
## 1) Minimum Viable Runtime (MVR) — Install in 10 minutes
### Step 1 — Publish the three core modules (T0)

text id=”a7f9u2″
INSTALL.MVR.STEP1:
Publish these pages (copy-paste from specs):
1) UOS_THRESHOLD_SPEC_v1_0
2) UOS_PROPAGATION_MAP_v1_0
3) RECL_SCHEMA_v1_0

### Step 2 — Publish the controller pack (T1)

text id=”m2q3p8″
INSTALL.MVR.STEP2:
Publish:
4) ERCO_DEPLOY_PACK_v1_0
Ensure Fence trigger language exists:
– TTC ≤ T_repair => TRUNCATE now
– then STITCH + RETEST

### Step 3 — Publish the City template + one example city (T2 minimal)

text id=”j1r4c0″
INSTALL.MVR.STEP3:
Publish:
5) GLOBAL_CITYERCO_TEMPLATE_v1_0
Then publish 1 city using the template:
– SGP:SGP or USA:NYC or JPN:TYO (choose any)

### Step 4 — Publish the Z6 City registry (breadth surface)

text id=”p6v0d3″
INSTALL.MVR.STEP4:
Publish:
6) Z6_GLOBALPACK_CITYERCO_REGISTRY_BLOCK_v1_0
(Optional) paste Top-50 stubs if you want immediate breadth.

✅ At this point the runtime is “installable”:
**thresholds + propagation + lattice + controller + city template + registry**
---
## 2) “Do Not Break Ontology” Checklist (publish-time)

text id=”s8n2k7″
CHECKLIST.PUBLISH:
[ ] First line contains version anchor (v1.0/v1.2).
[ ] Definition lock present (short, fenced).
[ ] IDs are stable and consistent:
– PlaceID: COUNTRY:, CITY::
– NodeID: NODE__Z3_CITYOS – ERCO instance: ERCO__Z3
[ ] No renames, no “cleanup edits” that mutate IDs.
[ ] If you must change wording, do it without changing IDs.
[ ] If you must change structure, publish a new version page.

---
## 3) When to Install the Live Layer (T3)
Only install these when you actually want the runtime to “update” over time.

text id=”v4w7m1″
INSTALL.LIVE_LAYER:
7) Z5Z5_COUNTRY_BIND_LAYER_v1_0
8) Z5_SHOCK_ROUTER_BUFFER_POLICY_PACK_v1_0
9) Z6_ADAPTER_SPEC_v1_0
10) Z6_DATAFEED_ADAPTER_INDEX_v1_0
11) Z6_EVENTLOG_DIRECTORY_v1_0

---
## 4) “What do I paste where?” (Operator Map)

text id=”n3y6p2″
OPERATOR.MAP:

  • CivOS runtime hub page:
    Z6_RUNTIME_CONTROL_TOWER_INDEX_v1_0
  • Physics pages:
    UOS_THRESHOLD_SPEC_v1_0
    UOS_PROPAGATION_MAP_v1_0
  • Data model page:
    RECL_SCHEMA_v1_0
  • Controller page:
    ERCO_DEPLOY_PACK_v1_0
  • Templates:
    GLOBAL_CITYERCO_TEMPLATE_v1_0
  • Registries:
    Z6_GLOBALPACK_CITYERCO_REGISTRY_BLOCK_v1_0
    (optional) TOP50 / TOP200 stub packs
  • Live updates:
    Z6_ADAPTER_SPEC_v1_0
    Z6_EVENTLOG_DIRECTORY_v1_0
---
## 5) Minimal “AI Mode Hook” (optional; use on install pages)

text id=”k1c0z9″
AI_MODE.HOOK.MIN:
Install order: Thresholds → Propagation → RECL schema → ERCO controller → City template → Global registry → (optional) adapters + eventlog.
Structure is immutable; updates are append-only events.

---
## 6) Fast Troubleshooting (publishing + indexing)

text id=”r0t9a1″
TROUBLESHOOT:
If a page doesn’t show up quickly:
– confirm it’s linked from a hub/index page
– ensure canonical slug is stable
– avoid duplicate near-identical pages published in bulk without index pointers
– add 1–2 internal links with exact module names (ERCO/RECL/UOS)

---
## 7) “Next Install” Recommendations (choose by need, not by template)

text id=”e7s3m6″
NEXT.INSTALL.RECO:

  • If your goal is breadth:
    paste TOP200_CITY_STUB_EXPANSION_PACK_v1_0 into the Z6 registry page
  • If your goal is depth:
    publish CityERCO pages for:
    SGP:SGP, USA:NYC, JPN:TYO, CHN:BJS, GBR:LON
  • If your goal is “live runtime”:
    install adapter spec + eventlog pages
    “`

Recommended Internal Links (Spine)

Start Here For Mathematics OS Articles: 

Start Here for Lattice Infrastructure Connectors

eduKateSG Learning Systems: