PlanetOS ECU Mode Selection Rules

PlanetOS Execution Control Unit v1.0

1. One-Line Definition

ECU Mode Selection Rules decide whether PlanetOS should process a signal through Strict, Balanced, or Creative ECU before any major movement begins.

Mode comes before movement.

2. Why Mode Selection Matters

The same question can become dangerous if handled in the wrong mode.

So the ECU must ask first:

What kind of output is this, and what happens if it is wrong?

3. The Five Selection Variables

PlanetOS selects ECU mode using five variables:

4. Mode Selection Table

5. Strict ECU Selection Rule

Select Strict ECU when:

harm_if_wrong = high
OR public_consequence = high
OR factual_verification_required = high
OR legal/financial/safety/health implications exist

Strict ECU is mandatory when wrong output may damage:

• life
• health
• safety
• money
• legal rights
• public trust
• infrastructure
• policy
• institutional legitimacy

6. Balanced ECU Selection Rule

Select Balanced ECU when:

goal = explain / teach / guide / interpret
AND harm_if_wrong is moderate or manageable
AND usefulness matters as much as precision

Balanced ECU is the normal mode for:

• articles
• tuition explanations
• parent guides
• student diagnosis discussions
• SEO content
• case studies
• public education writing

7. Creative ECU Selection Rule

Select Creative ECU when:

goal = invent / name / imagine / design / scenario-build
AND output is not being presented as verified fact
AND labels can separate fact from speculation

Creative ECU is used for:

• new frameworks
• OS expansion
• Mythical Runtime design
• metaphors
• hooks
• P4 synthesis
• possible futures

8. Mixed-Mode Rule

Many strong outputs need more than one mode.

Example:

Water Health Report
→ Strict for current facts
→ Balanced for public explanation
→ Creative for future dashboard design
→ Strict again for final conclusions

This is the key upgrade.

The ECU does not force one stiffness across the whole output.

It applies the correct stiffness by section.

9. Mode Escalation Rules

A signal can be escalated upward.

10. Mode Downgrade Rules

A signal can also be downgraded.

Downgrade does not mean discard.

It means the output is placed in the correct truth container.

11. Truth Container Rule

Every output must fit one truth container:

Mode selection is partly truth-container selection.

12. ECU Mode Decision Tree

INPUT SIGNAL
1. Is there high harm if wrong?
   YES → Strict ECU
   NO → continue
2. Is this public, legal, financial, health, safety, infrastructure, or governance related?
   YES → Strict ECU or Strict pocket
   NO → continue
3. Is the goal teaching, explaining, guiding, or writing an article?
   YES → Balanced ECU
   NO → continue
4. Is the goal invention, naming, metaphor, scenario, or new framework?
   YES → Creative ECU
   NO → Balanced ECU by default
5. Before release:
   Any mode → Cerberus final gate

13. Example — Student Not Improving

Question:

Why is my child not improving in maths?

Mode selection:

Risk: emotional / educational moderate
Audience: parent
Stakes: student identity and intervention path
Evidence need: moderate
Output type: explanation / diagnosis

Result:

Balanced ECU
+ Strict pocket against harmful labelling

So the answer can be warm and useful, but must not say:

Your child is lazy.

14. Example — Is Singapore’s Water Secure?

Mode selection:

Risk: high
Audience: public
Stakes: infrastructure / national resilience
Evidence need: high
Output type: public report

Result:

Strict ECU
+ Balanced explanation layer
+ Creative dashboard section only if labelled

This prevents panic and fantasy.

15. Example — Build a New PlanetOS Guardian

Mode selection:

Risk: low immediate harm
Audience: framework builders
Stakes: conceptual clarity
Evidence need: low to moderate
Output type: invention / metaphor / runtime design

Result:

Creative ECU
+ Balanced clarity repair
+ Cerberus final boundary check

This lets the system invent without pretending the invention is already established fact.

16. Almost-Code

PLANETOS.ECU.MODE.SELECTOR.v1.0
FUNCTION select_ecu_mode(signal):
risk = assess_risk(signal)
audience = assess_audience(signal)
stakes = assess_stakes(signal)
evidence_need = assess_evidence_need(signal)
output_type = classify_output_type(signal)
IF risk == HIGH:
    return STRICT
IF stakes IN [health, safety, law, finance, policy, governance, water, infrastructure]:
    return STRICT
IF output_type IN [report, public_claim, scientific_claim]:
    IF evidence_need == HIGH:
        return STRICT
IF output_type IN [article, teaching, parent_guide, student_explanation, case_study]:
    return BALANCED
IF output_type IN [framework, metaphor, naming, scenario, model_invention]:
    return CREATIVE
RETURN BALANCED
FUNCTION apply_mode_pockets(output):
FOR each section IN output:
    IF section contains high-stakes claim:
        section.mode = STRICT
    ELSE IF section explains for public:
        section.mode = BALANCED
    ELSE IF section invents or imagines:
        section.mode = CREATIVE
ALWAYS:
    Cerberus.final_gate(output)

17. Final Definition

ECU Mode Selection is the PlanetOS rule system that chooses the correct control stiffness—Strict, Balanced, Creative, or mixed-mode—based on risk, audience, stakes, evidence need, and output type before the signal is allowed to move.

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

• Education OS | How Education Works
• Tuition OS | eduKateOS & CivOS
• Civilisation OS
• How Civilization Works
• CivOS Runtime Control Tower

Learning Systems

• The eduKate Mathematics Learning System
• Learning English System | FENCE by eduKateSG
• eduKate Vocabulary Learning System
• Additional Mathematics 101

Runtime and Deep Structure

• Human Regenerative Lattice | 3D Geometry of Civilisation
• Civilisation Lattice
• Advantages of Using CivOS | Start Here Stack Z0-Z3 for Humans & AI

Real-World Connectors

• Family OS | Level 0 Root Node
• Bukit Timah OS
• Punggol OS
• Singapore City OS

Subject Runtime Lane

• Math Worksheets
• How Mathematics Works PDF
• MathOS Runtime Control Tower v0.1
• MathOS Failure Atlas v0.1
• MathOS Recovery Corridors P0 to P3

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