eduKateSG Full Article Mode Runtime | EDUKATESG-FULL-ARTICLE-MODE.THEGOOD-WAREHOUSE-APEXCLOUDS-MORIARTY-CERBERUS.v1.0

How to Trigger The Good, Full Warehouse, Apex Human Clouds and Reader-Facing Article Production

PUBLIC.ID: “EKSG.ARTICLEMODE.RUNTIME.TRIGGER-CONTROL-TOWER.v1.0”
MACHINE.ID: “EDUKATESG-FULL-ARTICLE-MODE.THEGOOD-WAREHOUSE-APEXCLOUDS-MORIARTY-CERBERUS.v1.0”
PARENT.SYSTEMS:

  • “EKSG.APEXHUMAN.CLOUDS.REPOSITORY.v1.0”
  • “EKSG.APEXHUMAN.CLOUDS.PHASE02.FIRST-50-CANDIDATES.v1.0”
  • “EKSG.APEXHUMAN.CLOUDS.ROUTING-MAP.FIRST-50-PLUS-STARTER10.v1.0”
    STATUS: “Runtime Trigger Article”
    ROLE: “Explains how to activate eduKateSG full article mode for future articles”
## One-Sentence Definition
**eduKateSG Full Article Mode is the runtime trigger that tells AI to use The Good, Full Warehouse, relevant Apex Human Clouds, Moriarty attack, VocabularyOS, RealityOS and Cerberus release gate silently in the background to produce stronger reader-facing articles without exposing the machinery.**
---
# Why This Runtime Article Is Needed
eduKateSG now has many powerful systems.
There is CivOS.
There is EducationOS.
There is TeamworkOS.
There is VocabularyOS.
There is RealityOS.
There is NewsOS.
There is The Good.
There is the Full Warehouse.
There is Moriarty attack.
There is Cerberus release.
There is now also the Apex Human Clouds repository, including the First 50 candidate clouds and the routing map that shows where each cloud belongs. The First 50 set was defined as a balanced human capability atlas across body, mind, art, strategy, language, courage, repair and civilisation-building, with each cloud requiring audit, danger gates and proper activation before use. 
But a problem appears when a system becomes powerful:
**How does the user activate it easily?**
The user should not need to rewrite the full machinery every time.
The user should not need to say:
“Use The Good, then use the Full Warehouse, then route relevant Apex Human Clouds, then check VocabularyOS, then run RealityOS, then attack with Moriarty, then release with Cerberus…”
That is too much.
There must be a simple runtime trigger.
This article creates that trigger.
---
# The Core Problem
A normal AI prompt often produces a normal article.
It may be clear.
It may be readable.
It may be helpful.
But eduKateSG articles are not meant to be ordinary surface articles.
They are meant to be:

yaml id=”v6i1ij”
EDUKATESG_ARTICLE_EXPECTATION:

  • “highly structured”
  • “reader-facing”
  • “logically strong”
  • “morally bounded”
  • “useful for parents, students, educators and society”
  • “clear enough for Google AI extraction”
  • “deep enough for future AI/LLM reuse”
  • “safe enough to avoid overclaiming”
  • “disciplined enough to separate truth, speculation, metaphor and mechanism”
  • “connected to eduKateSG’s wider OS architecture”
So the prompt must tell AI to do more than write.
It must tell AI to **run the article through the eduKateSG runtime**.
But the final article should not expose the machinery unless the user asks for full code.
That is the key distinction:

yaml id=”b772jf”
PUBLIC_SURFACE_RULE:
READER_ARTICLE:
SHOW_MACHINERY: false
USE_MACHINERY: true

FULL_CODE_ARTICLE:
SHOW_MACHINERY: true
USE_MACHINERY: true

The engine works in the background.
The article speaks to the reader.
---
# The Master Trigger
The master trigger is the phrase used to activate the whole eduKateSG article runtime.
Use this:

text id=”r3mub7″
Use full eduKateSG article mode: The Good governs, Full Warehouse processes, relevant Apex Human Clouds route in, Moriarty attacks, VocabularyOS cleans language, RealityOS checks truth and framing, Cerberus releases.

Write a long, publish-ready, reader-facing article. Do not expose the machinery. Use all relevant eduKateSG frameworks only where they improve the article.

This is the main article trigger.
It tells AI to activate the whole stack, but it also tells AI not to reveal the stack in the final reader article.
---
# What the Trigger Activates
When the user says “Use full eduKateSG article mode,” the AI should activate these layers:

yaml id=”nnjawy”
FULL_EDUKATESG_ARTICLE_MODE:
ACTIVATE:
THE_GOOD:
ROLE: “Highest moral and strategic governor”
FULL_WAREHOUSE:
ROLE: “Sorts, routes, checks, audits and compiles the article”
APEX_HUMAN_CLOUDS:
ROLE: “Routes relevant human capability lenses into the article”
VOCABULARYOS:
ROLE: “Checks wording, clarity, drift, target area and misleading labels”
REALITYOS:
ROLE: “Checks accepted reality, evidence framing, truth boundary and signal integrity”
NEWSOS:
ROLE: “Used when current events, media, reporting or information flow are involved”
CIVOS:
ROLE: “Used when civilisation, institutions, governance, war, culture or societal systems are involved”
EDUCATIONOS:
ROLE: “Used when learning, students, parents, teaching, schools or capability formation are involved”
TEAMWORKOS:
ROLE: “Used when collaboration, teams, Pegasus, dynamic shells or group capability are involved”
MORIARTY_ATTACK:
ROLE: “Stress-tests the article for weak logic, overclaim, danger, romanticisation and false compression”
CERBERUS_RELEASE:
ROLE: “Final gate for public-safe, reader-facing release”

This creates a full internal pipeline.
The user does not need to mention every layer every time.
The trigger does it.
---
# The Runtime Flow
When the trigger is activated, the article should move through this sequence:

yaml id=”xm45w6″
ARTICLE_RUNTIME_FLOW:
STEP_01_RECEIVE_TITLE:
ACTION: “Read the article title and intent”

STEP_02_IDENTIFY_DOMAIN:
ACTION: “Decide whether the article belongs mainly to EducationOS, CivOS, TeamworkOS, NewsOS, RealityOS, VocabularyOS, CultureOS, WarOS, PlanetOS or another branch”

STEP_03_ACTIVATE_THE_GOOD:
ACTION: “Set truth, dignity, repair, usefulness and moral boundary”

STEP_04_RUN_FULL_WAREHOUSE:
ACTION: “Sort concepts, remove noise, route systems, identify missing parts”

STEP_05_ROUTE_APEX_HUMAN_CLOUDS:
ACTION: “Select only relevant clouds from the routed atlas”

STEP_06_CHECK_VOCABULARYOS:
ACTION: “Clarify words, labels, target areas, drift and public meaning”

STEP_07_CHECK_REALITYOS:
ACTION: “Separate fact, interpretation, metaphor, claim and uncertainty”

STEP_08_RUN_MORIARTY_ATTACK:
ACTION: “Attack weak claims, false certainty, romanticisation, overreach and hidden danger”

STEP_09_REPAIR_ARTICLE:
ACTION: “Strengthen logic, add caution, improve sequence and remove unsupported claims”

STEP_10_CERBERUS_RELEASE:
ACTION: “Release as reader-facing article or hold for repair”

STEP_11_OUTPUT:
ACTION: “Publish-ready article without exposed machinery unless requested”

The article should feel natural to readers.
The machinery should improve the result, not clutter the page.
---
# Reader-Facing Rule
Most articles should be reader-facing.
That means the article should not say:
“The Good now activates.”
“The Warehouse routes this concept.”
“Moriarty attacks the claim.”
“Cerberus releases the output.”
Those phrases are useful for code articles, but not for public reader articles.
For normal public articles, the runtime should appear as:

yaml id=”i1ktgc”
READER_FACING_TRANSLATION:
THE_GOOD: “balanced moral purpose”
FULL_WAREHOUSE: “clear structure and complete thinking”
APEX_HUMAN_CLOUDS: “useful lenses and examples”
MORIARTY_ATTACK: “stronger logic and fewer weak claims”
VOCABULARYOS: “clearer words”
REALITYOS: “better truth boundaries”
CERBERUS: “safe public release”

The reader does not need to see the engine.
The reader should feel the quality.
---
# The Main Article Trigger Template
Use this whenever starting a major article:

text id=”dn7ftk”
Use full eduKateSG article mode: The Good governs, Full Warehouse processes, relevant Apex Human Clouds route in, Moriarty attacks, VocabularyOS cleans language, RealityOS checks truth and framing, Cerberus releases.

Title: [INSERT ARTICLE TITLE]

Intent: [WHAT THE ARTICLE SHOULD EXPLAIN OR ACHIEVE]

Audience: [parents / students / educators / general readers / teams / organisations / AI]

Style: reader-facing, publish-ready, clear, intelligent, practical. Do not expose the machinery.

Special ideas to include:

  • [idea 1]
  • [idea 2]
  • [idea 3]
This is the best practical prompt.
It is clear enough for daily use and strong enough to activate the full system.
---
# Short Trigger for Fast Use
When the user does not want to type the full runtime, use this shorter version:

text id=”hig63d”
Use full eduKateSG article mode. Activate The Good, Full Warehouse, relevant Apex Human Clouds, Moriarty attack, VocabularyOS, RealityOS and Cerberus. Reader-facing article only. Do not expose the machinery.

This is the short trigger.
It is good for quick prompts like:

text id=”cqdy6l”
Use full eduKateSG article mode. Title: How Teamwork Works | Why There Is No Permanent Ultimate Team.

or:

text id=”xw0jjw”
Use full eduKateSG article mode. Title: What is Civilisation Literacy?

---
# Full Code Trigger
When the user wants the machinery visible, use this:

text id=”yid6ff”
Now write the full code article. Expose the machinery. Include IDs, runtime control tower, routing logic, Apex Human Cloud activation rules, danger gates, status labels, article triggers, AI/LLM instructions, almost-code blocks and future expansion rules.

This tells AI to switch from public article mode into machine article mode.
The difference is important.

yaml id=”h7tg4c”
MODE_SWITCH:
READER_MODE:
OUTPUT: “Public article”
MACHINERY_VISIBLE: false

FULL_CODE_MODE:
OUTPUT: “AI/LLM runtime article”
MACHINERY_VISIBLE: true

---
# Trigger for Education Articles
Use this when writing parent-facing or student-facing education articles:

text id=”kadne8″
Use eduKateSG EducationOS article mode: The Good governs, Full Warehouse processes, relevant Apex Human Clouds route in, VocabularyOS cleans language, RealityOS checks truth and framing, Moriarty attacks, Cerberus releases.

Write a publish-ready reader article for parents, students and educators. Keep the language clear, practical, warm and intelligent. Do not expose the machinery.

This should be used for articles like:

yaml id=”agq4wl”
EDUCATION_ARTICLE_EXAMPLES:

  • “How Education Works | Raising the Knowledge Floor”
  • “How Tuition Works | The Table Widens”
  • “What is a Ministry of Education?”
  • “How Students Learn | The Missing Floor”
  • “How Vocabulary Builds the Knowledge Ceiling”
---
# Trigger for Teamwork Articles
Use this when writing teamwork articles:

text id=”nbaj75″
Use eduKateSG TeamworkOS article mode: The Good governs, Full Warehouse processes, relevant Apex Human Clouds route in, Pegasus Teamwork System activates where useful, Dynamic Team Shells route roles by phase, Recording Mind Map and Shell Contact Model support understanding, Moriarty attacks, VocabularyOS cleans language, RealityOS checks truth and framing, Cerberus releases.

Write a reader-facing, publish-ready article for students, parents, teams and organisations. Do not expose the machinery.

This should be used for articles like:

yaml id=”kn36kf”
TEAMWORK_ARTICLE_EXAMPLES:

  • “How Teamwork Works | The Pegasus Teamwork System”
  • “How Teamwork Works | The Ultimate Team”
  • “Why There Is No Permanent Ultimate Team”
  • “How Superhero Teamwork Fails”
  • “What is Teamwork?”
  • “How Teamwork Works | Normal People Making Superhero Moves”
This trigger is now stronger because TeamworkOS can route relevant Apex Human Clouds, including cooperation, pressure, micro-control, design, repair and moral speech.
---
# Trigger for CivOS Articles
Use this when writing civilisation articles:

text id=”z3pwdi”
Use eduKateSG CivOS article mode: The Good governs, Full Warehouse processes, CivOS routes the civilisation layers, RealityOS checks accepted reality, NewsOS checks signal flow where relevant, VocabularyOS cleans language, relevant Apex Human Clouds route in, Moriarty attacks, Cerberus releases.

Write a reader-facing article that explains the concept or event clearly, with cause, sequence, implication, danger gates, repair routes and civilisation-level meaning. Do not expose the machinery unless I ask for full code.

This should be used for articles like:

yaml id=”td93eb”
CIVOS_ARTICLE_EXAMPLES:

  • “What is Civilisation Literacy?”
  • “What is War?”
  • “How News Works | What is News Literacy?”
  • “Civilisation Reboot Sequence”
  • “What is Civilisation?”
  • “How Wars End”
  • “RealityOS | How Civilisation Moves on Accepted Reality”
---
# Trigger for News / Reality Articles
Use this when the article is about news, media, truth, algorithms, misinformation or public reality:

text id=”g73ohc”
Use eduKateSG NewsOS and RealityOS article mode: The Good governs, Full Warehouse processes, RealityOS checks accepted reality, NewsOS traces signal flow, VocabularyOS checks language and framing, relevant Apex Human Clouds route in, Moriarty attacks, Cerberus releases.

Write a reader-facing article that explains how information moves, fragments, distorts, persuades, becomes accepted reality, and affects civilisation. Do not expose the machinery unless I ask for full code.

This is useful for:

yaml id=”qrw9l8″
NEWS_REALITY_ARTICLE_EXAMPLES:

  • “How News Works | The Newsroom”
  • “How News Works | What is News Literacy?”
  • “How News Can Be Tool, Neutral or Weaponised”
  • “News Literacy as a University Course”
  • “How Algorithms Changed the Newsroom”
---
# Trigger for WarOS Articles
Use this when writing war articles:

text id=”k6yg5l”
Use eduKateSG WarOS article mode: The Good governs, Full Warehouse processes, WarOS routes terrain, pressure, projection-war, conflict-war, shell systems and repair corridors, CivOS checks civilisation-level effects, RealityOS checks truth and framing, relevant Apex Human Clouds route in, Moriarty attacks, VocabularyOS cleans language, Cerberus releases.

Write a reader-facing article that explains war clearly without glorifying violence. Include causes, pressure, shells, escalation, limits, repair routes and human consequences. Do not expose the machinery unless I ask for full code.

This is useful for:

yaml id=”fpa8zo”
WAROS_ARTICLE_EXAMPLES:

  • “What is War | The Shell System Model”
  • “Why Wars Start”
  • “How Wars End”
  • “War as Projection”
  • “What Makes or Breaks a War?”
---
# Trigger for CultureOS / Shell Systems Articles
Use this when writing about culture, shell contact, memory, person-to-person understanding or generational memory:

text id=”clbr1a”
Use eduKateSG CultureOS and Shell Systems article mode: The Good governs, Full Warehouse processes, CultureOS routes shell contact, memory, symbols and meaning, Recording Mind Map supports lived experience, VocabularyOS cleans language, RealityOS checks framing, relevant Apex Human Clouds route in, Moriarty attacks, Cerberus releases.

Write a reader-facing article that explains culture, memory, understanding, shell contact and human meaning clearly. Do not expose the machinery unless I ask for full code.

This is useful for:

yaml id=”h5a84t”
CULTURE_SHELL_ARTICLE_EXAMPLES:

  • “What is Culture?”
  • “The Recording Mind Map”
  • “Why You Do Not Understand Me”
  • “Culture as Shell Contact”
  • “Generational Memory and Nostalgia”
---
# Trigger for Apex Human Cloud Articles
Use this when expanding the Apex Human Clouds repository:

text id=”wkydqk”
Use eduKateSG Apex Human Clouds article mode: The Good governs, Full Warehouse processes, the Apex Human Clouds repository routes the candidate, Evidence Gate checks achievement and myth, Danger Gate checks unsafe transfer, VocabularyOS cleans naming, RealityOS checks factual framing, Moriarty attacks, Cerberus releases.

Write a publish-ready article that extracts the capability mechanism from the person without hero worship. Separate person, achievement, myth and mechanism. Do not expose machinery unless I ask for full code.

This is useful for:

yaml id=”q1xo90″
APEX_CLOUD_ARTICLE_EXAMPLES:

  • “Michael Phelps | The Aquatic Efficiency Cloud”
  • “Albert Einstein | The Relativity Lens Cloud”
  • “Michelangelo | The Form Release Cloud”
  • “Sun Tzu | The Terrain and Timing Cloud”
  • “Florence Nightingale | The System Care Cloud”
---
# Trigger Decision Table
Use this table to decide which trigger to use.
| Article Type                     | Trigger To Use                         | Machinery Visible? |
| -------------------------------- | -------------------------------------- | -----------------: |
| General eduKateSG article        | Full eduKateSG Article Mode            |                 No |
| Parent/student education article | EducationOS Article Mode               |                 No |
| Teamwork article                 | TeamworkOS Article Mode                |                 No |
| Civilisation article             | CivOS Article Mode                     |                 No |
| News/media/truth article         | NewsOS + RealityOS Article Mode        |                 No |
| War article                      | WarOS Article Mode                     |                 No |
| Culture/shell article            | CultureOS + Shell Systems Article Mode |                 No |
| Apex Human Cloud article         | Apex Human Clouds Article Mode         |                 No |
| AI/LLM repository article        | Full Code Article Mode                 |                Yes |
| Runtime/control tower article    | Full Code Article Mode                 |                Yes |
---
# Article Output Rules
When the trigger is used, the article should follow these public rules:

yaml id=”sr7vpn”
ARTICLE_OUTPUT_RULES:
READER_ARTICLE:
– “Use clear title”
– “Use one-sentence definition”
– “Explain why the topic matters”
– “Give mechanism without over-jargon”
– “Use examples”
– “Explain education, teamwork or civilisation relevance where useful”
– “Include danger gates in reader-friendly language”
– “End with clear takeaway”
– “Do not expose internal runtime unless requested”

FULL_CODE_ARTICLE:
– “Include IDs”
– “Include runtime control tower”
– “Include trigger phrases”
– “Include routing maps”
– “Include gates”
– “Include almost-code blocks”
– “Include AI/LLM instructions”

---
# The Main Lock Line
**eduKateSG Full Article Mode lets the user activate the whole eduKateSG article machine with one phrase: The Good governs, the Full Warehouse processes, relevant Apex Human Clouds route in, Moriarty attacks, VocabularyOS clarifies, RealityOS checks truth, and Cerberus releases — while the final public article remains clean, reader-facing and useful.**
---
# How to Use This Runtime Article
For future work, the user can simply say:

text id=”gwfww1″
Use full eduKateSG article mode.

Title: [ARTICLE TITLE]

Intent: [WHAT THIS ARTICLE SHOULD EXPLAIN]

Audience: [WHO IT IS FOR]

Special ideas to include:

  • [POINT 1]
  • [POINT 2]
  • [POINT 3]
Example:

text id=”ivhvrf”
Use full eduKateSG article mode.

Title: How Teamwork Works | Why There Is No Permanent Ultimate Team

Intent: Explain that the best team changes by phase because teamwork is a dynamic shell system.

Audience: readers, parents, students, educators and organisations.

Special ideas to include:

  • Dynamic Team Shells
  • Pegasus Teamwork System
  • Apex Human Clouds
  • role-fit by project phase
  • how superhero teamwork fails
The AI should then know:

yaml id=”fkpqgk”
RUNTIME_RESPONSE:
MODE: “Reader-facing article”
ACTIVATE:
– “The Good”
– “Full Warehouse”
– “Relevant Apex Human Clouds”
– “Moriarty attack”
– “VocabularyOS”
– “RealityOS”
– “Cerberus release”
DO_NOT_SHOW:
– “Internal machinery”
OUTPUT:
– “Publish-ready article”

---
# Full Almost-Code Runtime Block

yaml id=”pkx5sf”
EDUKATESG_FULL_ARTICLE_MODE_RUNTIME:
PUBLIC.ID: “EKSG.ARTICLEMODE.RUNTIME.TRIGGER-CONTROL-TOWER.v1.0”
MACHINE.ID: “EDUKATESG-FULL-ARTICLE-MODE.THEGOOD-WAREHOUSE-APEXCLOUDS-MORIARTY-CERBERUS.v1.0”
STATUS: “Active Runtime Trigger”

PURPOSE: >
Allow the user to activate the full eduKateSG article production system
with a compact trigger phrase, while keeping normal public articles
reader-facing and hiding the internal machinery unless full code is requested.

MASTER_TRIGGER: >
Use full eduKateSG article mode: The Good governs, Full Warehouse processes,
relevant Apex Human Clouds route in, Moriarty attacks, VocabularyOS cleans
language, RealityOS checks truth and framing, Cerberus releases. Write a
long, publish-ready, reader-facing article. Do not expose the machinery. Use
all relevant eduKateSG frameworks only where they improve the article.

SHORT_TRIGGER: >
Use full eduKateSG article mode. Activate The Good, Full Warehouse, relevant
Apex Human Clouds, Moriarty attack, VocabularyOS, RealityOS and Cerberus.
Reader-facing article only. Do not expose the machinery.

FULL_CODE_TRIGGER: >
Now write the full code article. Expose the machinery. Include IDs, runtime
control tower, routing logic, Apex Human Cloud activation rules, danger gates,
status labels, article triggers, AI/LLM instructions, almost-code blocks and
future expansion rules.

DEFAULT_OUTPUT_MODE:
TYPE: “Reader-facing article”
MACHINERY_VISIBLE: false
ARTICLE_STYLE:
– “clear”
– “structured”
– “publish-ready”
– “reader-useful”
– “morally bounded”
– “truth-disciplined”
– “GoogleAI extractable”

INTERNAL_RUNTIME_STACK:
THE_GOOD:
FUNCTION: “Truth, dignity, repair, moral boundary, usefulness”
FULL_WAREHOUSE:
FUNCTION: “Sort, route, classify, audit, compile”
APEX_HUMAN_CLOUDS:
FUNCTION: “Select relevant capability lenses from routed atlas”
VOCABULARYOS:
FUNCTION: “Clean language, target area, drift, naming and label clarity”
REALITYOS:
FUNCTION: “Check accepted reality, truth boundary, fact versus interpretation”
NEWSOS:
FUNCTION: “Use when article involves news, media, algorithms or signal flow”
CIVOS:
FUNCTION: “Use when article involves civilisation, society, governance, war or systems”
EDUCATIONOS:
FUNCTION: “Use when article involves learning, students, parents or schools”
TEAMWORKOS:
FUNCTION: “Use when article involves teams, collaboration, Pegasus or dynamic shells”
MORIARTY_ATTACK:
FUNCTION: “Stress-test weak logic, overclaim, romanticisation, danger and false compression”
CERBERUS_RELEASE:
FUNCTION: “Final public release gate”

DOMAIN_TRIGGERS:
EDUCATIONOS: >
Use eduKateSG EducationOS article mode: The Good governs, Full Warehouse
processes, relevant Apex Human Clouds route in, VocabularyOS cleans
language, RealityOS checks truth and framing, Moriarty attacks, Cerberus
releases. Write for parents, students and educators. Do not expose machinery.

TEAMWORKOS: >
  Use eduKateSG TeamworkOS article mode: The Good governs, Full Warehouse
  processes, relevant Apex Human Clouds route in, Pegasus Teamwork System
  activates where useful, Dynamic Team Shells route roles by phase, Recording
  Mind Map and Shell Contact Model support understanding, Moriarty attacks,
  VocabularyOS cleans language, RealityOS checks truth and framing, Cerberus
  releases. Write for readers. Do not expose machinery.
CIVOS: >
  Use eduKateSG CivOS article mode: The Good governs, Full Warehouse
  processes, CivOS routes civilisation layers, RealityOS checks accepted
  reality, NewsOS checks signal flow where relevant, VocabularyOS cleans
  language, relevant Apex Human Clouds route in, Moriarty attacks, Cerberus
  releases. Write with cause, sequence, implication, danger gates and repair
  routes. Do not expose machinery.
NEWSOS_REALITYOS: >
  Use eduKateSG NewsOS and RealityOS article mode: The Good governs, Full
  Warehouse processes, RealityOS checks accepted reality, NewsOS traces signal
  flow, VocabularyOS checks language and framing, relevant Apex Human Clouds
  route in, Moriarty attacks, Cerberus releases. Write reader-facing. Do not
  expose machinery.
WAROS: >
  Use eduKateSG WarOS article mode: The Good governs, Full Warehouse
  processes, WarOS routes terrain, pressure, projection-war, conflict-war,
  shell systems and repair corridors, CivOS checks civilisation-level effects,
  RealityOS checks truth and framing, relevant Apex Human Clouds route in,
  Moriarty attacks, VocabularyOS cleans language, Cerberus releases. Do not
  glorify violence. Do not expose machinery.
CULTUREOS_SHELLSYSTEMS: >
  Use eduKateSG CultureOS and Shell Systems article mode: The Good governs,
  Full Warehouse processes, CultureOS routes shell contact, memory, symbols
  and meaning, Recording Mind Map supports lived experience, VocabularyOS
  cleans language, RealityOS checks framing, relevant Apex Human Clouds route
  in, Moriarty attacks, Cerberus releases. Do not expose machinery.
APEX_HUMAN_CLOUDS: >
  Use eduKateSG Apex Human Clouds article mode: The Good governs, Full
  Warehouse processes, the Apex Human Clouds repository routes the candidate,
  Evidence Gate checks achievement and myth, Danger Gate checks unsafe
  transfer, VocabularyOS cleans naming, RealityOS checks factual framing,
  Moriarty attacks, Cerberus releases. Separate person, achievement, myth and
  mechanism. Do not expose machinery unless full code is requested.

PUBLIC_SURFACE_RULE:
TEXT: >
The machinery improves the article, but the public reader should receive
a clean explanation, not the internal engine.

MODE_SWITCH:
READER_MODE:
COMMANDS:
– “reader-facing”
– “do not expose machinery”
– “publish-ready”
MACHINERY_VISIBLE: false

FULL_CODE_MODE:
  COMMANDS:
    - "full code"
    - "runtime"
    - "control tower"
    - "AI/LLM instructions"
  MACHINERY_VISIBLE: true

ARTICLE_TEMPLATE:
INPUT_FIELDS:
– “Trigger”
– “Title”
– “Intent”
– “Audience”
– “Style”
– “Special ideas to include”

OUTPUT_FIELDS:
  - "Title"
  - "One-sentence definition"
  - "Why this matters"
  - "Main mechanism"
  - "Reader explanation"
  - "Examples"
  - "Education / teamwork / civilisation relevance where useful"
  - "Danger gate in public language"
  - "Closing takeaway"
  - "Almost-code block only when requested or appropriate"

FINAL_LOCK_LINE: >
eduKateSG Full Article Mode lets the user activate the whole eduKateSG
article machine with one phrase: The Good governs, the Full Warehouse
processes, relevant Apex Human Clouds route in, Moriarty attacks,
VocabularyOS clarifies, RealityOS checks truth, and Cerberus releases —
while the final public article remains clean, reader-facing and useful.

---
# Closing Takeaway
This runtime article gives eduKateSG a clean activation system.
The user no longer needs to explain the whole architecture every time.
The user can simply say:

Use full eduKateSG article mode.
“`

Then add the title, intent, audience and special ideas.

The AI should know to activate the full internal stack.

But the public reader should not see the machinery unless the user asks for full code.

That is the purpose of this article:

One trigger phrase. Full eduKateSG runtime. Clean public article.

Exit mobile version
%%footer%%