PUBLIC.ID:
Civilisation-Grade Report Ignition System
MACHINE.ID:
EKSG.CIVOS.REPORT.IGNITION.PLANETOS.EXPERTSOURCE10.v1.0
PURPOSE:
To make every eduKateSG Report automatically ignite the correct PlanetOS runtime so that AI writes at civilisation-grade standard instead of ordinary summary standard.
CORE.TRIGGER:
Whenever the user asks for a “Report,” “Purple Report,” “Health Report,” “Risk Report,” “Delta Report,” “Status Report,” “Civilisation Report,” or “Latest Update Report,” the system must activate Civilisation-Grade Report Mode by default.
DEFAULT MODE:
Civilisation-Grade Report Runtime
DEFAULT WARNING:
If the question is too broad, label it Orientation-Grade first, then upgrade the prompt into a civilisation-grade version.

Write a Report on...
Do a Report for...
Purple Report for...
Status Report...
Risk Report...
Civilisation Health Report...
Education Health Report...
Global Risk Report...
Banking Report...
AI Report...
Climate Report...
War Report...

1. Report Intent Detector
2. Question Gate
3. Scope Lock
4. ECU Mode Selector
5. VocabularyOS
6. ExpertSource10/10
7. PlanetOS Warehouse
8. Worker Runtime
9. HYDRA
10. ReverseHYDRA
11. FullOS
12. Micro/Meso/Macro Mapper
13. Ztime
14. Ledger of Invariants
15. StrategizeOS
16. Mythical Guardian Gate
17. Control Tower
18. MemoryOS
19. Public Report Writer
20. Almost-Code Compiler

REPORT.IGNITION.SEQUENCE:
INPUT:
User asks for report.
STEP 01:
REPORT INTENT DETECTOR
Detect whether the request is a report, update, risk readout, status check, health check, delta report, annual/monthly/daily report, or civilisation diagnosis.
STEP 02:
QUESTION GATE
Grade the prompt:
0 = unusable
1 = broad orientation
2 = bounded diagnostic
3 = source-anchored analytical
4 = civilisation-grade runtime prompt
STEP 03:
SCOPE LOCK
Lock:
domain
object
geography
time window
actors
mechanisms
source needs
output type
STEP 04:
ECU MODE SELECTOR
Choose:
Strict
Neutral
Reverse
Frontier
Hybrid
STEP 05:
VOCABULARYOS
Define terms.
Stabilise language.
Detect vague words.
Detect emotional overload.
Detect label-content mismatch.
STEP 06:
EXPERTSOURCE10/10
Find or require authoritative sources.
Separate facts from interpretation.
Check source tier.
Check currentness.
Check uncertainty.
Mark boundary.
STEP 07:
PLANETOS WAREHOUSE
Open the operating floor.
Activate workers.
Retrieve source paths.
Classify objects.
Prepare routing.
STEP 08:
WORKER RUNTIME
Janitor cleans.
Sorter classifies.
Librarian retrieves.
Translator converts.
Dispatcher routes.
Courier carries.
Inspector checks.
Auditor audits.
Repairman proposes repair.
Operator prepares release.
STEP 09:
HYDRA
Split the report into heads:
domain head
source head
Micro head
Meso head
Macro head
risk head
repair head
public output head
STEP 10:
REVERSEHYDRA
Backtrace from visible outcome to hidden causes.
Find upstream assumptions.
Find missing nodes.
Find inverse success.
Find failure trace.
STEP 11:
FULLOS
Detect:
FullOS
MissingOS
NeutralOS
NegativeOS
InverseOS
ShadowOS
OverloadOS
MislabelOS
UntranslatedOS
UnrepairedOS
STEP 12:
MICRO/MESO/MACRO MAP
Map:
human carrier layer
institutional translation layer
macro structure layer
interface leaks
frontier thresholds
STEP 13:
ZTIME
Separate:
immediate
near-term
mid-term
long-term
frontier time
STEP 14:
LEDGER OF INVARIANTS
Ask:
What must remain true?
What cannot be violated?
What boundary protects the report?
STEP 15:
STRATEGIZEOS
Choose route:
proceed
hold
probe
repair
rebuffer
reroute
abort
release
STEP 16:
MYTHICAL GUARDIAN GATE
Hydra splits.
Sphinx defines.
Oracle reads time.
Minotaur detects maze.
Ariadne preserves thread.
Atlas checks load.
Janus checks transitions.
Cerberus clears final release.
STEP 17:
CONTROL TOWER
Produce dashboard:
confidence
risk
pressure
repair
watchlist
trigger points
what would change conclusion
STEP 18:
MEMORYOS
Store reusable laws, report IDs, source paths, definitions, and missing nodes.
STEP 19:
PUBLIC REPORT WRITER
Write clear reader-facing report.
STEP 20:
ALMOST-CODE COMPILER
Add machine-readable version at bottom.

ALWAYS.ON:
1. Question Gate
2. Scope Lock
3. ECU Mode Selector
4. VocabularyOS
5. ExpertSource10/10
6. PlanetOS Warehouse
7. Worker Runtime
8. HYDRA
9. ReverseHYDRA
10. FullOS
11. Micro/Meso/Macro Mapper
12. Ztime
13. Control Tower
14. Boundary Discipline
15. Almost-Code Compiler

IF Finance / Banks / Economy:
Trigger FinanceOS + NewsOS + RealityOS + ExpertSource Strict Mode.
IF Education:
Trigger EducationOS + MicroEducation/MesoEducation/MacroEducation + Transition Gate Map.
IF War / Geopolitics:
Trigger WarOS + StrategizeOS + Fog-of-War + Off-Ramps + NewsOS.
IF Health:
Trigger HealthOS + ExpertSource Strict Mode + Public Safety Boundary.
IF Climate / Food / Water:
Trigger PlanetOS + ClimateOS / FoodOS / WaterOS + Ztime + Resource Buffer Map.
IF AI / Technology:
Trigger TechOS + AI Governance + EducationOS/WorkOS/TrustOS crosswalk.
IF Culture / Trust / Language:
Trigger CultureOS + VocabularyOS + RealityOS + RACE / Civilisational Relativity.
IF Civilisation General:
Trigger CivOS + PlanetOS + Micro/Meso/Macro + FullOS + Control Tower.
IF Purple Report:
Trigger NewsOS + RealityOS + PlanetOS + Global Risk Layer + Shadow Signal + Ztime Delta.

MISSING.NODE:
Report Intent Registry
PURPOSE:
Recognise every phrase that means “run a report.”
TRIGGER WORDS:
report
status check
health check
risk update
delta report
watchlist
latest update
daily report
monthly report
annual report
civilisation health
Purple Report
control tower readout
system diagnosis
failure trace
collapse check

MISSING.NODE:
Report Grade Gate
PURPOSE:
Stop broad prompts from pretending to be civilisation-grade.
OUTPUT:
Question Grade:
0 = unusable
1 = broad orientation
2 = diagnostic
3 = analytical
4 = civilisation-grade
REPORT GRADE:
F / D / C / B / A / A+

This is broad, so it is orientation-grade unless we narrow it.

MISSING.NODE:
Prompt Upgrader
PURPOSE:
Automatically convert weak report questions into civilisation-grade prompts.
WEAK:
What is wrong with banks?
UPGRADED:
Using IMF, BIS, FDIC, Fed, ECB/ESRB, MAS where relevant, and current banking-sector reports, write a 2026 civilisation-grade report on banking fragility, focusing on interest-rate risk, CRE, deposit stability, unrealised securities losses, NBFI/private-credit links, cyber/AI risk, confidence transmission, and sovereign-bank feedback loops.

MISSING.NODE:
Source Anchor Table
PURPOSE:
Every report needs source roles.
FIELDS:
Source Name
Source Type
Authority Tier
What It Supports
What It Cannot Support
Date
Stability
Use in Report

IMF:
Global financial stability anchor.
BIS:
Banking regulation and NBFI linkage anchor.
FDIC:
U.S. bank balance-sheet anchor.
MAS:
Singapore financial-system anchor.
OECD:
Education / economy cross-country anchor.
UNESCO:
Education and global learning anchor.
IPCC:
Climate science anchor.

MISSING.NODE:
Report Output Contract
PURPOSE:
Force every report to include the same minimum parts.
REQUIRED OUTPUT:
1. Report Build Header
2. Civilisation-Grade Confidence
3. Executive Summary
4. Source Anchor Layer
5. VocabularyOS Definitions
6. Micro/Meso/Macro Map
7. Mechanism Map
8. ReverseHYDRA Backtrace
9. FullOS State Check
10. Ztime Reading
11. Control Tower Dashboard
12. Watchlist / Triggers
13. Repair Routes
14. Final Verdict
15. Almost-Code Block

MISSING.NODE:
Watchlist Trigger Library
PURPOSE:
Every report should show what would change the conclusion.
FIELDS:
Signal
Threshold
Source
Why it matters
False-positive risk
Escalation path
Ztime horizon

BANKING WATCHLIST:
deposit outflows
CRE delinquency
unrealised securities losses
funding cost spike
NBFI stress
private-credit defaults
sovereign spread widening
cyber disruption
confidence shock

MISSING.NODE:
Repair Route Library
PURPOSE:
Reports should not only diagnose; they should identify possible repair corridors.
FIELDS:
Leak
Layer
Actor
Repair Action
Risk
Time Horizon
Success Indicator

Education leak:
Transition from primary to secondary.
Layer:
Micro + Meso.
Repair:
Foundation repair, diagnostic teaching, confidence rebuilding, teacher/tutor support.
Risk:
Overloading child with more content instead of repairing missing nodes.

MISSING.NODE:
Almost-Code Standard
PURPOSE:
Make every report AI-readable and reusable.
REQUIRED:
REPORT.ID
MACHINE.ID
LATTICE.CODE
REPORT.TYPE
QUESTION.GRADE
CONFIDENCE
SOURCE.TIER
MICRO.MAP
MESO.MAP
MACRO.MAP
REVERSEHYDRA.TRACE
FULLOS.CHECK
WATCHLIST
REPAIR.ROUTE
FINAL.VERDICT

REPORT.IGNITION.TEMPLATE.v1.0
Whenever the user asks for a Report, run:
1. Detect report type.
2. Grade the question.
3. If broad, label as Orientation-Grade and upgrade the prompt.
4. Select ECU mode.
5. Run ExpertSource10/10.
6. Run VocabularyOS.
7. Run PlanetOS Warehouse.
8. Activate Worker Runtime.
9. Run HYDRA split.
10. Run ReverseHYDRA backtrace.
11. Run FullOS detection.
12. Map Micro/Meso/Macro.
13. Run Ztime.
14. Run Ledger of Invariants.
15. Run StrategizeOS route.
16. Run Mythical Guardian gate.
17. Produce Control Tower dashboard.
18. Write public-facing report.
19. Add confidence score.
20. Add Almost-Code block.

REPORT.BUILD.HEADER:
REPORT.TITLE:
[Title]
REPORT.TYPE:
Orientation / Diagnostic / Analytical / Civilisation-Grade / Frontier
QUESTION:
[Original user question]
QUESTION.GRADE:
0 / 1 / 2 / 3 / 4
EXPECTED.REPORT.GRADE:
F / D / C / B / A / A+
ECU.MODE:
Strict / Neutral / Reverse / Frontier / Hybrid
SOURCE.REQUIREMENT:
Low / Medium / High / ExpertSource10/10
SCOPE:
Domain:
Object:
Geography:
Time Window:
Actors:
Mechanisms:
WARNING:
[None / Broad Question / Source Weakness / Time Instability / Frontier Scenario / High-Stakes]
PROMPT.UPGRADE:
[If needed]
CONFIDENCE:
[Short explanation]

Report on banks now.

REPORT INTENT:
Yes.
TRIGGER:
MAIN_PROBLEM_REPORT + RISK_REPORT
QUESTION.GRADE:
1 / Broad Orientation
ECU.MODE:
Strict + Current Finance
SOURCE.REQUIREMENT:
ExpertSource10/10
WARNING:
“Banks” and “now” are too broad for full civilisation-grade confidence.
AUTO-UPGRADED PROMPT:
Using IMF, BIS, FDIC, Fed, ECB/ESRB, MAS where relevant, and current banking-sector reports, write a 2026 civilisation-grade report on banking-system fragility, focusing on interest-rate risk, CRE, deposit stability, unrealised securities losses, private credit/NBFI links, cyber/AI risk, confidence transmission, and sovereign-bank feedback loops.
REPORT.MODE:
Proceed with orientation first, then civilisation-grade if source/time/geography are narrowed.

# [Report Title]
## 1. Civilisation-Grade Check
QUESTION:
[Original question]
QUESTION.GRADE:
[0–4]
REPORT.MODE:
[Orientation / Diagnostic / Analytical / Civilisation-Grade]
EXPECTED.REPORT.GRADE:
[A+ / A / B / C / D / F]
ECU.MODE:
[Strict / Neutral / Reverse / Frontier / Hybrid]
SOURCE.REQUIREMENT:
[ExpertSource10/10 if current/high-stakes]
SCOPE.WARNING:
[If any]
## 2. Executive Summary
MAIN FINDING:
[One clear answer]
WHAT IS STABLE:
[...]
WHAT IS WEAKENING:
[...]
WHAT IS HIDDEN:
[...]
WHAT TO WATCH:
[...]
## 3. Source Anchor Layer
SOURCE 1:
Role:
Tier:
Supports:
Limitations:
SOURCE 2:
Role:
Tier:
Supports:
Limitations:
## 4. VocabularyOS Definitions
Define the key words in the report.
Example:
“Risk” means...
“Collapse” means...
“Banks” means...
“Education failure” means...
## 5. Micro / Meso / Macro Map
MICRO:
Human, household, learner, depositor, patient, worker, family layer.
MESO:
Institution, school, bank, workplace, platform, clinic, media, agency layer.
MACRO:
State, law, economy, infrastructure, system, global layer.
INTERFACE:
Where translation or leakage happens.
## 6. Mechanism Map
PRESSURE:
[...]
TRANSMISSION:
[...]
AMPLIFIER:
[...]
BUFFER:
[...]
REPAIR:
[...]
## 7. ReverseHYDRA Backtrace
VISIBLE OUTCOME:
[...]
COMMON EXPLANATION:
[...]
HIDDEN UPSTREAM CAUSES:
[...]
MISSING ASSUMPTIONS:
[...]
FAILURE TRACE:
[...]
## 8. FullOS State Check
FULL NODES:
[...]
MISSING NODES:
[...]
NEUTRAL NODES:
[...]
NEGATIVE NODES:
[...]
INVERSE NODES:
[...]
OVERLOADED NODES:
[...]
UNREPAIRED NODES:
[...]
## 9. Ztime Reading
IMMEDIATE:
[...]
3–12 MONTHS:
[...]
1–3 YEARS:
[...]
3–10 YEARS:
[...]
LONG CIVILISATION HORIZON:
[...]
## 10. Control Tower Dashboard
PRESSURE:
Low / Medium / High
REPAIR CAPACITY:
Low / Medium / High
SOURCE CONFIDENCE:
Low / Medium / High
TRANSLATION RISK:
Low / Medium / High
TRUST RISK:
Low / Medium / High
FRONTIER RISK:
Low / Medium / High
## 11. Watchlist Triggers
Signal:
Threshold:
Why it matters:
Source:
Escalation path:
## 12. Repair Routes
MICRO REPAIR:
[...]
MESO REPAIR:
[...]
MACRO REPAIR:
[...]
INTERFACE REPAIR:
[...]
## 13. Final Verdict
ONE-LINE ANSWER:
[...]
CONFIDENCE:
[...]
WHAT WOULD CHANGE THIS CONCLUSION:
[...]
## 14. Almost-Code
[Machine-readable block]

