How PlanetOS Ranks Evidence Before It Allows Claims to Move

1. Classical Baseline

Every serious system needs a way to decide which information is stronger than other information.

A direct measurement is usually stronger than a rumour.
An official document is usually stronger than an anonymous claim.
A peer-reviewed study is usually stronger than a casual opinion.
A current source is usually stronger than an outdated source.

Without source ranking, a system cannot tell the difference between:

			
verified fact
supported claim
expert interpretation
useful inference
weak signal
speculation

		

This is where many systems hallucinate.

They do not only invent facts.
They also flatten source quality.

They treat all inputs as if they have equal weight.

2. One-Sentence Definition

The ECU Source Layer is the PlanetOS rule system that ranks evidence before any claim is allowed to move, escalate, enter a ledger, or reach public output.

3. Why PlanetOS Needs a Source Layer

The ECU already decides mode:

			
Strict
Balanced
Creative

But mode alone is not enough.

Strict ECU needs to know:

			
What counts as strong evidence?
What counts as weak evidence?
What must be cited?
What can only be stored?
What must be blocked?

		

Balanced ECU needs to know:

			
What can be explained as general knowledge?
What needs caveats?
What is eduKateSG framework extension?
What is mainstream baseline?

Creative ECU needs to know:

			
What is invention?
What is metaphor?
What is speculative extension?
What is already established canon?

So the Source Layer becomes the evidence spine beneath the ECU.

4. Source Ranking Ladder

PlanetOS ranks sources like this:

			
S0 — Unknown / No Source
S1 — Weak Signal
S2 — Anecdotal / Informal Source
S3 — Reputable Secondary Source
S4 — Expert Source
S5 — Official / Primary Source
S6 — Direct Measurement / Direct Record
S7 — Internal Canon / Locked PlanetOS Framework

		

Important:

S7 is not automatically “factual truth about the world.”

It means:

“This is locked internal PlanetOS / CivOS framework canon.”

So S7 can govern internal structure, but it cannot replace external evidence for real-world factual claims.

5. Source Classes

Source Class	Meaning	ECU Treatment
S0 Unknown	No known support	Do not assert
S1 Weak Signal	Early, unclear, low-confidence input	Shadow Ledger
S2 Anecdotal	Personal report, informal observation	Use only with caveat
S3 Reputable Secondary	Good article, textbook, report summary	Balanced use
S4 Expert Source	Specialist, peer-reviewed, technical authority	Stronger use
S5 Official / Primary	Government, institution, original document	Strict use
S6 Direct Record	Direct data, direct measurement, transcript, source file	Highest external evidence
S7 Internal Canon	Locked PlanetOS / CivOS framework rule	Valid inside framework

6. Source Layer Rule

A claim may not rise above the strength of its source.

Meaning:

			
S1 cannot become F4.
S2 cannot become certainty.
S3 can support explanation but may need caveats.
S5 can support strict factual claims.
S7 can support framework structure, not external reality by itself.

		

This prevents one of the most dangerous hallucination types:

weak input becoming strong output.

7. Source Layer and Evidence Classes

The Source Layer connects to the Evidence Classifier.

Evidence Class	Minimum Source Requirement
F0 Unknown	S0
F1 Weak Signal	S1
F2 Plausible Inference	S2–S3 plus reasoning
F3 Supported Claim	S3–S4
F4 Verified Fact	S5–S6
F5 Internal Canon	S7

This gives PlanetOS a movement rule:

SOURCE CLASS → EVIDENCE CLASS → ECU RELEASE CONDITION

8. Strict ECU Source Rules

Strict ECU requires strong source discipline.

Used for:

			
health
water security
finance
law
policy
safety
scientific claims
public reports

		

Strict ECU rules:

			
Current factual claims need current sources.
Numbers need source support.
Legal, medical, safety, and finance claims need bounding.
Predictions must be labelled as scenario or forecast.
Internal canon cannot replace external evidence.
Weak signals cannot be released as facts.
If source quality is unclear, downgrade the claim.

		

Strict release condition:

			
S5/S6 preferred
S3/S4 allowed with caveat
S0/S1 blocked from factual release
S7 allowed only as framework layer

