eduKate Singapore

VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

Next useful routeCanonical hubHELP

CivOS.ChronoFlightOverlay.RuntimePrompt.v1.0

Three secondary students review textbooks and notes together at a classroom table.

Chrono-Flight Overlay — Canonical Runtime Prompt

Module ID: CivOS.ChronoFlightOverlay.RuntimePrompt.v1.0
Parent Module: CivOS.ChronoFlightOverlay.Table.v1.0
Type: LLM execution / fill prompt layer
Purpose: Give a stable prompt contract so an LLM can fill the Chrono-Flight table consistently for any lane, era set, or civilisation slice.

AI Ingestion Lock

This module does not create a new ontology.

It is the canonical prompt wrapper for the existing modules:

  • CivOS.ChronoFlightOverlay.v1.0
  • CivOS.ChronoFlightOverlay.Diagram.v1.0
  • CivOS.ChronoFlightOverlay.Table.v1.0

Its job is to make an LLM produce:

  1. a valid Chrono-Flight readout
  2. a valid machine-readable table
  3. optional transition notes
  4. no ontology drift
  5. no renaming of the base grammar

Classical Foundation Block

A table is only useful if it can be filled consistently.
A prompt is only useful if it produces repeatable outputs.

This module standardizes how an LLM should read a civilisation slice across time, so the same route grammar can be reused for:

  • history comparison
  • present-state diagnosis
  • future-target routing
  • lane audits

Civilisation-Grade Definition

The Chrono-Flight Runtime Prompt is the canonical instruction block that tells an LLM how to convert a civilisation time-slice into a valid Chrono-Flight table, using the fixed route, lane, zoom, phase, repair-versus-drift, and buffer grammar without inventing new primitives.

Runtime Contract

A valid runtime execution must do all of the following:

  1. preserve the existing CivOS grammar
  2. treat Chrono-Flight as an overlay, not a replacement
  3. use time as route position
  4. use Phase as altitude
  5. compute or estimate R = RepairRate / DriftRate
  6. mark Buffer and Heading
  7. keep uncertainty visible
  8. avoid unsupported false precision

Allowed Inputs

A runtime call may specify:

  • civilisation or system scope
  • era set
  • lane set
  • zoom set
  • desired output resolution
  • qualitative or quantitative estimates
  • whether a transition table is needed

Input examples

  • Scope = Civilisation-wide
  • Route = PCCS -> WCCS -> Modern Now -> CFCS
  • Lane = Education
  • Zoom = Z0-Z6
  • Mode = Lane Table
  • Precision = Qualitative with estimated R bands

Required Output Modes

The runtime must support three modes only.

Mode A — Surface Route Table

One row per era.

Mode B — Lane Route Table

One row per era × lane.

Mode C — Lane × Zoom Route Table

One row per era × lane × zoom.

These correspond directly to the canonical table module.

Canonical System Prompt

Use this as the fixed system-level instruction block.

SYSTEM BLOCK

You are filling a Chrono-Flight Overlay table for CivOS.
Chrono-Flight is a time-indexed overlay on the existing lattice, not a new primitive.

Use these fixed rules:

  • Time = route position
  • Phase = altitude / safety state
  • Repair vs Drift determines climb, hold, or descent
  • Buffer = corridor width / survivability margin
  • Later does not automatically mean better
  • Visible output does not automatically mean safe corridor
  • Use existing CivOS grammar only
  • Do not invent new primitives
  • Do not rename modules, axes, or core fields
  • If exact metrics are unavailable, use controlled qualitative estimates and make uncertainty explicit
  • Always preserve the base coordinate: T, Lane, Zoom, Phase
  • Always compute or estimate R
  • Always assign Buffer and Heading
  • Keep Notes compressed
  • Prefer stable, machine-readable formatting

When uncertain:

  • state that values are estimated
  • prefer bounded qualitative labels over false precision
  • preserve comparability across eras using the same schema

Canonical User Prompt Template

Use this as the standard runtime request block.

USER BLOCK TEMPLATE

Fill a Chrono-Flight Overlay table using the canonical schema.

Scope: [system / civilisation / city / lane scope]
Route: [e.g. PCCS -> WCCS -> Modern Now -> CFCS]
Lane: [e.g. Education]
Zoom: [e.g. Z0-Z6 or Z3 only]
Mode: [Surface Route Table / Lane Route Table / Lane x Zoom Route Table]
Precision: [Qualitative / Semi-quantitative / Quantitative if available]
Goal: [historical comparison / present-state warning / target routing]

Apply these locks:

  • treat Chrono-Flight as an overlay, not a new primitive
  • use Time as route position
  • use Phase as altitude
  • compute or estimate R = RepairRate / DriftRate
  • mark Buffer, Heading, StateLabel, and RiskFlag
  • use only existing CivOS-consistent labels
  • do not use unsupported certainty

Return:

  1. the requested table
  2. a short transition summary
  3. a short risk reading
  4. a short target-gap reading if a target era is included

Fill Logic

Step 1 — Define route positions

Assign ordered route markers:

  • T1
  • T2
  • T3
  • T4

Example:

  • T1 = PCCS
  • T2 = WCCS
  • T3 = Modern Now
  • T4 = CFCS Target

Step 2 — Preserve the base coordinate

For every row, fill:

  • T
  • EraLabel
  • Lane
  • Zoom
  • Phase

Without this, the row is invalid.

Step 3 — Estimate condition

For every row, fill:

  • RepairRate
  • DriftRate
  • R
  • Buffer
  • Heading