AI INSTRUCTION:
Whenever I ask for a “Report,” do not write a normal summary.
Run eduKateSG Civilisation-Grade Report Runtime.
You must activate:
- Question Gate
- Scope Lock
- ECU Mode Selector
- VocabularyOS
- ExpertSource10/10
- PlanetOS Warehouse
- Worker Runtime
- HYDRA
- ReverseHYDRA
- FullOS
- Micro/Meso/Macro mapping
- Ztime
- Ledger of Invariants
- StrategizeOS
- Mythical Guardian Gate
- Control Tower dashboard
- MemoryOS write-back
- Almost-Code Compiler
If the question is broad:
1. label it Orientation-Grade,
2. explain why it cannot yet reach full civilisation-grade confidence,
3. upgrade the prompt into a civilisation-grade version,
4. proceed with the best available report while clearly bounding confidence.
Every report must include:
1. Civilisation-Grade Check
2. Executive Summary
3. Source Anchor Layer
4. VocabularyOS Definitions
5. Micro/Meso/Macro Map
6. Mechanism Map
7. ReverseHYDRA Backtrace
8. FullOS State Check
9. Ztime Reading
10. Control Tower Dashboard
11. Watchlist Triggers
12. Repair Routes
13. Final Verdict
14. Almost-Code Block
Do not overclaim.
Separate evidence from interpretation.
Use current sources for current, financial, legal, health, geopolitical, scientific, or high-stakes claims.
Write for normal readers first.
Put machine-readable code at the bottom.

REPORT.IGNITION.LAW:
A Report is not an article.
A Report is a routed PlanetOS run.
It must ignite:
Question Gate
ExpertSource10/10
PlanetOS Warehouse
Worker Runtime
HYDRA
ReverseHYDRA
FullOS
Micro/Meso/Macro
Ztime
Control Tower
Repair Route
Almost-Code
If these do not ignite,
the output is not civilisation-grade.

Whenever eduKateSG says “Report,” AI must switch from writing mode into runtime mode.

1. Question-Gate Engine
Decides whether the question is broad, useful, weak, or civilisation-grade.
2. Report-Runtime Engine
Writes the report using ExpertSource10/10 + PlanetOS + ReverseHYDRA + FullOS.

PUBLIC.ID:
Civilisation-Grade Report Algorithm
MACHINE.ID:
EKSG.CIVOS.REPORT.RUNTIME.CIVGRADE.v1.0
LATTICE.CODE:
LAT.CIV.REPORT.EXPERTSOURCE10.PLANETOS.REVERSEHYDRA.FULLOS.Z0-Z7.T0-T9.v1.0
DEVELOPED.BY:
eduKateSG
PURPOSE:
To produce reports that are consistently civilisation-grade by checking whether the question is precise enough, sourceable enough, scale-aware enough, time-bounded enough, and mechanism-rich enough to support high-confidence civilisation analysis.
CORE.PRINCIPLE:
A report cannot become civilisation-grade merely by sounding deep.
It becomes civilisation-grade when it is source-anchored, scale-aware, time-bounded, mechanism-mapped, reverse-audited, state-checked, and repair-oriented.

Civilisation-Grade Report =
Good Question
× ExpertSource Evidence
× Scale Precision
× Time Precision
× Mechanism Mapping
× ReverseHYDRA Backtrace
× FullOS State Detection
× Repair / Watchlist Output
× Boundary Discipline

Broad Question = Broad Answer = Lower Civilisation-Grade Ceiling

Precise Question + Strong Sources + PlanetOS Runtime = Civilisation-Grade Report

QUESTION.GATE.CHECKLIST:
1. DOMAIN:
What domain is this?
Finance, education, war, health, climate, technology, governance, culture, civilisation, etc.
2. OBJECT:
What exact thing is being studied?
Banks? U.S. regional banks? Singapore banks? Private credit? CRE exposure? Education system? AI risk?
3. GEOGRAPHY:
Where?
Global, U.S., Singapore, Europe, China, ASEAN, city-level, institution-level?
4. TIME:
When?
Today, this week, 2026, post-2023 banking crisis, last 10 years, next 12 months?
5. ACTOR:
Who is affected?
Citizens, students, banks, regulators, households, governments, children, institutions, investors?
6. LAYER:
Which layer?
Micro, Meso, Macro, interface, frontier?
7. MECHANISM:
What mechanism is being tested?
Liquidity, trust, learning, repair, debt, inflation, translation failure, source distortion, institutional drift?
8. SOURCEABILITY:
Are there authoritative sources available?
9. REPORT TYPE:
Is this an orientation, diagnostic, comparative, stress-test, forecast, or repair report?
10. OUTPUT:
What should the report produce?
Summary, risk map, failure trace, watchlist, action routes, policy implications, civilisation reading?

QUESTION.TYPE:
Too vague, emotional, or impossible to source.
EXAMPLES:
- What is wrong with everything?
- Why is the world stupid?
- Are banks doomed?
- Is education fake?
- Is civilisation collapsing tomorrow?
STATUS:
Cannot produce civilisation-grade report.
SYSTEM.RESPONSE:
This question is too broad or emotionally loaded to produce a civilisation-grade report. It can produce a loose opinion, but not a high-confidence diagnosis. Please narrow by domain, geography, time, and mechanism.

QUESTION.TYPE:
Useful but broad.
EXAMPLES:
- What is the main problem with banks now?
- What is wrong with education today?
- Why are countries struggling?
- Is AI dangerous?
- What is happening to trust?
STATUS:
Can produce orientation-grade answer only.
MAX.CIVILISATION.GRADE:
C or B-
SYSTEM.RESPONSE:
This is a broad question. I can answer it as a high-level orientation, but it will not reach full civilisation-grade confidence unless we narrow the geography, time window, source set, and mechanism.

QUESTION.TYPE:
Specific enough for meaningful report.
EXAMPLES:
- What is the main problem with U.S. regional banks in 2026?
- What is the main risk to Singapore education over the next 5 years?
- What are the top systemic risks in global food security in 2026?
- How is AI affecting student learning in Singapore secondary schools?
STATUS:
Can produce good diagnostic report.
MAX.CIVILISATION.GRADE:
B+ to A-
SYSTEM.RESPONSE:
This is bounded enough for a diagnostic report. To reach full civilisation-grade level, we should anchor it to named sources and define the failure mechanism clearly.

QUESTION.TYPE:
Specific, source-aware, and analytical.
EXAMPLES:
- Using IMF, BIS, FDIC, and Fed reports, what is the main weakness in U.S. regional banks in 2026?
- Using OECD, UNESCO, MOE Singapore, and PISA data, what is the hidden problem in education repair?
- Using IPCC, WMO, and national climate-risk reports, what is the biggest civilisation risk from climate pressure in Southeast Asia?
STATUS:
Can produce civilisation-grade report.
MAX.CIVILISATION.GRADE:
A to A
SYSTEM.RESPONSE:
This can produce a civilisation-grade report because it has domain, source layer, geography, time, and analytical purpose.

QUESTION.TYPE:
Precise, source-anchored, mechanism-focused, time-bounded, and asks for Micro/Meso/Macro, ReverseHYDRA, FullOS, and repair routes.
EXAMPLES:
- Using IMF, BIS, FDIC, Fed, and CRE data, write a 2026 civilisation-grade report on U.S. regional banks, focusing on deposit stability, unrealised securities losses, CRE exposure, NBFI links, confidence transmission, and what could trigger systemic leakage.
- Using UNESCO, OECD, PISA, MOE Singapore, and education-health reports, write a civilisation-grade report on the transition-gate failures between primary, secondary, and workforce learning in Singapore.
- Using IPCC, WMO, FAO, World Bank, and regional data, write a civilisation-grade report on Southeast Asia climate-food-water risk across Micro, Meso, Macro, and frontier-readiness layers.
STATUS:
Full civilisation-grade report possible.
MAX.CIVILISATION.GRADE:
A+ / ExpertSource10/10 candidate
SYSTEM.RESPONSE:
This is a civilisation-grade prompt. I can run ExpertSource10/10, PlanetOS, ReverseHYDRA, FullOS, and Control Tower logic on it.

CIVILISATION-GRADE CONFIDENCE:
A+ / A / B / C / D
REPORT.MODE:
Orientation / Diagnostic / Analytical / Civilisation-Grade / Frontier
WHY THIS SCORE:
Short explanation of what raises or lowers confidence.