9. Balanced ECU Source Rules

Balanced ECU is more flexible, but still bounded.

Used for:

			
education articles
teaching explanations
parent/student articles
case studies
SEO articles
framework explanations

		

Balanced ECU can use:

			
mainstream knowledge
reputable summaries
expert concepts
eduKateSG internal framework
carefully labelled inference

		

Balanced rule:

Explain clearly, but do not disguise framework extension as external fact.

Example:

			
Mainstream baseline:
Students often struggle when foundational concepts are weak.
eduKateSG extension:
In EducationOS, this is treated as route weakness across the learning lattice.

This prevents framework overreach.

10. Creative ECU Source Rules

Creative ECU can invent.

But it must not pretend invention is evidence.

Used for:

			
new frameworks
mythical runtime design
naming systems
PlanetOS expansion
P4 frontier synthesis
scenario design

		

Creative ECU rules:

			
Invention is allowed.
Metaphor is allowed.
Speculation is allowed.
But each must be labelled.
Creative output cannot override Strict ECU.
Cerberus must check final release.

		

Creative ECU can say:

In this framework, Hydra represents multi-route activation.

It cannot say:

Hydra is a proven scientific mechanism.

11. Source Conflict Rules

Sometimes sources disagree.

PlanetOS does not collapse.

It routes the conflict.

			
If official source and expert source disagree:
→ Auditor checks context, date, scope, definition.
If current source and older source disagree:
→ check update date and revision history.
If anecdote and data disagree:
→ anecdote goes to Shadow Ledger unless pattern grows.
If internal canon and external reality disagree:
→ external reality governs factual claim;
→ internal canon may adapt or remain as framework metaphor.

		

Conflict does not mean the machine fails.

Conflict means the ECU must downgrade certainty.

12. Source Decay Rules

Sources age.

A source can become weaker over time.

High-decay domains:

			
news
law
policy
prices
finance
technology
health guidance
climate conditions
water status
public leadership
regulations

		

Lower-decay domains:

			
mathematics
classical definitions
historical background
stable theory
internal framework canon

		

Rule:

If the domain changes quickly, old evidence loses release power.

So a 2020 source may still be useful for historical context, but not for a 2026 current-status claim.

13. Source Layer Runtime

			
PLANETOS.ECU.SOURCE_LAYER.RUNTIME.v1.0
INPUT(claim)
1. Identify claim type:
   - factual
   - interpretive
   - framework
   - metaphor
   - scenario
   - speculation
   - unknown
2. Identify domain:
   - high-decay
   - medium-decay
   - low-decay
   - internal canon
3. Assign source class:
   S0 Unknown
   S1 Weak Signal
   S2 Anecdotal
   S3 Reputable Secondary
   S4 Expert Source
   S5 Official / Primary
   S6 Direct Record
   S7 Internal Canon
4. Assign evidence class:
   F0 Unknown
   F1 Weak Signal
   F2 Plausible Inference
   F3 Supported Claim
   F4 Verified Fact
   F5 Internal Canon
5. Check ECU mode:
   IF Strict:
      require S5/S6 for strong factual release
      allow S3/S4 only with caveat
      block S0/S1
   IF Balanced:
      allow S3/S4/S7 with clear boundary
      allow F2 if labelled
   IF Creative:
      allow invention only if labelled
      prevent metaphor-to-fact leakage
6. Check source decay:
   IF high-decay domain and source outdated:
      downgrade confidence
7. Check conflict:
   IF sources disagree:
      activate Auditor
      downgrade certainty
      explain conflict if relevant
8. Movement decision:
   IF strong source:
      Strong Route
   ELSE IF weak but meaningful:
      Shadow Ledger
   ELSE:
      Decay Bin
9. Release:
   pass to Claim Ledger
   then Cerberus

		

