PlanetOS ECU v1.0 | Worker Priority Rules

PlanetOS ECU v1.0

1. One-Line Definition

Worker Priority Rules define which PlanetOS Worker acts first, second, third, and why, so signals move through the system in the correct order instead of activating randomly.

The ECU rule is simple:

Workers do not all act at once.
They act in priority order.

2. Why Worker Priority Matters

A signal can be damaged if the wrong worker acts too early.

Example:

Wrong OrderFailure
Dispatcher acts before Sortersignal routed to wrong OS
Translator acts before Janitornoise gets translated as meaning
Auditor acts before Librarianchecks without enough context
Repairman acts before diagnosisfixes the wrong problem
Operator acts before Cerberusunsafe output released

So the ECU imposes a worker sequence.

3. Default Intake Chain

VocabularyOS
→ Janitor
→ Sorter
→ Librarian
→ Translator
→ Dispatcher

This is the default before any major routing.

4. Core Priority Law

LAW 12.1 — CLEAN BEFORE CLASSIFY, CLASSIFY BEFORE ROUTE
A signal must be cleaned before classification,
classified before retrieval,
contextualised before translation,
and translated before dispatch.

This prevents premature routing.

5. Worker Priority Table

PriorityWorkerFunction
0VocabularyOScheck language warp
1Janitorremove noise and contamination
2Sorterclassify signal type and OS branch
3Librarianretrieve memory and context
4Translatornormalise meaning
5Dispatcherroute signal
6Inspectorcheck task-fit
7Auditorcheck invariants and ledgers
8Repairmanrepair broken route or missing node
9Operatorcompile output

6. Priority 0 — VocabularyOS

VocabularyOS acts before all workers.

It checks whether the signal’s words are stable.

It asks:

  • Is the term defined?
  • Is the label accurate?
  • Is the frame loaded?
  • Is attribution warped?
  • Is emotion distorting meaning?
  • Is positive language hiding negative movement?

If language is unstable, the signal cannot move cleanly.

7. Priority 1 — Janitor

The Janitor cleans the signal.

It removes:

  • spam
  • duplicate noise
  • irrelevant material
  • emotional excess
  • broken formatting
  • contamination from unrelated frames

But the Janitor must not throw away weak signals too early.

LAW 12.2 — CLEANING IS NOT DELETION
The Janitor removes noise.
The Janitor does not destroy weak but meaningful signals.

8. Priority 2 — Sorter

The Sorter classifies the signal.

It decides:

  • signal type
  • OS branch
  • urgency
  • stakes
  • evidence level
  • likely route

Example:

“Student is not improving” may be sorted into:

EducationOS
→ MathOS / EnglishOS
→ MindOS
→ Uptake Algorithm
→ Repair Corridor

Not automatically:

discipline problem

9. Priority 3 — Librarian

The Librarian retrieves context.

It pulls:

  • previous cases
  • definitions
  • ledgers
  • framework memory
  • article branch context
  • known failure patterns
  • relevant canonical locks

Without the Librarian, PlanetOS becomes shallow.

It answers only from the surface of the signal.

10. Priority 4 — Translator

The Translator normalises meaning.

It separates:

LayerMeaning
Factwhat is claimed as true
Inferencewhat is being concluded
Emotionwhat is being felt
Metaphorwhat is symbolic
Speculationwhat is possible but not proven
Instructionwhat action is being requested

This is especially important in Creative ECU.

Creative ideas must be translated before release so they do not masquerade as established fact.

11. Priority 5 — Dispatcher

The Dispatcher sends the signal to the correct branch.

It routes to:

  • OS module
  • Worker chain
  • Mythical Guardian
  • Ledger
  • Shadow Ledger
  • Repair loop
  • Cerberus gate

The Dispatcher acts only after cleaning, sorting, context retrieval, and translation.

12. Priority 6 — Inspector

The Inspector checks task-fit.

It asks:

  • Is this the right route?
  • Is the correct ECU mode active?
  • Is the output type clear?
  • Are the relevant OS branches included?
  • Is the question being answered at the right zoom level?

The Inspector prevents beautiful wrong answers.

13. Priority 7 — Auditor

The Auditor checks invariants.

It asks:

  • Did we violate the Ledger of Invariants?
  • Did we overclaim?
  • Did we confuse fact with speculation?
  • Did we break the user’s intended branch?
  • Did we route by label rather than content?
  • Did we preserve uncertainty where needed?

Auditor is especially strong under Strict ECU.

14. Priority 8 — Repairman

The Repairman activates only when something is broken.

Triggers:

  • missing node
  • contradiction
  • failed transfer
  • broken route
  • unstable definition
  • unreconciled ledger
  • wrong OS branch
  • collapsed learning path

Repairman does not invent randomly.

Repairman restores corridor viability.

15. Priority 9 — Operator

The Operator compiles the final output.

The Operator:

  • assembles the response
  • preserves structure
  • formats for public use
  • keeps article sequence intact
  • prepares WordPress-ready output
  • ensures the answer is readable

But the Operator cannot release alone.

Cerberus still gates final output.

16. Worker Priority Almost-Code

PLANETOS.ECU.WORKER_PRIORITY.v1.0
FUNCTION WorkerPriority(signal):
0. VocabularyOS.check(signal)
1. Janitor.clean(signal)
   IF signal = junk:
      send_to_decay_bin()
   ELSE:
      preserve_signal()
2. Sorter.classify(signal)
   SET signal_type
   SET OS_branch
   SET urgency
   SET stakes
   SET evidence_level
3. Librarian.retrieve(signal)
   LOAD memory
   LOAD context
   LOAD ledgers
   LOAD relevant branches
4. Translator.normalise(signal)
   SPLIT fact
   SPLIT inference
   SPLIT emotion
   SPLIT metaphor
   SPLIT speculation
   SPLIT instruction
5. Dispatcher.route(signal)
   ROUTE to OS_branch
   ROUTE to worker_chain
   ROUTE to guardian_if_needed
   ROUTE to ledger_or_shadow_ledger
6. Inspector.check_task_fit(signal)
7. Auditor.check_invariants(signal)
8. IF broken_route OR missing_node OR contradiction:
      Repairman.repair(signal)
9. Operator.compile(signal)
10. Cerberus.final_gate(output)

17. Wrong-Order Failure Examples

Example 1 — EducationOS

Wrong order:

Parent says “my child is lazy”
→ Dispatcher routes to discipline
→ output blames effort

Correct order:

VocabularyOS checks “lazy”
→ Janitor removes frustration
→ Sorter identifies learning failure signal
→ Librarian retrieves learning history
→ Translator separates behaviour from uptake mismatch
→ Dispatcher routes to EducationOS repair

Example 2 — NewsOS

Wrong order:

Headline says “crisis”
→ Hydra activates many narratives
→ output amplifies panic

Correct order:

VocabularyOS checks “crisis”
→ Janitor removes emotional overload
→ Sorter separates event / claim / frame
→ Librarian retrieves source context
→ Translator separates fact from framing
→ Dispatcher routes to NewsOS + RealityOS

Example 3 — Creative ECU

Wrong order:

New metaphor appears
→ Operator publishes as truth

Correct order:

Creative signal
→ VocabularyOS checks term
→ Sorter classifies as model invention
→ Translator labels metaphor/speculation
→ Auditor checks boundary
→ Cerberus releases as creative framework

18. Priority Override Rule

Sometimes the normal sequence can be accelerated.

But not skipped.

For emergency Strict ECU:

VocabularyOS
→ Janitor
→ Sorter
→ Strict ECU
→ Auditor
→ Cerberus

Even under urgency:

The system may compress the intake chain, but it cannot bypass meaning checks.

19. Clean Compression

Worker Priority = correct turn order.
VocabularyOS checks language.
Janitor cleans.
Sorter classifies.
Librarian retrieves.
Translator normalises.
Dispatcher routes.
Inspector checks.
Auditor audits.
Repairman repairs.
Operator compiles.
Cerberus releases.

20. Final Lock

Article 12 locks the worker order of PlanetOS ECU.

The key rule:

Clean before classify.
Classify before retrieve.
Retrieve before translate.
Translate before route.
Audit before release.

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 blazer and skirt giving a thumbs up, standing in a café setting with a workbook open on the table.