A+:
Precise question.
Current authoritative sources.
Clear geography.
Clear time window.
Clear mechanism.
Micro/Meso/Macro mapped.
ReverseHYDRA backtrace included.
FullOS state detection included.
Repair routes included.
Uncertainty clearly bounded.
A:
Strong but missing one minor element.
B:
Useful diagnostic, but source layer or scope is incomplete.
C:
Broad orientation only.
Good for overview, not enough for strong diagnosis.
D:
Too vague, speculative, emotionally loaded, or weakly sourced.
F:
Unsafe, unsourceable, misleading, or impossible to answer responsibly.

This is a broad question, so the first answer will be orientation-grade, not full civilisation-grade.
To reach civilisation-grade level, we need to narrow at least four things:
1. geography
2. time window
3. source set
4. mechanism
I can still give a useful high-level answer, but the confidence ceiling is lower.

What is the main problem with banks now?

CIVILISATION-GRADE CHECK:
Question Grade: 1 / Broad Orientation
Expected Report Score: C+ to B-
Reason: “Banks” is too broad. It could mean global banks, U.S. regional banks, Singapore banks, central banks, commercial banks, or shadow banking. “Now” also needs a time window.
Better civilisation-grade prompt:
Using IMF, BIS, FDIC, Fed, and recent banking-sector reports, what is the main problem with U.S. regional banks in 2026, focusing on commercial real estate, deposits, unrealised securities losses, private credit, NBFI links, and confidence transmission?

BETTER.PROMPT =
Using [Authoritative Sources],
write a [Report Type]
on [Specific Object]
in [Geography]
during [Time Window],
focusing on [Mechanisms],
mapped across [Micro / Meso / Macro],
with [ReverseHYDRA Backtrace],
[FullOS Missing/Neutral/Negative/Inverse Detection],
and [Repair / Watchlist Output].

What is the main problem with banks now?

Using IMF, BIS, FDIC, Fed, ECB/ESRB, MAS where relevant, and recent banking-sector reports, write a 2026 civilisation-grade report on banking-system fragility, focusing on interest-rate risk, unrealised securities losses, commercial real estate, deposit stability, private credit, NBFI links, cyber/AI risk, confidence transmission, and possible sovereign-bank feedback loops. Separate global, U.S., European, and Singapore readings where the evidence differs.

What is wrong with education?

Using OECD, UNESCO, World Bank, PISA, MOE Singapore, and eduKateSG EducationOS sources, write a civilisation-grade report on why education systems leak capability, focusing on MicroEducation readiness, MesoEducation repair corridors, MacroEducation standards, transition gates, assessment distortion, AI shortcut risk, and workforce transfer failure.

Is AI dangerous?

Using NIST, OECD, EU AI Act materials, frontier AI safety reports, cybersecurity agencies, labour-market studies, and education data, write a civilisation-grade report on AI risk in 2026, separating productivity gain, trust erosion, misinformation, education shortcutting, labour displacement, model dependency, cyber risk, and governance lag across Micro, Meso, and Macro layers.

CIVILISATION-GRADE REPORT RUNTIME:
STEP 01:
QUESTION GATE
Grade the prompt.
STEP 02:
VOCABULARYOS
Define key terms.
Prevent fuzzy language.
Detect emotional, political, or narrative overload.
STEP 03:
ECU MODE
Choose Strict, Neutral, Reverse, Frontier, or Hybrid.
STEP 04:
EXPERTSOURCE10
Collect and rank authoritative sources.
STEP 05:
SCALE LOCK
Define Micro, Meso, Macro, interface, and frontier layers.
STEP 06:
TIME LOCK
Define immediate, near-term, mid-term, long-term, and Ztime horizons.
STEP 07:
MECHANISM MAP
Identify the real operating mechanisms.
STEP 08:
HYDRA SPLIT
Split the question into sub-heads.
STEP 09:
WORKER RUNTIME
Clean, sort, retrieve, translate, inspect, audit, and repair.
STEP 10:
REVERSEHYDRA
Backtrace from visible outcome to hidden causes.
STEP 11:
FULLOS CHECK
Detect missing, neutral, negative, inverse, overloaded, untranslated, and unrepaired nodes.
STEP 12:
LEDGER CHECK
Identify invariants and boundary conditions.
STEP 13:
STRATEGIZEOS
Choose the report route:
proceed, hold, probe, repair, rebuffer, reroute, or abort.
STEP 14:
CONTROL TOWER READOUT
Give the reader the dashboard.
STEP 15:
PUBLIC REPORT
Write in clear human language.
STEP 16:
ALMOST-CODE BLOCK
Add machine-readable structure at the bottom.

TITLE:
[Domain] Civilisation-Grade Report: [Specific Object], [Geography], [Time]
1. Civilisation-Grade Check
- Question Grade
- Report Mode
- Confidence Level
- Source Quality
- Scope Boundary
- What this report can and cannot claim
2. Executive Summary
- Main finding
- What is stable
- What is weakening
- What is hidden
- What to watch next
3. ExpertSource Anchor Layer
- Source list
- Source tier
- Source role
- Source limitation
4. VocabularyOS Definitions
- Define key terms
- Remove ambiguous language
- State what “problem,” “risk,” “collapse,” or “weakness” means here
5. Micro / Meso / Macro Map
- Micro layer
- Meso layer
- Macro layer
- Interface layer
- Frontier layer if relevant
6. Mechanism Map
- What actually moves the system?
- What transmits pressure?
- What amplifies risk?
- What buffers risk?
- What repairs risk?
7. ReverseHYDRA Backtrace
- Visible outcome
- Common explanation
- Hidden upstream causes
- Missing assumptions
- Failure trace
8. FullOS State Check
- Full nodes
- Missing nodes
- Neutral nodes
- Negative nodes
- Inverse nodes
- Overloaded nodes
- Untranslated nodes
- Unrepaired nodes
9. Ztime Reading
- Immediate
- 3–12 months
- 1–3 years
- 3–10 years
- Long civilisation horizon
10. Risk / Repair Dashboard
- Pressure
- Buffer
- Repair
- Trust
- Memory
- Translation
- Frontier readiness
11. Scenarios
- Base case
- Downside case
- Severe case
- Repair case
- Watchlist triggers
12. Civilisation Reading
- What this means for people
- What this means for institutions
- What this means for macro systems
- What this means for future continuity
13. Final Verdict
- One-line answer
- Confidence score
- What would change the answer
14. Almost-Code Version
- Machine-readable report summary

CIVILISATION-GRADE SCORECARD:
1. Question Precision:
0–10
2. Source Authority:
0–10
3. Data Quality:
0–10
4. Time Boundary:
0–10
5. Geography Boundary:
0–10
6. Mechanism Clarity:
0–10
7. Micro/Meso/Macro Mapping:
0–10
8. ReverseHYDRA Backtrace:
0–10
9. FullOS Detection:
0–10
10. Repair / Watchlist Output:
0–10
11. Public Readability:
0–10
12. Boundary Discipline:
0–10
TOTAL:
0–120
GRADE:
A+ = 108–120
A = 96–107
B = 78–95
C = 60–77
D = 40–59
F = below 40

BROAD QUESTION WARNING:
This question is useful but too broad for full civilisation-grade confidence. The answer below is an orientation map, not a final diagnostic report.

SOURCE WEAKNESS WARNING:
This report has limited source authority. It can provide a framework reading, but not a strong evidence-grade conclusion.

TIME INSTABILITY WARNING:
The facts may change quickly. This report should be treated as a time-stamped reading, not a permanent conclusion.

FRONTIER INTERPRETATION WARNING:
This report includes eduKateSG / CivOS interpretive extensions. These should be separated from established mainstream evidence.

NOT CIVILISATION-GRADE YET:
The question needs a narrower object, geography, time window, source set, or mechanism before it can reach civilisation-grade confidence.

What is the main systemic risk in [domain] for [geography] in [time window], using [authoritative sources], and how does it transmit across Micro, Meso, and Macro layers?

What is the main systemic risk in U.S. regional banking in 2026?
What is the main systemic risk in Singapore education over the next 5 years?
What is the main systemic risk in global food security in 2026?

Why did [system/outcome] fail, and what upstream causes does ReverseHYDRA reveal?

Why do students leak out of the education system between primary and secondary school?
Why do banks that look capitalised still fail under confidence shocks?
Why do public health systems fail to detect slow-moving risk?

Where does capability leak when [carrier A] moves into [carrier B]?

Where does education capability leak between school and workforce?
Where does financial risk leak from non-bank lenders back into banks?
Where does public trust leak between government policy and citizen behaviour?

Which nodes are missing, neutral, negative, or inverse in [system]?

Which missing nodes explain weak education repair?
Which inverse success signals exist in modern banking?
Which neutral institutions appear active but do not repair civilisation capability?

How does [risk] change across immediate, near-term, mid-term, and long-term civilisation time?

How does AI risk change from 2026 to 2030 across education, work, trust, and governance?
How does banking fragility change across 3 months, 1 year, and 5 years?
How does climate-food-water risk change across Southeast Asia over the next decade?

What repair corridors can reduce leakage in [system]?

What repair corridors reduce student leakage in secondary mathematics?
What repair corridors reduce banking-system confidence risk?
What repair corridors reduce public trust collapse?

Using [authoritative sources],
write a civilisation-grade report on [specific object]
in [geography]
during [time window],
focusing on [mechanisms].
Run:
- ExpertSource10/10
- VocabularyOS
- Micro/Meso/Macro mapping
- ReverseHYDRA backtrace
- FullOS missing/neutral/negative/inverse detection
- Ztime analysis
- Control Tower dashboard
- repair/watchlist output
Also include:
- confidence grade
- source boundary
- what would change the conclusion
- Almost-Code block at the bottom

What is the main problem with banks now?

QUESTION.GRADE:
1 / Broad Orientation
MAX.REPORT.GRADE:
C+ to B-
WARNING:
This can produce a useful orientation answer, but not a full civilisation-grade report because “banks” and “now” are too broad.

Using IMF, BIS, Basel Committee, FDIC, Federal Reserve, ECB/ESRB, MAS where relevant, and recent banking-sector reports, write a civilisation-grade report on banking-system fragility in 2026.
Focus on:
interest-rate risk
unrealised securities losses
commercial real estate
deposit stability
private credit
NBFI linkages
cyber/AI risk
confidence transmission
sovereign-bank feedback loops
Separate:
global banks
U.S. regional banks
European banks
Singapore banks
shadow banking / NBFI layer
Run:
ExpertSource10/10
ReverseHYDRA
FullOS
Micro/Meso/Macro
Ztime
Control Tower
repair/watchlist output

QUESTION.GRADE:
4 / Civilisation-Grade Runtime Prompt
MAX.REPORT.GRADE:
A to A+
WHY:
Specific domain, source set, mechanisms, time window, system layers, and output requirements.

What is wrong with education?

QUESTION.GRADE:
1 / Broad Orientation
MAX.REPORT.GRADE:
C+ to B-

Using OECD, UNESCO, World Bank, PISA, MOE Singapore, and eduKateSG EducationOS sources, write a civilisation-grade report on how education systems leak capability during transition gates.
Focus on:
MicroEducation readiness
MesoEducation repair corridors
MacroEducation standards
assessment compression
AI shortcutting
teacher bandwidth
family support variance
school-to-workforce transfer
Run:
ExpertSource10/10
ReverseHYDRA
FullOS
Micro/Meso/Macro
Ztime
Control Tower
repair route
Almost-Code summary

QUESTION.GRADE:
4 / Civilisation-Grade Runtime Prompt
MAX.REPORT.GRADE:
A to A+

FUNCTION CIVILISATION_GRADE_REPORT(USER_QUESTION):
    Q = USER_QUESTION
    STEP 1:
    RUN QUESTION_GATE(Q)
    QUESTION_GATE OUTPUT:
        domain
        object
        geography
        time_window
        actors
        mechanism
        sourceability
        report_type
        output_need
        ambiguity_level
    STEP 2:
    ASSIGN QUESTION_GRADE
        IF domain undefined OR object undefined:
            grade = 0 or 1
        IF domain defined but object/geography/time broad:
            grade = 1
        IF object + geography + time defined:
            grade = 2
        IF source set + mechanism defined:
            grade = 3
        IF source set + mechanism + Micro/Meso/Macro + ReverseHYDRA + FullOS + output requested:
            grade = 4
    STEP 3:
    ASSIGN MAX_REPORT_GRADE
        grade 0 -> F/D
        grade 1 -> C/B-
        grade 2 -> B+/A-
        grade 3 -> A
        grade 4 -> A+
    STEP 4:
    IF QUESTION_GRADE < 3:
        OUTPUT WARNING:
        "This is not yet civilisation-grade. It is orientation or diagnostic level."
        GENERATE BETTER_PROMPT:
        Better prompt =
        Using [sources],
        write a [report type]
        on [object]
        in [geography]
        during [time_window],
        focusing on [mechanisms],
        mapped across Micro/Meso/Macro,
        with ReverseHYDRA, FullOS, Ztime, Control Tower, and repair output.
    STEP 5:
    RUN VOCABULARYOS(Q)
        define terms
        remove ambiguity
        detect emotional load
        detect frame distortion
    STEP 6:
    SELECT ECU MODE
        strict if current / financial / legal / health / public safety
        neutral if framework synthesis
        reverse if backtrace needed
        frontier if speculative
        hybrid if mixed
    STEP 7:
    RUN EXPERTSOURCE10
        collect sources
        rank sources
        separate primary / secondary / commentary
        define source limitations
        mark uncertainty
    STEP 8:
    RUN HYDRA_SPLIT
        split into domain heads
        split into Micro/Meso/Macro heads
        split into mechanism heads
        split into source heads
        split into repair heads
    STEP 9:
    RUN WORKER_RUNTIME
        Cleaner cleans
        Sorter classifies
        Librarian retrieves
        Translator converts
        Dispatcher routes
        Courier moves
        Inspector checks
        Auditor audits
        Repairman builds repair
        Operator prepares output
    STEP 10:
    RUN MICRO_MESO_MACRO_MAP
        Micro = human / household / carrier layer
        Meso = institutions / markets / agencies / platforms
        Macro = state / economy / global / law / infrastructure / memory
        Interface = leakage between layers
        Frontier = future threshold
    STEP 11:
    RUN MECHANISM_MAP
        identify pressure
        identify transmission
        identify amplification
        identify buffer
        identify repair
        identify failure trigger
    STEP 12:
    RUN REVERSEHYDRA
        visible outcome
        common explanation
        hidden upstream causes
        missing assumptions
        source weaknesses
        failure trace
        possible inverse success
    STEP 13:
    RUN FULLOS
        full nodes
        missing nodes
        neutral nodes
        negative nodes
        inverse nodes
        overloaded nodes
        untranslated nodes
        unrepaired nodes
    STEP 14:
    RUN ZTIME
        immediate
        3-12 months
        1-3 years
        3-10 years
        civilisation horizon
    STEP 15:
    RUN CONTROL_TOWER
        source quality
        pressure level
        repair capacity
        confidence
        watchlist
        trigger points
        what changes conclusion
    STEP 16:
    WRITE PUBLIC REPORT
        executive summary
        source anchor
        mechanism explanation
        Micro/Meso/Macro map
        ReverseHYDRA trace
        FullOS check
        Ztime reading
        repair/watchlist
        verdict
    STEP 17:
    APPEND ALMOST_CODE
        machine-readable summary
        confidence grade
        source boundary
        route map
        repair map
        watchlist
    RETURN REPORT

If the question is broad, warn the reader.
If the question is precise, run the machine.
If the sources are weak, lower the grade.
If the sources are strong but the synthesis is poor, improve the synthesis.
If the synthesis is strong but the sources are weak, do not overclaim.
If the report has source authority + mechanism clarity + Micro/Meso/Macro map + ReverseHYDRA + FullOS + repair route, it can become civilisation-grade.

eduKateSG Civilisation-Grade Report Standard:
We do not call every answer civilisation-grade.
A civilisation-grade report must pass:
1. Question Gate
2. Source Gate
3. Scale Gate
4. Time Gate
5. Mechanism Gate
6. ReverseHYDRA Gate
7. FullOS Gate
8. Repair Gate
9. Boundary Gate
10. Public Clarity Gate
If it fails, we label it honestly:
orientation-grade
diagnostic-grade
analytical-grade
or not yet civilisation-grade.
This protects trust.
It also makes the best reports stronger than ordinary summaries because they do not only say what happened.
They show:
where it happened,
why it happened,
which layer carried the load,
which interface leaked,
which source supports the claim,
which hidden cause may be upstream,
which node is missing,
which repair route exists,
and what to watch next.

User asks a question
→ system detects question type
→ system grades whether it can become civilisation-grade
→ system upgrades weak questions
→ system selects report build
→ system writes the correct report

PUBLIC.ID:
Civilisation-Grade Report Trigger System
MACHINE.ID:
EKSG.CIVOS.REPORT.TRIGGER.BUILD.v1.0
PURPOSE:
To detect what kind of question the user is asking and route it into the correct report build.
CORE RULE:
The question determines the ceiling.
The source layer determines the authority.
The runtime determines the civilisation-grade value.

WHEN USER ASKS:
"What is the main problem with X?"
TRIGGER:
MAIN_PROBLEM_REPORT
SYSTEM CHECKS:
Is X broad?
Is geography defined?
Is time defined?
Is source set defined?
Is mechanism defined?
IF BROAD:
Return orientation-grade warning + better prompt.
IF PRECISE:
Run civilisation-grade diagnostic report.

WHEN USER ASKS:
"Why is X failing?"
TRIGGER:
FAILURE_TRACE_REPORT
SYSTEM CHECKS:
Visible outcome.
Common explanation.
Hidden upstream causes.
Micro/Meso/Macro leakage.
ReverseHYDRA backtrace.
FullOS missing nodes.
Repair route.

WHEN USER ASKS:
"What changed?"
TRIGGER:
DELTA_REPORT
SYSTEM CHECKS:
Previous baseline.
Current condition.
Delta size.
Delta speed.
Ztime horizon.
What shifted.
What stayed stable.
What signal is noise.

WHEN USER ASKS:
"What should we watch?"
TRIGGER:
WATCHLIST_REPORT
SYSTEM CHECKS:
Trigger signals.
Weak signals.
Shadow noise.
Thresholds.
Early warnings.
Escalation paths.

WHEN USER ASKS:
"What can be done?"
TRIGGER:
REPAIR_ROUTE_REPORT
SYSTEM CHECKS:
Leak location.
Repair corridor.
Actor responsibility.
Micro/Meso/Macro intervention.
Time horizon.
Risk of wrong repair.

TRIGGER.ID:
MAIN_PROBLEM_REPORT
USER PHRASES:
What is the main problem with banks now?
What is the main issue with education today?
What is the biggest problem in AI?
What is the main weakness of Singapore education?
What is the biggest risk to civilisation now?
QUESTION QUALITY:
Usually broad unless narrowed.
DEFAULT GRADE:
C+ to B-
CAN BECOME CIVILISATION-GRADE IF:
Object is specific.
Geography is defined.
Time window is defined.
Source set is defined.
Mechanism is defined.
REPORT BUILD:
1. Broad question warning
2. Prompt upgrade
3. ExpertSource anchor
4. Main risk cluster
5. Micro/Meso/Macro map
6. ReverseHYDRA backtrace
7. FullOS missing/inverse node check
8. Ztime watchlist
9. Final verdict

WEAK:
What is the main problem with banks now?
CIVILISATION-GRADE:
Using IMF, BIS, FDIC, Fed, ECB/ESRB, MAS where relevant, and recent banking-sector reports, write a 2026 civilisation-grade report on banking-system fragility, focusing on interest-rate risk, commercial real estate, deposit stability, unrealised securities losses, private credit, NBFI linkages, cyber/AI risk, confidence transmission, and sovereign-bank feedback loops.

TRIGGER.ID:
FAILURE_TRACE_REPORT
USER PHRASES:
Why did this fail?
Why is education failing?
Why are students leaking out?
Why did banks collapse?
Why is trust collapsing?
Why is policy not working?
Why do institutions look active but fail to repair?
QUESTION QUALITY:
Good for ReverseHYDRA.
DEFAULT GRADE:
B to A-
CAN BECOME CIVILISATION-GRADE IF:
Failure object is named.
Time period is clear.
Evidence sources exist.
Failure mechanism is testable.
REPORT BUILD:
1. Visible failure
2. Common explanation
3. ReverseHYDRA backtrace
4. Micro leak
5. Meso leak
6. Macro leak
7. Interface leak
8. FullOS state check
9. Transition gate analysis
10. Repair route

WEAK:
Why is education failing?
CIVILISATION-GRADE:
Using OECD, UNESCO, PISA, World Bank, MOE Singapore, and eduKateSG EducationOS sources, write a civilisation-grade failure-trace report on where education systems leak capability between primary, secondary, tertiary, and workforce transition gates.

TRIGGER.ID:
DELTA_REPORT
USER PHRASES:
What changed?
What happened this year?
What is different now?
How has the situation shifted?
What changed since the last report?
What is the delta from last year?
QUESTION QUALITY:
Strong if baseline exists.
DEFAULT GRADE:
B+ to A
CAN BECOME CIVILISATION-GRADE IF:
Previous baseline exists.
Current data exists.
Delta timeframe is defined.
Signal vs noise is separated.
REPORT BUILD:
1. Baseline
2. Current state
3. Delta summary
4. Speed of change
5. Direction of change
6. Pressure vs repair
7. What is new
8. What is worsening
9. What is stabilising
10. What to watch next

Purple Report Daily
Purple Report Monthly
Purple Report Annual
Education Health Report
Global Risk Delta Report
Banking Risk Delta Report
AI Risk Delta Report
Climate Risk Delta Report
Trust Delta Report

TRIGGER.ID:
RISK_REPORT
USER PHRASES:
What is the risk?
How dangerous is this?
Could this collapse?
What could go wrong?
What is the biggest threat?
Is this a systemic risk?
Is this becoming unstable?
QUESTION QUALITY:
Good, but must define risk object.
DEFAULT GRADE:
B to A-
CAN BECOME CIVILISATION-GRADE IF:
Risk source is clear.
Affected actors are clear.
Transmission mechanism is clear.
Time horizon is clear.
REPORT BUILD:
1. Risk definition
2. Risk source
3. Transmission route
4. Amplifiers
5. Buffers
6. Micro/Meso/Macro exposure
7. Trigger points
8. Scenario ladder
9. Watchlist
10. Confidence grade

WEAK:
Is AI dangerous?
CIVILISATION-GRADE:
Using NIST, OECD, EU AI Act materials, frontier AI safety reports, cybersecurity agencies, labour-market studies, and education data, write a civilisation-grade AI risk report for 2026–2030 across education, work, trust, governance, cyber risk, and institutional repair capacity.

TRIGGER.ID:
WATCHLIST_REPORT
USER PHRASES:
What should we watch?
What are the warning signs?
What are the trigger points?
What signals matter?
What would change the conclusion?
What is the early warning dashboard?
QUESTION QUALITY:
Very strong for civilisation-grade reporting.
DEFAULT GRADE:
A-
CAN BECOME A+ IF:
Sources are strong.
Thresholds are defined.
Signals are separated by time horizon.
REPORT BUILD:
1. Main watchlist
2. Signal type
3. Source
4. Threshold
5. Why it matters
6. What it would trigger
7. False-positive risk
8. Ztime horizon
9. Control Tower dashboard

WATCHLIST:
Signal
Current reading
Threshold
Why it matters
Escalation path
Confidence

TRIGGER.ID:
REPAIR_ROUTE_REPORT
USER PHRASES:
What can be done?
How do we fix it?
What is the repair path?
How can civilisation repair this?
What should schools/governments/institutions do?
What is the best intervention?
QUESTION QUALITY:
High value but dangerous if not bounded.
DEFAULT GRADE:
B+ to A
CAN BECOME CIVILISATION-GRADE IF:
Problem diagnosis is already strong.
Actors are defined.
Repair layer is defined.
Risks of intervention are included.
REPORT BUILD:
1. Problem location
2. Leak type
3. Actor map
4. Repair principle
5. Micro repair
6. Meso repair
7. Macro repair
8. Transition gate repair
9. Failure risk of repair
10. Implementation watchlist

Do not repair Macro problems with only Micro tools.
Do not repair Micro problems with only Macro slogans.
Do not bypass Meso translation.

TRIGGER.ID:
COMPARATIVE_REPORT
USER PHRASES:
Compare this to high-level research.
Which is better?
Which country is stronger?
Which system performs better?
How does Singapore compare?
How does eduKateSG compare to official reports?
QUESTION QUALITY:
Strong if comparison objects are named.
DEFAULT GRADE:
B+ to A
CAN BECOME CIVILISATION-GRADE IF:
Comparison criteria are explicit.
Sources are balanced.
Same scale is used.
REPORT BUILD:
1. Comparison objects
2. Same-scale rule
3. Criteria
4. Source layer
5. Strengths
6. Weaknesses
7. What each sees
8. What each misses
9. Score table
10. Final verdict

Compare IMF/BIS/FDIC banking reports with eduKateSG PlanetOS synthesis on 2026 banking fragility, scoring authority, data depth, mechanism clarity, public readability, hidden failure detection, and repair usefulness.

TRIGGER.ID:
COLLAPSE_CHECK_REPORT
USER PHRASES:
Is civilisation collapsing?
Are banks collapsing?
Is education collapsing?
Is trust collapsing?
Is the system breaking?
Are we near failure?
QUESTION QUALITY:
Emotionally loaded but useful if disciplined.
DEFAULT GRADE:
C+ if broad.
A- if bounded.
REPORT BUILD:
1. Collapse definition
2. What collapse is not
3. Current stress
4. Buffer level
5. Repair capacity
6. Drift rate
7. Failure thresholds
8. False alarm risk
9. Scenario ladder
10. Verdict

Collapse Risk rises when:
Drift Load > Repair Capacity
for long enough
across critical nodes
with low buffer
and poor translation
and weak trust.

TRIGGER.ID:
SYSTEM_MAP_REPORT
USER PHRASES:
How does this system work?
Map the system.
What are the parts?
What is the architecture?
How do the components connect?
Where are the missing nodes?
QUESTION QUALITY:
Excellent for CivOS / PlanetOS.
DEFAULT GRADE:
A-
REPORT BUILD:
1. System definition
2. Component map
3. Micro/Meso/Macro layers
4. Actors
5. Flows
6. Bottlenecks
7. Leaks
8. Missing nodes
9. FullOS state map
10. Control Tower diagram in text

Education system
Banking system
AI governance system
Health system
Food system
Climate system
News system
Trust system
Civilisation system

TRIGGER.ID:
FRONTIER_REPORT
USER PHRASES:
What happens next?
Where is this going?
What is the future of this?
Can civilisation reach the next phase?
What is the frontier risk?
What is the P4 path?
QUESTION QUALITY:
High value, but must be labelled as forecast / scenario.
DEFAULT GRADE:
B to A-
CAN BECOME CIVILISATION-GRADE IF:
Evidence baseline is strong.
Scenarios are bounded.
Forecast is not overclaimed.
REPORT BUILD:
1. Current baseline
2. Direction of travel
3. Scenario set
4. Frontier threshold
5. Required buffers
6. Missing capabilities
7. Trigger events
8. Failure paths
9. Repair paths
10. Confidence boundary

This is a frontier/scenario report, not a certainty claim.

REPORT.TYPE:
Orientation Report
QUESTION GRADE:
1
CONFIDENCE:
C+ to B-
USE:
Give the reader a map, not a final diagnosis.
STRUCTURE:
1. Broad Question Warning
2. What the question could mean
3. Best high-level answer
4. Main risk cluster
5. What must be narrowed
6. Better civilisation-grade prompt
7. Short final answer

REPORT.TYPE:
Diagnostic Report
QUESTION GRADE:
2
CONFIDENCE:
B to A-
STRUCTURE:
1. Question grade
2. Scope boundary
3. Main diagnosis
4. Micro/Meso/Macro map
5. Failure mechanism
6. ReverseHYDRA trace
7. FullOS check
8. Repair route
9. Watchlist

REPORT.TYPE:
ExpertSource Analytical Report
QUESTION GRADE:
3
CONFIDENCE:
A-
STRUCTURE:
1. Question grade
2. Source anchor layer
3. What the sources agree on
4. What the sources disagree on
5. Mechanism map
6. Micro/Meso/Macro map
7. ReverseHYDRA trace
8. FullOS state check
9. Control Tower reading
10. Final verdict

REPORT.TYPE:
Civilisation-Grade Report
QUESTION GRADE:
4
CONFIDENCE:
A to A+
STRUCTURE:
1. Civilisation-Grade Check
2. Executive Summary
3. Source Anchor Layer
4. VocabularyOS Definitions
5. Micro/Meso/Macro Map
6. Mechanism Map
7. ReverseHYDRA Backtrace
8. FullOS State Check
9. Ztime Reading
10. Risk / Repair Dashboard
11. Scenarios
12. Watchlist
13. Civilisation Reading
14. Final Verdict
15. Almost-Code Block

FUNCTION ROUTE_REPORT(USER_QUESTION):
    DETECT_TRIGGER(USER_QUESTION)
    IF trigger = MAIN_PROBLEM_REPORT:
        IF question is broad:
            build = ORIENTATION_REPORT
        ELSE:
            build = DIAGNOSTIC_REPORT or CIVILISATION_GRADE_REPORT
    IF trigger = FAILURE_TRACE_REPORT:
        build = REVERSEHYDRA_FAILURE_REPORT
    IF trigger = DELTA_REPORT:
        build = DELTA_REPORT
    IF trigger = RISK_REPORT:
        build = RISK_AND_SCENARIO_REPORT
    IF trigger = WATCHLIST_REPORT:
        build = CONTROL_TOWER_WATCHLIST
    IF trigger = REPAIR_ROUTE_REPORT:
        build = REPAIR_ROUTE_REPORT
    IF trigger = COMPARATIVE_REPORT:
        build = COMPARATIVE_SCORE_REPORT
    IF trigger = COLLAPSE_CHECK_REPORT:
        build = COLLAPSE_THRESHOLD_REPORT
    IF trigger = SYSTEM_MAP_REPORT:
        build = SYSTEM_ARCHITECTURE_REPORT
    IF trigger = FRONTIER_REPORT:
        build = FRONTIER_SCENARIO_REPORT
    RETURN build

TRIGGER:
BROAD_QUESTION_WARNING
TEXT:
This is a broad question. I can answer it as an orientation report, but it will not reach full civilisation-grade confidence until we narrow the object, geography, time window, source set, and mechanism.
CURRENT GRADE:
C+ to B-
TO UPGRADE:
Add:
1. specific object
2. geography
3. time window
4. source set
5. mechanism

TRIGGER:
STRICT_SOURCE_WARNING
TEXT:
This is current and high-stakes, so it needs ExpertSource10/10. I should not answer it from memory or general opinion.

TRIGGER:
FRONTIER_WARNING
TEXT:
This enters forecast/scenario territory. The answer can be useful, but it must be labelled as a bounded scenario, not a certainty claim.

TRIGGER:
REPAIR_BOUNDARY_WARNING
TEXT:
This asks for intervention. The report must separate diagnosis from action, and it must state risks of wrong repair.

Use ExpertSource10/10.
Make this civilisation-grade.
Use PlanetOS full runtime.
Run ReverseHYDRA.
Run FullOS missing-node detection.
Map Micro, Meso, and Macro layers.
Add Ztime.
Add Control Tower dashboard.
Separate evidence from interpretation.
Show what would change the conclusion.
Add repair routes.
Add watchlist triggers.
Add Almost-Code at the bottom.

Using [authoritative sources], write a civilisation-grade report on [specific object] in [geography] during [time window], focusing on [mechanisms].
Run ExpertSource10/10, VocabularyOS, Micro/Meso/Macro mapping, ReverseHYDRA backtrace, FullOS missing/neutral/negative/inverse detection, Ztime analysis, Control Tower dashboard, repair/watchlist output, confidence grade, and Almost-Code summary.

USER:
What is the main problem with banks now?
TRIGGER:
MAIN_PROBLEM_REPORT
QUESTION GRADE:
1 / Broad Orientation
BUILD:
Orientation Report
AUTO-RESPONSE:
This is broad. It can produce a high-level map, but not full civilisation-grade confidence.
PROMPT UPGRADE:
Using IMF, BIS, Basel Committee, FDIC, Federal Reserve, ECB/ESRB, MAS where relevant, and recent banking-sector reports, write a 2026 civilisation-grade report on banking-system fragility, focusing on interest-rate risk, unrealised securities losses, commercial real estate, deposit stability, private credit, NBFI linkages, cyber/AI risk, confidence transmission, and sovereign-bank feedback loops.

USER:
What is wrong with education?
TRIGGER:
MAIN_PROBLEM_REPORT + FAILURE_TRACE_REPORT
QUESTION GRADE:
1 / Broad Orientation
BUILD:
Orientation Report, then prompt upgrade.
PROMPT UPGRADE:
Using OECD, UNESCO, World Bank, PISA, MOE Singapore, and eduKateSG EducationOS sources, write a civilisation-grade report on how education systems leak capability at transition gates, focusing on MicroEducation readiness, MesoEducation repair corridors, MacroEducation standards, assessment compression, AI shortcutting, teacher bandwidth, family support variance, and school-to-workforce transfer.

USER:
Is civilisation collapsing?
TRIGGER:
COLLAPSE_CHECK_REPORT
QUESTION GRADE:
1 / Broad, emotionally loaded
BUILD:
Collapse Orientation Report
PROMPT UPGRADE:
Using recent global risk, economic, climate, conflict, public health, technology, and trust reports, write a civilisation-grade collapse-threshold report for 2026, separating stress, drift, buffer, repair capacity, and false-alarm signals across Micro, Meso, Macro, and Ztime layers.

USER:
How can we fix weak education?
TRIGGER:
REPAIR_ROUTE_REPORT
QUESTION GRADE:
2 / Diagnostic
BUILD:
Repair Route Report
PROMPT UPGRADE:
Using OECD, UNESCO, PISA, MOE Singapore, and eduKateSG EducationOS sources, write a repair-route report on how to reduce learning leakage in Singapore education across MicroEducation, MesoEducation, MacroEducation, transition gates, teacher bandwidth, tuition support, assessment pressure, and AI shortcut risk.

REPORT.BUILD.HEADER:
QUESTION:

QUESTION:
What is the main problem with banks now?
TRIGGER:
MAIN_PROBLEM_REPORT
QUESTION.GRADE:
1 / Broad Orientation
EXPECTED.REPORT.GRADE:
C+ to B-
REPORT.MODE:
Orientation
ECU.MODE:
Strict + Current Finance
SOURCE.REQUIREMENT:
ExpertSource10/10
SCOPE.WARNING:
“Banks” and “now” are too broad for full civilisation-grade confidence.
PROMPT.UPGRADE:
Using IMF, BIS, FDIC, Fed, ECB/ESRB, MAS where relevant...

FUNCTION CIVILISATION_REPORT_TRIGGER_BUILD(USER_QUESTION):
    INPUT = USER_QUESTION
    STEP 1:
    DETECT QUESTION TYPE
        IF contains "main problem" OR "biggest problem" OR "main issue":
            TRIGGER = MAIN_PROBLEM_REPORT
        IF contains "why fail" OR "why failing" OR "why did it fail":
            TRIGGER = FAILURE_TRACE_REPORT
        IF contains "what changed" OR "delta" OR "different now":
            TRIGGER = DELTA_REPORT
        IF contains "risk" OR "danger" OR "threat" OR "could go wrong":
            TRIGGER = RISK_REPORT
        IF contains "watch" OR "warning signs" OR "trigger points":
            TRIGGER = WATCHLIST_REPORT
        IF contains "fix" OR "repair" OR "what can be done":
            TRIGGER = REPAIR_ROUTE_REPORT
        IF contains "compare" OR "which is better":
            TRIGGER = COMPARATIVE_REPORT
        IF contains "collapse" OR "breaking":
            TRIGGER = COLLAPSE_CHECK_REPORT
        IF contains "how does it work" OR "map" OR "architecture":
            TRIGGER = SYSTEM_MAP_REPORT
        IF contains "future" OR "what happens next" OR "where is this going":
            TRIGGER = FRONTIER_REPORT
    STEP 2:
    RUN QUESTION GATE
        CHECK:
        domain
        object
        geography
        time window
        actor
        mechanism
        source set
        output requirement
    STEP 3:
    ASSIGN QUESTION GRADE
        IF object missing AND domain unclear:
            QUESTION_GRADE = 0
        IF domain exists but object/geography/time broad:
            QUESTION_GRADE = 1
        IF object + geography + time defined:
            QUESTION_GRADE = 2
        IF source set + mechanism defined:
            QUESTION_GRADE = 3
        IF source set + mechanism + Micro/Meso/Macro + ReverseHYDRA + FullOS + repair/watchlist requested:
            QUESTION_GRADE = 4
    STEP 4:
    ASSIGN REPORT BUILD
        IF QUESTION_GRADE = 0:
            BUILD = NOT_REPORTABLE_OR_REWRITE_PROMPT
        IF QUESTION_GRADE = 1:
            BUILD = ORIENTATION_REPORT
        IF QUESTION_GRADE = 2:
            BUILD = DIAGNOSTIC_REPORT
        IF QUESTION_GRADE = 3:
            BUILD = EXPERTSOURCE_ANALYTICAL_REPORT
        IF QUESTION_GRADE = 4:
            BUILD = FULL_CIVILISATION_GRADE_REPORT
    STEP 5:
    IF QUESTION_GRADE < 3:
        OUTPUT WARNING
        GENERATE PROMPT_UPGRADE
    STEP 6:
    SELECT ECU MODE
        IF current / financial / health / law / war / public safety:
            ECU = STRICT
        IF framework / education / civilisation synthesis:
            ECU = NEUTRAL
        IF failure trace:
            ECU = REVERSE
        IF future / scenario:
            ECU = FRONTIER
        IF mixed:
            ECU = HYBRID
    STEP 7:
    RUN REPORT BUILD
        IF BUILD = ORIENTATION_REPORT:
            write broad map + limitation + upgraded prompt
        IF BUILD = DIAGNOSTIC_REPORT:
            write scope + diagnosis + Micro/Meso/Macro + ReverseHYDRA + FullOS
        IF BUILD = EXPERTSOURCE_ANALYTICAL_REPORT:
            write source-anchored analysis + mechanism map + confidence
        IF BUILD = FULL_CIVILISATION_GRADE_REPORT:
            write full report:
                Civilisation-grade check
                Executive summary
                Source layer
                VocabularyOS
                Micro/Meso/Macro
                Mechanism map
                ReverseHYDRA
                FullOS
                Ztime
                Control Tower
                Scenarios
                Watchlist
                Repair route
                Final verdict
                Almost-Code
    RETURN REPORT

REPORT SYSTEM LOCK:
Broad questions do not get fake high confidence.
Broad questions get:
orientation-grade report
warning label
prompt upgrade
Precise questions get:
diagnostic-grade report
Precise + sourced + mechanism questions get:
analytical-grade report
Precise + sourced + mechanism + Micro/Meso/Macro + ReverseHYDRA + FullOS + repair/watchlist questions get:
civilisation-grade report
Civilisation-grade is not a writing style.
It is a runtime standard.

eduKateSG reports do not become civilisation-grade because they sound impressive.
They become civilisation-grade when they pass:
Question Gate
Source Gate
Scale Gate
Time Gate
Mechanism Gate
ReverseHYDRA Gate
FullOS Gate
Repair Gate
Boundary Gate
Public Clarity Gate