PlanetOS ECU v1.0 | Machine-Readable Runtime Rules
1. One-Line Definition
The ECU Almost-Code Compiler is the machine-readable rule layer that tells PlanetOS how to select mode, route signals, activate workers, wake guardians, audit ledgers, repair failure, store weak signals, and release final output.
2. Core Function
The compiler turns this:
A messy input enters PlanetOS.
Into this:
mode selected→ language checked→ workers activated→ route chosen→ guardians triggered→ ledgers audited→ repair applied→ Cerberus release gate passed→ output compiled→ memory updated
The ECU Compiler makes PlanetOS executable.
3. PlanetOS ECU Compiler v1.0
PLANETOS.ECU.COMPILER.v1.0SYSTEM.TYPE: Execution Control UnitSYSTEM.ROLE: Governs signal movement across PlanetOS.SYSTEM.NOT: Not an OS branch. Not a worker. Not a mythical guardian. Not a truth oracle. Not a replacement for evidence.SYSTEM.DOES: Selects control mode. Orders worker sequence. Routes signal. Activates guardians. Controls thresholds. Audits ledgers. Sends weak signals to Shadow Ledger. Sends junk to Decay Bin. Triggers repair. Gates release through Cerberus. Updates MemoryOS.
4. Input Object
INPUT.OBJECT:signal.id: unique signal identifiersignal.raw: original inputsignal.source: user / document / report / news / sensor / memory / external systemsignal.type: question / claim / problem / case / report / scenario / metaphor / instructionsignal.domain: EducationOS / NewsOS / WaterOS / FinanceOS / GovernanceOS / RealityOS / Unknownsignal.stakes: low / medium / high / criticalsignal.audience: private / student / parent / public / institutional / policy / safety-criticalsignal.evidence_state: none / weak / partial / strong / verifiedsignal.time_pressure: low / medium / high / emergencysignal.creativity_need: none / low / medium / high / frontiersignal.release_target: answer / article / report / dashboard / case study / registry / memory update
5. ECU Mode Selection
FUNCTION SELECT_ECU_MODE(signal):IF signal.stakes = critical: RETURN STRICT_ECUELSE IF signal.domain IN [health, safety, law, finance, water_security, governance, public_policy]: RETURN STRICT_ECUELSE IF signal.release_target IN [public_report, formal_report, risk_report]: RETURN STRICT_ECUELSE IF signal.creativity_need IN [high, frontier]: RETURN CREATIVE_ECUELSE IF signal.release_target IN [article, teaching, case_study, parent_explanation, student_explanation]: RETURN BALANCED_ECUELSE: RETURN BALANCED_ECU
6. ECU Mode Profiles
STRICT_ECU:purpose: protect accuracy, safety, public trust, evidence integrityrequires: evidence check claim boundary uncertainty label audit trail source discipline where applicable Cerberus final gateforbids: unsupported certainty speculative release as fact metaphor treated as proof emotional overstatement hidden assumptionsBALANCED_ECU:purpose: explain clearly while preserving truth boundariesrequires: conceptual clarity reasonable checking useful synthesis visible limits repair pathway where neededallows: explanation teaching analogy structured interpretation framework connectionforbids: careless overclaim fake precision unsupported diagnosisCREATIVE_ECU:purpose: generate new models, names, metaphors, scenarios, and frontier structuresrequires: label as fact / inference / scenario / metaphor / speculation internal coherence check safety boundary Cerberus final gateallows: invention pattern extension metaphor speculative architecture frontier synthesisforbids: presenting speculation as established fact bypassing Cerberus collapsing imagination into truth claim
7. Mandatory Intake Sequence
FUNCTION ECU_INTAKE(signal):STEP 1: VocabularyOS.check(signal)STEP 2: Janitor.clean(signal)STEP 3: Sorter.classify(signal)STEP 4: Librarian.retrieve_context(signal)STEP 5: Translator.normalise(signal)STEP 6: Dispatcher.route(signal)RETURN prepared_signal
8. VocabularyOS Pre-Check
VOCABULARYOS.CHECK(signal):CHECK definition_driftCHECK frame_injectionCHECK emotional_overloadCHECK label_content_mismatchCHECK attribution_warpCHECK compression_distortionCHECK hidden_lattice_flipIF severe_language_warp_detected: flag signal.language_status = WARPED send to Sphinx for meaning gateELSE: flag signal.language_status = STABLE_ENOUGH
Core law:
NO RAW LANGUAGE MOVES UNCHECKED.
9. Worker Activation Rules
WORKER.DEFAULT_CHAIN:1. Janitor2. Sorter3. Librarian4. Translator5. Dispatcher6. Inspector7. Auditor8. Repairman9. Operator
JANITOR: remove noise separate junk from signal preserve raw originalSORTER: classify domain classify stakes classify urgency classify signal typeLIBRARIAN: retrieve memory retrieve relevant OS branch retrieve prior cases retrieve ledgersTRANSLATOR: convert raw phrasing into stable operational meaningDISPATCHER: route to OS branch / worker / guardianINSPECTOR: check task-fit and route-fitAUDITOR: check invariants, evidence, logic, contradictionsREPAIRMAN: repair missing nodes, broken routes, failed transferOPERATOR: compile final usable output
10. Movement Threshold Rules
FUNCTION DETERMINE_SIGNAL_ROUTE(prepared_signal):IF evidence_state IN [strong, verified]AND meaning_status = stableAND route_fit = clear: RETURN STRONG_ROUTEELSE IF signal has anomaly_valueOR future_warning_valueOR rare_pattern_valueOR unresolved_but_non-junk_value: RETURN SHADOW_LEDGERELSE IF signal is duplicate_spamOR incoherent_after_repair_attemptOR malicious_noiseOR irrelevant_junk: RETURN DECAY_BINELSE: RETURN SHADOW_LEDGER
Critical law:
LOW-VOLUME SIGNAL ≠ LOW-VALUE SIGNAL.
11. Shadow Ledger Rule
SHADOW_LEDGER.STORE(signal):store raw_signalstore cleaned_signalstore reason_for_nonreleasestore uncertainty_levelstore possible_future_valuestore required_evidence_for_promotionstore review_triggerstore decay_timer
A signal in Shadow Ledger is not believed.
It is preserved.
12. Decay Bin Rule
DECAY_BIN.STORE(signal):IF signal is clearly junk: mark as DECAY preserve minimal trace only do not route furtherIF signal later repeats across independent channels: re-open as Shadow Ledger candidate
This prevents over-filtering.
13. Guardian Activation Compiler
FUNCTION ACTIVATE_GUARDIANS(signal):IF signal.has_multiple_routesOR signal.requires_multi-branch_processing: wake HYDRAIF signal.meaning_unclearOR definition_unstableOR question_hidden: wake SPHINXIF signal.future_uncertainOR weak_signal_with_possible_importanceOR early_warning: wake ORACLEIF signal.trapped_in_loopOR circular_problemOR maze_structure: wake MINOTAURIF signal.needs_escape_routeOR continuity_pathOR thread_recovery: wake ARIADNEIF signal.high_value_resourceOR guarded_capabilityOR power_concentration: wake DRAGONIF signal.deep_hidden_riskOR submerged_systemic_force: wake KRAKENIF signal.load_bearingOR burden_distribution_problem: wake ATLASIF signal.requires_repairOR collapse_recoveryOR rebirth_after_failure: wake PHOENIXALWAYS before release: wake CERBERUS
14. Guardian Output Types
HYDRA_OUTPUT: route map branch map head activation listSPHINX_OUTPUT: corrected question definition lock meaning gate resultORACLE_OUTPUT: watch signal uncertainty band future review triggerMINOTAUR_OUTPUT: trap map loop detection dead-end warningARIADNE_OUTPUT: path thread exit route continuity corridorDRAGON_OUTPUT: guarded resource map concentration warning access conditionKRAKEN_OUTPUT: hidden risk trace deep-system pressure warningATLAS_OUTPUT: load map burden stress collapse pressurePHOENIX_OUTPUT: repair route rebuild plan recovery conditionCERBERUS_OUTPUT: release / hold / revise / reject
15. Audit Layer
AUDITOR.CHECK(signal, output):CHECK evidence_integrityCHECK invariant_integrityCHECK ledger_alignmentCHECK mode_complianceCHECK claim_boundaryCHECK uncertainty_labelCHECK contradictionCHECK missing_nodeCHECK inverse_lattice_riskCHECK public_consequence
IF violation_detected: send to REPAIRMANIF violation_severe: send to CERBERUS_HOLDIF unresolved_but_important: send to SHADOW_LEDGER
16. Repair Trigger Rules
REPAIRMAN.TRIGGER IF:missing_node = truebroken_route = truecontradiction_detected = truefailed_transfer = truestudent_uptake_failure = truedefinition_drift = severeledger_breach = trueoutput_unusable = truemode_mismatch = true
REPAIRMAN.ACTION:identify failure pointretrieve missing contextrepair routeadjust mode if neededcall Phoenix if collapse/rebuild requiredsend back to Auditor
17. Cerberus Final Release Gate
CERBERUS.FINAL_GATE(output, mode):IF mode = STRICT_ECU: REQUIRE verified_or_bounded_claims REQUIRE uncertainty_labels REQUIRE no unsupported factual claim REQUIRE audit_pass REQUIRE public_consequence_checkIF mode = BALANCED_ECU: REQUIRE clear_explanation REQUIRE bounded_synthesis REQUIRE no reckless certainty REQUIRE useful_output REQUIRE audit_passIF mode = CREATIVE_ECU: REQUIRE labels: fact / inference / scenario / metaphor / speculation REQUIRE internal coherence REQUIRE no false hard-truth claim REQUIRE safety boundary REQUIRE audit_passIF requirements_met: RELEASEELSE IF repair_possible: RETURN_TO_REPAIRMANELSE IF important_but_unready: STORE_IN_SHADOW_LEDGERELSE: REJECT_OR_DECAY
18. Mode Switching Compiler
FUNCTION MODE_SWITCH(section):IF section.contains_high_stakes_facts: section.mode = STRICT_ECUELSE IF section.explains_to_public: section.mode = BALANCED_ECUELSE IF section.designs_future_model: section.mode = CREATIVE_ECUELSE: section.mode = BALANCED_ECU
Example:
WATER_HEALTH_REPORT:facts_section: STRICT_ECUpublic_explanation: BALANCED_ECUfuture_dashboard_design: CREATIVE_ECUfinal_recommendation: STRICT_ECU + CERBERUS
19. Output Object
OUTPUT.OBJECT:output.id: unique output identifieroutput.mode: strict / balanced / creative / mixedoutput.domain: active OS branchoutput.claim_status: fact / inference / scenario / metaphor / speculation / unresolvedoutput.evidence_status: none / weak / partial / strong / verifiedoutput.guardians_used: listoutput.workers_used: listoutput.ledger_status: pass / warning / breach / repairedoutput.shadow_items: list of stored unresolved signalsoutput.release_status: released / held / revised / rejected / storedoutput.memory_update: none / temporary / durable / registry_lock
20. MemoryOS Update Rules
MEMORYOS.UPDATE(output):IF output creates durable framework law: store as registry_lockELSE IF output updates article queue: store as branch_statusELSE IF output records weak signal: store in Shadow LedgerELSE IF output is temporary: do not store long-termELSE: store minimal trace
Memory rule:
STORE STRUCTURE, NOT NOISE.
21. Full ECU Runtime Compiler
FUNCTION PLANETOS_ECU_RUN(signal):1. create INPUT.OBJECT2. mode = SELECT_ECU_MODE(signal)3. prepared_signal = ECU_INTAKE(signal)4. route = DETERMINE_SIGNAL_ROUTE(prepared_signal)5. IF route = DECAY_BIN: store minimal decay trace STOP6. IF route = SHADOW_LEDGER: ShadowLedger.store(prepared_signal) IF mode != STRICT_ECU: continue only as labelled weak signal ELSE: hold from public release7. guardians = ACTIVATE_GUARDIANS(prepared_signal)8. workers_process(prepared_signal)9. draft_output = Operator.compile(prepared_signal)10. audit_result = Auditor.check(draft_output)11. IF audit_result = fail: Repairman.repair(draft_output) send back to Auditor12. IF collapse_or_rebuild_needed: Phoenix.activate(draft_output)13. release_result = Cerberus.final_gate(draft_output, mode)14. IF release_result = release: output = publish_or_answer(draft_output)15. IF release_result = hold: store in Shadow Ledger or return to Repairman16. IF release_result = reject: mark decay or unresolved17. MemoryOS.update(output)18. RETURN output
22. ECU Error Codes
ECU.ERROR_CODES:ECU.001: Mode not selected before movementECU.002: Raw signal bypassed VocabularyOSECU.003: Worker chain skipped without justificationECU.004: Guardian activated before worker preparationECU.005: Weak signal deleted without Shadow Ledger reviewECU.006: Creative speculation released as factECU.007: Strict output released without auditECU.008: Cerberus bypass detectedECU.009: Memory stored noise instead of structureECU.010: Ledger breach unresolved
23. ECU Compliance Checklist
BEFORE RELEASE, CONFIRM:[ ] ECU mode selected[ ] VocabularyOS checked language[ ] Worker intake completed[ ] Route selected[ ] Shadow signals handled[ ] Guardians activated where needed[ ] Ledger checked[ ] Repair applied if needed[ ] Output labelled properly[ ] Cerberus passed[ ] MemoryOS updated correctly
24. Human-Readable Compression
The ECU Compiler answers five questions:
1. What kind of signal is this?2. How strict should the system be?3. Who handles it first?4. Which gate must wake?5. Can this safely leave the system?
25. Final Canonical Lock
PLANETOS.ECU.COMPILER.v1.0 =Mode Selection+ VocabularyOS Intake+ Worker Chain+ Movement Threshold+ Shadow Ledger+ Guardian Activation+ Ledger Audit+ Repair Loop+ Cerberus Release+ MemoryOS Update
This is the executable law layer of PlanetOS.
It makes the system:
less noisyless rigidmore creativemore boundedmore auditablemore reusablemore AI-ingestable
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
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