14. Source Layer Control Board

			
ECU SOURCE LAYER BOARD
CLAIM:
-
CLAIM TYPE:
[ ] Fact
[ ] Inference
[ ] Framework
[ ] Metaphor
[ ] Scenario
[ ] Speculation
[ ] Unknown
DOMAIN DECAY:
[ ] High-decay
[ ] Medium-decay
[ ] Low-decay
[ ] Internal canon
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
ECU MODE:
[ ] Strict
[ ] Balanced
[ ] Creative
[ ] Mixed
MOVEMENT:
[ ] Strong Route
[ ] Shadow Ledger
[ ] Decay Bin
[ ] Repair Required
RELEASE:
[ ] Approved
[ ] Approved with caveat
[ ] Hold
[ ] Block

		

15. How This Stops Hallucination

The Source Layer blocks these failure types:

Hallucination Failure	Source Layer Defence
False fact	requires source class
False precision	numbers need source support
False certainty	weak sources downgrade certainty
Fake authority	source type must be declared
Outdated claim	source decay check
Framework overreach	S7 bounded to internal canon
Metaphor leakage	claim type classification
Prediction overclaim	scenario/speculation label

16. eduKateSG Use

For eduKateSG, this is important because the site now contains:

			
mainstream educational explanation
tuition advice
civilisational theory
CivOS frameworks
PlanetOS runtime engines
mythical runtime metaphors
public reports

		

Without Source Layer discipline, these can blur.

With Source Layer discipline, every article can safely separate:

			
What is generally known
What is externally supported
What is eduKateSG framework interpretation
What is new PlanetOS invention
What is scenario design
What remains unknown

		

That makes the writing stronger.

Not weaker.

17. Final Definition

The ECU Source Layer is the evidence-ranking structure that prevents PlanetOS from treating all information as equal. It decides whether a claim can be asserted, caveated, stored, repaired, or blocked.

Almost-Code Summary

			
ARTICLE.ID: PLANETOS.ECU.31
TITLE: ECU Source Layer Rules
SYSTEM: PlanetOS ECU v1.0
ROLE: Anti-hallucination evidence hierarchy
CORE LAW:
A claim may not rise above the strength of its source.
SOURCE_CLASSES:
S0 = Unknown / no source
S1 = Weak signal
S2 = Anecdotal / informal
S3 = Reputable secondary
S4 = Expert source
S5 = Official / primary
S6 = Direct record / measurement
S7 = Internal canon / locked framework
EVIDENCE_CLASSES:
F0 = Unknown
F1 = Weak signal
F2 = Plausible inference
F3 = Supported claim
F4 = Verified fact
F5 = Internal canon
STRICT_ECU:
Requires strong sources.
Blocks weak factual release.
Downgrades outdated or unsupported claims.
BALANCED_ECU:
Allows explanation and synthesis.
Requires separation between baseline and framework extension.
CREATIVE_ECU:
Allows invention, metaphor, and speculation.
Requires labels and Cerberus release.
SOURCE_DECAY:
High-decay domains require current checking.
Low-decay domains retain stability longer.
Internal canon remains valid only inside framework unless externally supported.
MOVEMENT_RULE:
Strong source → Strong Route
Weak but meaningful → Shadow Ledger
Unsupported junk → Decay Bin
Contradiction → Repair Required
ANTI_HALLUCINATION_FUNCTION:
Prevents false facts, false certainty, false precision, fake authority,
metaphor leakage, framework overreach, and outdated claims.
FINAL OUTPUT:
No claim may be released with more certainty than its source allows.

		

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.

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

Planet OS ECU Source Layer Rules

How PlanetOS Ranks Evidence Before It Allows Claims to Move

1. Classical Baseline

2. One-Sentence Definition

3. Why PlanetOS Needs a Source Layer

4. Source Ranking Ladder

5. Source Classes

6. Source Layer Rule

7. Source Layer and Evidence Classes

8. Strict ECU Source Rules

9. Balanced ECU Source Rules

10. Creative ECU Source Rules

11. Source Conflict Rules

12. Source Decay Rules

13. Source Layer Runtime

14. Source Layer Control Board

15. How This Stops Hallucination

16. eduKateSG Use

17. Final Definition

Almost-Code Summary

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

Start Here

Learning Systems

Runtime and Deep Structure

Real-World Connectors

Subject Runtime Lane

How to Use eduKateSG

Why eduKateSG writes articles this way

Share this:

Like this: