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

Planet OS ECU Claim Ledger

How PlanetOS Tracks Every Major Claim Before Release

1. Classical Baseline

A serious system cannot only ask:

“`text id=”y6esbw”
Is this sentence well-written?

It must ask:

text id=”t2qz5i”
What claim is being made?
What supports it?
How certain is it?
What type of claim is it?
Can it be released?
What caveat is needed?

Without a Claim Ledger, unsupported claims can hide inside fluent writing.
That is how hallucination enters.
---
# 2. One-Sentence Definition
**The ECU Claim Ledger is the PlanetOS tracking table that records every major claim by type, source strength, evidence class, confidence, ECU mode, caveat, and release status.**
---
# 3. Why PlanetOS Needs a Claim Ledger
The Source Layer ranks evidence.
But the Claim Ledger records movement.
The Source Layer says:

text id=”45hjmn”
How strong is the evidence?

The Claim Ledger says:

text id=”v260j9″
What did PlanetOS do with that claim?

This prevents hidden overreach.
---
# 4. Claim Ledger Fields
Every important claim should be tracked like this:

text id=”9gke9d”
CLAIM:
CLAIM TYPE:
SOURCE CLASS:
EVIDENCE CLASS:
CONFIDENCE:
ECU MODE:
CAVEAT:
MOVEMENT STATUS:
RELEASE STATUS:
MEMORY STATUS:

---
# 5. Claim Types
| Claim Type      | Meaning                             |
| --------------- | ----------------------------------- |
| **Fact**        | Describes external reality          |
| **Inference**   | Reasoned from known facts           |
| **Framework**   | Internal PlanetOS / CivOS structure |
| **Metaphor**    | Explanatory image                   |
| **Scenario**    | Possible future/pathway             |
| **Speculation** | Exploratory idea                    |
| **Unknown**     | Not enough evidence                 |
---
# 6. Ledger Template

text id=”r5rdkv”
ECU CLAIM LEDGER v1.0

Claim:

Claim Type:
[ ] Fact
[ ] Inference
[ ] Framework
[ ] Metaphor
[ ] Scenario
[ ] Speculation
[ ] Unknown

Source Class:
[ ] S0 Unknown
[ ] S1 Weak Signal
[ ] S2 Anecdotal
[ ] S3 Reputable Secondary
[ ] S4 Expert Source
[ ] S5 Official / Primary
[ ] S6 Direct Record
[ ] S7 Internal Canon

Evidence Class:
[ ] F0 Unknown
[ ] F1 Weak Signal
[ ] F2 Plausible Inference
[ ] F3 Supported Claim
[ ] F4 Verified Fact
[ ] F5 Internal Canon

Confidence:
[ ] Low
[ ] Medium
[ ] High
[ ] Locked Canon

ECU Mode:
[ ] Strict
[ ] Balanced
[ ] Creative
[ ] Mixed

Caveat:

Movement Status:
[ ] Strong Route
[ ] Shadow Ledger
[ ] Decay Bin
[ ] Repair Required

Release Status:
[ ] Approved
[ ] Approved with caveat
[ ] Hold
[ ] Block

Memory Status:
[ ] Do not store
[ ] Store as weak signal
[ ] Store as article-level claim
[ ] Store as canon

---
# 7. Core Ledger Law

text id=”5xvq52″
NO MAJOR CLAIM MAY BE RELEASED WITHOUT A LEDGER STATE.

This does not mean every small sentence needs a visible table.
It means the ECU internally knows what kind of claim it is releasing.
---
# 8. Claim Movement Rules
| Claim State                 | Movement                 |
| --------------------------- | ------------------------ |
| Unsupported fact            | Block                    |
| Weak but interesting signal | Shadow Ledger            |
| Supported explanation       | Strong Route             |
| Framework rule              | Release as framework     |
| Metaphor                    | Release as metaphor      |
| Scenario                    | Release as scenario      |
| Speculation                 | Release only if labelled |
| Contradiction               | Repair Required          |
---
# 9. Strict ECU Claim Ledger Rules
Strict ECU allows no hidden softness.
For high-stakes claims:

text id=”j4jihr”

  1. Source class must be known.
  2. Evidence class must be F3 or F4 for factual release.
  3. F2 must be labelled as inference.
  4. F1 goes to Shadow Ledger.
  5. S7 internal canon cannot prove external facts.
  6. Numbers require source support.
  7. Uncertainty must be visible.
Strict release:

text id=”74hk7d”
Approve only if:
Claim Type + Source Class + Evidence Class + Caveat + Release Status are clear.

---
# 10. Balanced ECU Claim Ledger Rules
Balanced ECU is used for eduKateSG articles.
It permits synthesis, but not confusion.
Rules:

text id=”wlscxu”

  1. Mainstream baseline must be separated from CivOS extension.
  2. Teaching advice must not become diagnosis.
  3. Framework claims must be labelled as framework.
  4. Inference must be softened.
  5. Public-facing writing must remain clear.
Example:

text id=”zdk0lv”
Claim:
A student who struggles with algebra may have weak symbolic transfer.

Claim Type:
Inference / EducationOS framework interpretation

Release:
Approved with caveat

Better public wording:

text id=”77b50y”
A student struggling with algebra may not simply be “bad at maths”.
In the EducationOS lens, the issue may involve weak symbolic transfer.

---
# 11. Creative ECU Claim Ledger Rules
Creative ECU may invent new structures.
But the ledger must stop invention from pretending to be fact.
Rules:

text id=”ct82x0″

  1. New model = Framework / Speculation.
  2. Mythical engine = Metaphor + Runtime framework.
  3. Scenario = Scenario, not prediction.
  4. P4 frontier idea = Creative extension.
  5. Cerberus must check final wording.
Example:

text id=”u6sqb5″
Claim:
Cerberus is the final release gate of PlanetOS.

Claim Type:
Framework / Metaphor

Evidence Class:
F5 Internal Canon

Release:
Approved as internal PlanetOS structure

---
# 12. Claim Ledger and Shadow Ledger
The Claim Ledger and Shadow Ledger are different.
| Ledger            | Role                                      |
| ----------------- | ----------------------------------------- |
| **Claim Ledger**  | Tracks claims being processed or released |
| **Shadow Ledger** | Stores weak but meaningful signals        |
Movement rule:

text id=”l7r1gh”
If claim is weak but meaningful:
Claim Ledger marks F1
→ Shadow Ledger stores
→ Cerberus blocks factual release

---
# 13. Claim Ledger and MemoryOS
Not every released claim should become memory.
Memory rules:
| Memory Status                    | Meaning                        |
| -------------------------------- | ------------------------------ |
| **Do not store**                 | temporary, minor, context-only |
| **Store as weak signal**         | useful but unconfirmed         |
| **Store as article-level claim** | useful for this branch         |
| **Store as canon**               | stable internal rule           |
Canon storage requires higher threshold.

text id=”yx10ir”
Do not canonise first drafts too easily.

---
# 14. Claim Ledger Failure Types
The ledger blocks:
| Failure                | What Happens          |
| ---------------------- | --------------------- |
| False fact             | Block                 |
| False certainty        | Downgrade             |
| False precision        | Remove number or cite |
| Framework overreach    | Relabel               |
| Metaphor leakage       | Relabel               |
| Unsupported prediction | Scenario label        |
| Contradiction          | Repair                |
| Outdated claim         | Source decay check    |
---
# 15. Claim Ledger Runtime

text id=”gh8dxx”
PLANETOS.ECU.CLAIM_LEDGER.RUNTIME.v1.0

FOR each major claim:

  1. Extract claim.
  2. Classify claim type:
    fact / inference / framework / metaphor / scenario / speculation / unknown
  3. Assign source class:
    S0–S7
  4. Assign evidence class:
    F0–F5
  5. Assign confidence:
    low / medium / high / locked canon
  6. Match ECU mode:
    strict / balanced / creative / mixed
  7. Determine caveat:
    none / minor / required / block
  8. Determine movement:
    strong route / shadow ledger / decay bin / repair required
  9. Determine release:
    approved / approved with caveat / hold / block
  10. Determine memory:
    do not store / weak signal / article claim / canon
  11. Send to Cerberus.
---
# 16. Example Claim Ledger Run
Claim:

text id=”25m1ja”
PlanetOS ECU prevents hallucination by forcing claims through source ranking and release gates.

Ledger:

text id=”36zfkc”
Claim Type:
Framework claim

Source Class:
S7 Internal Canon

Evidence Class:
F5 Internal Canon

Confidence:
Locked inside PlanetOS framework

ECU Mode:
Balanced

Caveat:
This is a framework design claim, not external empirical proof.

Movement:
Strong Route

Release:
Approved with caveat

Memory:
Store as canon

Public wording:

text id=”tw43sa”
In the PlanetOS framework, the ECU reduces hallucination risk by forcing claims through source ranking, claim tracking, ledger audit, and final release gates.

---
# 17. eduKateSG Publishing Use
For eduKateSG, the Claim Ledger gives every article a hidden safety spine.
It lets the article contain:

text id=”xawq42″
mainstream baseline
expert explanation
CivOS extension
PlanetOS framework
metaphor
future scenario
parent-friendly advice

without mixing them into one confused truth layer.
That means eduKateSG can stay:

text id=”7ziqqh”
creative
clear
search-friendly
AI-ingestible
bounded
safe

---
# 18. Final Definition
**The ECU Claim Ledger is the anti-hallucination record that tracks what every major claim is, what supports it, how certain it is, how it may move, whether it may be released, and whether it should become memory.**
---
# Almost-Code Summary

text id=”17krlo”
ARTICLE.ID: PLANETOS.ECU.32
TITLE: ECU Claim Ledger
SYSTEM: PlanetOS ECU v1.0
ROLE: Claim tracking and anti-hallucination control

CORE LAW:
No major claim may be released without a ledger state.

CLAIM_TYPES:
Fact
Inference
Framework
Metaphor
Scenario
Speculation
Unknown

CLAIM_LEDGER_FIELDS:
Claim
Claim Type
Source Class
Evidence Class
Confidence
ECU Mode
Caveat
Movement Status
Release Status
Memory Status

SOURCE_CLASSES:
S0 Unknown
S1 Weak Signal
S2 Anecdotal
S3 Reputable Secondary
S4 Expert Source
S5 Official / Primary
S6 Direct Record
S7 Internal Canon

EVIDENCE_CLASSES:
F0 Unknown
F1 Weak Signal
F2 Plausible Inference
F3 Supported Claim
F4 Verified Fact
F5 Internal Canon

MOVEMENT:
Strong Route
Shadow Ledger
Decay Bin
Repair Required

RELEASE:
Approved
Approved with caveat
Hold
Block

MEMORY:
Do not store
Store as weak signal
Store as article-level claim
Store as canon

STRICT_ECU:
Requires source and evidence clarity.
Blocks weak factual release.

BALANCED_ECU:
Allows synthesis with clear boundaries.

CREATIVE_ECU:
Allows invention only when labelled.

FINAL OUTPUT:
PlanetOS may release only what the Claim Ledger can classify, bound, and pass through Cerberus.
“`

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
A young woman in a white suit and black tie gives a thumbs up while standing in a cozy, dimly-lit cafe with a marble table and books in the background.