Planet OS Plug-ins

Planet OS Plug-ins are the modular extensions of eduKate OS. They let Planet OS stay universal while still supporting local systems (Singapore, UK, US), specific exam boards (PSLE, O-Levels, IGCSE, IB), and specific school contexts — without turning the OS into a messy patchwork.

A plug-in is not a new OS.
A plug-in is a mapping layer that connects a local system to the universal structure.

Why Plug-ins Exist

If Planet OS is global, parents naturally ask:

“But my child is in Singapore.”
“But my child is doing IGCSE.”
“But my child is in a top school / needs higher difficulty.”
“But my child is in a weaker band and needs foundations.”

Plug-ins solve this.

Planet OS stays clean and universal.
Plug-ins localise the training content, benchmarks, and sensor tolerances.

What A Plug-in Contains

A proper Planet OS plug-in contains five things:

A local syllabus map (what is expected)
A local benchmark map (what “good” looks like)
A local sensor tolerance table (how much drift is acceptable)
A routing guide (which OS layer to start with)
A recovery guide (what recovery mode looks like locally)

This stops parents from copying random advice from different countries or systems.

The Two Plug-in Types

Planet OS supports two plug-in types.

Type 1: Curriculum & Exam Plug-ins

These align the OS to exam systems.

Examples:

Singapore PSLE plug-in
Singapore GCE O-Level plug-in
UK GCSE plug-in
Cambridge IGCSE plug-in
IB MYP/DP plug-in
US AP / SAT plug-in

These plug-ins define:

exam format expectations
grade boundaries
time constraints
common failure patterns

Type 2: Context Plug-ins

These align the OS to a student’s environment.

Examples:

Primary school plug-in
Secondary school plug-in
High-ability / advanced plug-in
Foundation / catch-up plug-in
Neurodiversity support plug-in (administered properly)
Language background plug-in (ESL / bilingual home)

These plug-ins define:

pacing
workload limits
confidence and stress tolerances
vocabulary expectations
recovery triggers

Why Plug-ins Must Not Break The System

A plug-in must never replace the universal core.
It must only map into it.

If the plug-in becomes the core, the system collapses into local noise.

That is why Planet OS always stays above:

Education OS
Vocabulary OS
ULD System

Plug-ins attach to Planet OS. They do not rewrite it.

Example: How A Singapore Plug-in Works

A Singapore plug-in would specify:

PSLE English components and timing
vocabulary expectations by primary level
AL-level outcome targets
sensor tolerances for drift (what is “normal” vs “alarm”)
when to route to ULD plateau recovery

But it still uses the same universal logic:

detect
route
diagnose
recover
rerun

Only the benchmark and tolerance values become local.

Example: How An IGCSE Plug-in Works

An IGCSE plug-in would map:

question types by paper
grade boundaries and time pressure
vocabulary and comprehension expectations
writing criteria and mark scheme interpretations

But again, the OS stays the same.

Plug-ins change the map.
They don’t change the physics.

The Plug-in Loading Rule (So Parents Don’t Panic)

Parents should load plug-ins only after the universal boot sequence.

Correct order:

Planet OS Boot (baseline + daily loop + sensors)
Identify the failing layer (Vocabulary / Education / ULD)
Load the plug-in to localise benchmarks and tolerances
Train using the same closed-loop logic

Wrong order:

jumping into an exam plug-in without fixing vocabulary or method
switching between plug-ins weekly
copying strategies from different systems at the same time

Plug-ins And AI Tools (Important Reality Check)

AI can help parents generate practice and explanations, but plug-ins must be used carefully because:

AI can be inaccurate or outdated
AI may not fully understand the child’s real constraints
if parents feed incomplete or dishonest information, outputs become unreliable

Planet OS plug-ins do not remove the need for good instruction.

They simply prevent system mismatch.

Plug-in Abuse Warning

Plug-ins can be abused when:

parents over-load a child with multiple systems
parents compare children using the wrong benchmarks
parents chase “harder” content before foundations exist

A plug-in is not a status symbol.
A plug-in is a calibration tool.