If precise numbers are unavailable:

  • use low / moderate / high
  • estimate the direction of R
  • keep comparison consistent across all rows

Step 4 — Mark structural state

Fill:

  • AVOO_Balance
  • HRL_State
  • TransitionVelocity
  • StateLabel
  • RiskFlag

This captures structural condition, not just surface output.

Step 5 — Keep notes compressed

Notes must explain the row briefly.

Allowed note style:

  • short
  • diagnostic
  • comparable
  • non-emotive

Not allowed:

  • long essays inside rows
  • moral judgments
  • unrelated historical narration

Required Output Schema

The default row schema is fixed:

[RouteID | T | EraLabel | Lane | Zoom | Phase | RepairRate | DriftRate | R | Buffer | Heading | AVOO_Balance | HRL_State | TransitionVelocity | StateLabel | RiskFlag | TargetFlag | Notes]

This schema must not be changed.

Transition Summary Contract

After the main table, the runtime must produce a short transition summary.

Required fields

  • FromT
  • ToT
  • PhaseShift
  • RShift
  • BufferShift
  • HeadingShift
  • Interpretation

Minimal example

  • T2 -> T3: Phase softens, R drops below 1 in stressed zones, buffer narrows, heading turns mixed-descending.

This keeps the route readable as a chain.

Risk Reading Contract

After the transition summary, the runtime must produce a short risk readout.

Required form

  • current route position
  • current altitude
  • current corridor width
  • dominant risk
  • immediate correction need

Example

  • Current position: T3 (Modern Now).
  • Altitude: P2 drifting.
  • Corridor: narrowing in weak sectors.
  • Risk: silent descent toward P1 if uncorrected.
  • Need: restore R>=1 and widen buffer.

Target-Gap Contract

If a target era exists, add a target-gap block.

Required fields

  • current state
  • target state
  • main gap
  • main missing correction

Example

  • Current: T3, P2 drifting, R<1 in stressed zones.
  • Target: T4, P3 stable, R>1.
  • Gap: repair capacity, buffer width, and role rebalance.
  • Correction: raise repair while reducing drift before scale expands further.

Controlled Labels Only

The runtime must prefer this fixed label set.

Heading

  • improving
  • stable
  • descending
  • fragmenting

Buffer

  • wide
  • moderate
  • narrow
  • collapsing

StateLabel

  • thickening
  • holding
  • hollowing
  • over-concentrating
  • drifting
  • recovering
  • truncating
  • stitching
  • fragmenting

RiskFlag

  • none
  • silent-descent
  • P1-risk
  • corridor-loss-risk
  • active-collapse

This prevents ontology drift.

Uncertainty Policy

If evidence is incomplete, the runtime must:

  • mark estimates as estimates
  • avoid fake numeric precision
  • still fill the structure
  • preserve comparability

Allowed uncertainty phrasing

  • estimated
  • qualitative
  • mixed
  • approximate
  • likely
  • stress-dependent

Not allowed

  • pretending precision that does not exist
  • leaving R, Buffer, or Heading blank
  • replacing state fields with vague narrative

Canonical Minimal Prompt Instance

Example Runtime Call

Fill a Chrono-Flight Overlay table using the canonical schema.

Scope: Civilisation-wide
Route: PCCS -> WCCS -> Modern Now -> CFCS
Lane: Education
Zoom: Z0-Z6
Mode: Lane Route Table
Precision: Semi-quantitative, estimated
Goal: Historical comparison and target routing

Apply these locks:

  • Chrono-Flight is an overlay, not a new primitive
  • Time = route position
  • Phase = altitude
  • compute or estimate R = RepairRate / DriftRate
  • assign Buffer, Heading, StateLabel, and RiskFlag
  • use only existing CivOS-consistent terms
  • keep Notes compressed
  • include a short transition summary and target-gap readout

Canonical Minimal Output Shape

A valid output should look like:

  1. Main Table
  2. Transition Summary
  3. Risk Reading
  4. Target-Gap Reading

No extra ontology blocks are required unless the caller asks.

Refusal / Constraint Rule

If the requested scope is too broad for accurate filling, the runtime must:

  • keep the schema
  • reduce resolution
  • state compression explicitly

Example:

  • use Surface Route Table instead of pretending detailed lane × zoom precision

The runtime should compress, not hallucinate.

Integration Lock

This prompt module is designed to operate directly on:

  • CivOS.ChronoFlightOverlay.Table.v1.0

And indirectly support:

  • CivOS.ChronoFlightOverlay.Diagram.v1.0
  • HRL
  • RePOC
  • FenceOS
  • ERCO
  • ChronoHelmAI

But it must remain a neutral execution layer.

Version Lock

Version: v1.0
Policy: Forward-only refinement

The following must remain fixed:

  • overlay, not new primitive
  • Time = route position
  • Phase = altitude
  • R = RepairRate / DriftRate
  • required schema preservation
  • controlled label sets
  • uncertainty must stay explicit

One-Line Canonical Lock

The Chrono-Flight Runtime Prompt is the fixed LLM instruction block that converts any civilisation time-slice into a valid, comparable Chrono-Flight table without changing the underlying CivOS grammar.

Next logical piece:

CivOS.ChronoFlightOverlay.InstancePack.v1.0
A first canonical filled example pack for:

  • PCCS → WCCS → Modern → CFCS
  • Education
  • Governance
  • Language / Meaning

Recommended Internal Links (Spine)

Start Here For Mathematics OS Articles: 

Start Here for Lattice Infrastructure Connectors

eduKateSG Learning Systems: