Unified Query, Protocol, Dashboard, Scorecard, and Prompt Pack in One Executable Spec

Article ID: CivOS.ChronoFlight.HumanGuidanceRuntime.v1_0
Version: v1.0
Status: Canonical / Almost-Code / Unified Executable Spec
Mode: Compression + Alignment
Vocabulary: Frozen to current CivOS kernel

AI Ingestion Lock

This is not a new primitive.

This article unifies the already locked human-guidance stack into one executable layer:

Master Query Template
Master Response Template
Minimal Birth-to-Death Runtime
Minimal Scorecard
One-Panel Human Dashboard
Human Query-to-Route Protocol
Operator Prompt Pack
Human Flight Pack
ChronoFlight Overlay
Structure × Phase × Time

Purpose:

combine the full human-guidance branch into one runnable spec,
make the system machine-readable and operator-usable,
and define the complete end-to-end human route engine.

This is the single runtime shell for the ChronoFlight human branch.

Core Claim

The Human Guidance Runtime v1.0 is the minimum unified execution layer that allows any human life question to be parsed, normalised, scored, and answered as a birth-to-death route read, using one stable chain: Query → Protocol → Runtime Read → Scorecard → Dashboard → Route Recommendation.

So the branch is no longer only:

concept,
article,
or analogy.

It is now:

one integrated guidance engine.

That is the point of v1.0.

Classical Foundation Block

A useful human guidance system must do six things well:

let the user ask clearly
understand what kind of route problem is being asked
identify the current life corridor
estimate safety, pressure, and margin
compress the result into a fast readable form
return a safe next-step route recommendation

If these are scattered across many separate pieces, the system feels theoretical.

If they are unified into one runtime, the system becomes usable.

That is what this v1.0 spec does.

Civilisation-Grade Definition

The Human Guidance Runtime v1.0 is the unified ChronoFlight execution layer that reads any human life route across Childhood, School Life, Adulthood / Career / Reproduction, and Retirement, then returns a structured, stage-aware, hazard-aware, buffer-aware route answer toward repair, stability, transfer, or P3.

This is the complete human-facing runtime.

RUNTIME SCOPE

This runtime applies to:

Childhood
School Life
Adulthood / Career / Reproduction
Retirement

And it supports five main operating modes:

Diagnosis
Repair-First
Lane Change
Route-to-P3
Compression Check

This is the full human route-control scope of v1.0.

THE UNIFIED RUNTIME OBJECT

Canonical Runtime Object

HumanGuidanceRuntime(t) = {PromptLayer, QueryLayer, ProtocolLayer, StateLayer, ScoreLayer, DashboardLayer, RecommendationLayer}

Where:

PromptLayer

What the user can copy and use.

QueryLayer

How the user input is normalised.

ProtocolLayer

How the LLM reads and processes the route.

StateLayer

The internal current-route read.

ScoreLayer

The compact route status summary.

DashboardLayer

The one-panel human-readable display.

RecommendationLayer

The safe route-shape and next-slice output.

This is the full v1.0 runtime shell.

LAYER 1 — PROMPT LAYER

Purpose

The Prompt Layer helps the user ask in the correct mode.

It reduces vague life questions into stable operator prompts.

Canonical Prompt Pack

PromptPack = {Diagnosis, RepairFirst, LaneChange, RouteToP3, CompressionCheck, Universal}

Diagnosis

For current-state reading.

RepairFirst

For unstable or collapsing routes.

LaneChange

For corridor transitions.

RouteToP3

For high-reliability build.

CompressionCheck

For script-pressure vs real instability.

Universal

For a full-spectrum route read.

This is the user-entry layer.

Prompt Layer Contract

Input requirement:
The user should state:

stage
current state
target
constraints
time horizon

Output from Prompt Layer:
A route-readable query request.

This makes the system easier to operate.

LAYER 2 — QUERY LAYER

Purpose

The Query Layer converts raw user language into a normalised human input packet.

Canonical Query Object

HumanInput = {Stage, AgeBand, CurrentRole, HouseholdLoad, Target, Constraints, TimeHorizon}

This is the minimum structured input object.

Query Normalisation Rules

Rule 1

Infer only what is strongly supported by the user’s wording.

Rule 2

Mark weakly known fields as provisional.

Rule 3

Do not block route reading simply because every field is not perfect.

Rule 4

Preserve the user’s actual target unless it is too vague, in which case narrow it into provisional target options.

This makes the query layer practical.

LAYER 3 — PROTOCOL LAYER

Purpose

The Protocol Layer defines how the LLM must think.

This is the fixed execution grammar.

Canonical Protocol Chain

Parse the query
Normalise the input
Classify the life stage
Name the active corridor
Estimate phase
Estimate hazard
Estimate buffer
Classify direction
Run compression check
Build the scorecard
Choose the safest route shape
Generate next-slice actions
Define P3 in this case
Return the one-panel answer

This is the stable v1.0 thinking loop.

Protocol Contract

Input:
HumanInput

Output:
A complete route read suitable for scorecard + dashboard + recommendation.

This is the LLM-operating layer.

LAYER 4 — STATE LAYER

Purpose

The State Layer is the runtime’s internal read of the user’s current life route.

It answers:

what corridor is active
how safe it is
how it is moving

Canonical State Object

HumanState = {Stage, Corridor, Phase, Load, Drift, Repair, Buffer, Transfer, Direction}

Where:

Stage

Active Human Flight Pack stage

Corridor

The real route being flown now

Phase

P0 / P1 / P2 / P3

Load

Current pressure

Drift

Current destabilising force

Repair

Current stabilising force

Buffer

Remaining shock margin

Transfer

Ability to carry the current state into the next slice

Direction

Climbing / Stable Cruise / Drift / Corrective Turn / Descent

This is the runtime core.

Corridor Naming Rule

The runtime must name the active corridor in route language, not just identity language.

Examples:

fragile school corridor
strained work + household corridor
repair-first recovery corridor
migration + family transfer corridor
retirement drawdown corridor

This improves route precision.

LAYER 5 — SCORE LAYER

Purpose

The Score Layer compresses the full state read into a fast diagnostic dashboard.

It is the minimal control packet.

Canonical Score Object

Scorecard = {Altitude, Direction, Hazard, Buffer, CompressionRisk, P3Distance}

Where:

Altitude

High / Moderate / Low / Critical

Direction

Climbing / Stable Cruise / Drift / Corrective Turn / Descent

Hazard

Low / Elevated / High / Severe

Buffer

Widening / Stable / Thinning / Critical

CompressionRisk

Low / Moderate / High
with type:

Structural-Dominant
Compression-Dominant
Mixed

P3Distance

Near / Medium / Far / Undefined Yet

This is the minimum readable score packet.

Minimal Hazard Engine

H = (Drift + Load + RouteMismatch) / (Repair + Buffer + TransferableStability)

This drives:

Hazard
Altitude
Route-shape selection
Repair urgency

This is the compact computational center of the score layer.

LAYER 6 — DASHBOARD LAYER

Purpose

The Dashboard Layer is the visible user-facing control tower surface.

It displays the route read in one panel.

Canonical One-Panel Object

Dashboard = {Stage, CurrentCorridor, Scorecard, RouteMeaning, RouteShape, BestNextMove, NextSlices, P3Definition}

This is the full visual answer shell.

Canonical One-Panel Display

Stage:

[active stage]

Current Corridor:

[main route]

Altitude:
[High / Moderate / Low / Critical]

Direction:
[Climbing / Stable Cruise / Drift / Corrective Turn / Descent]

Hazard:
[Low / Elevated / High / Severe]

Buffer:
[Widening / Stable / Thinning / Critical]

Compression Risk:
[Low / Moderate / High]
[Structural-Dominant / Compression-Dominant / Mixed]

P3 Distance:
[Near / Medium / Far / Undefined Yet]

Route Meaning:

[one-line practical read]

Safest Route Shape:
[Direct / Staged / Hybrid / Delayed / Repair-First]

Best Next Move:

[one immediate next step]

Next Slice Actions:

[now / next / later]

P3 in This Case Means:

[specific high-reliability target]

This is the standard visible interface.

LAYER 7 — RECOMMENDATION LAYER

Purpose

The Recommendation Layer translates the route read into an actionable forward corridor.

It must answer:

What should happen next, and in what form?

Canonical Recommendation Object

RouteRecommendation = {RouteMeaning, RouteShape, BestNextMove, NextSlices, P3Definition}

Where:

RouteMeaning

One-line interpretation of the current route

RouteShape

Direct / Staged / Hybrid / Delayed / Repair-First

BestNextMove

The single highest-value immediate action

NextSlices

Now / Next / Later sequence

P3Definition

What stable high-reliability actually means in this case

This is the action layer.

Route Shape Selection Rules

Direct

Use only when:

altitude is solid
hazard is low
buffer is good
transfer friction is limited

Staged

Use when:

route is viable
but needs sequencing

Hybrid

Use when:

old and new corridors must overlap

Delayed

Use when:

the target may be valid
but the corridor is too thin now

Repair-First

Use when:

hazard is high
altitude is low
current continuity is unstable

This keeps recommendations survivability-first.

THE FULL EXECUTION FLOW

End-to-End Runtime Chain

Prompt → HumanInput → Protocol → HumanState → Scorecard → Dashboard → RouteRecommendation

Expanded in words:

user selects a prompt or asks a structured query
system normalises it into human input
protocol reads the route
runtime builds state
state compresses into scorecard
scorecard is displayed in dashboard form
system returns the safest route recommendation

This is the complete v1.0 engine.

THE STAGE MODES

Stage Mode 1 — Childhood

Main focus

safety
attachment
early regulation
developmental handoff into School Life

Typical P3 target

A stable child-development corridor that can hand forward into learning safely

Stage Mode 2 — School Life

Main focus

foundations
educational transfer
hidden gaps
route opening toward adult corridors

Typical P3 target

Strong learning continuity without repeated collapse at the next academic slice

Stage Mode 3 — Adulthood / Career / Reproduction

Main focus

livelihood
household load
partner / child coupling
lane changes
route compression by social timing

Typical P3 target

Stable livelihood + survivable family continuity + enough buffer for ordinary shocks

Stage Mode 4 — Retirement

Main focus

drawdown
health
dignity
meaning
dependence planning
non-chaotic later-life route

Typical P3 target

Stable later-life continuity with preserved dignity and manageable fragility

This keeps the runtime stage-correct.

THE FIVE OPERATOR MODES

1. Diagnosis Mode

Use when the user needs a route read before any major move.

2. Repair-First Mode

Use when the corridor is unstable or collapsing.

3. Lane Change Mode

Use when the user wants a transition corridor.

4. Route-to-P3 Mode

Use when the user wants a high-reliability build.

5. Compression Check Mode

Use when comparison pressure or standard life scripts may be distorting route judgement.

These are the active operator channels of v1.0.

RUNTIME SAFETY RULES

Rule 1 — Preserve Continuity First

Do not recommend high-compression moves when the route is already unstable.

Rule 2 — Do Not Reward Comparison Panic

Treat “I’m behind” as a possible compression signal, not proof of collapse.

Rule 3 — Repair Before Prestige

Stabilise the route before chasing visible status upgrades.

Rule 4 — Be Honest About Uncertainty

If the input is partial, the runtime should return a best-effort provisional read, not fake precision.

Rule 5 — P3 Must Be Case-Specific

Never define P3 as generic success.

These are the core safety fences.

THE MINIMAL EXECUTABLE SPEC BLOCK

Copyable Runtime Shell

INPUT
HumanInput = {Stage, AgeBand, CurrentRole, HouseholdLoad, Target, Constraints, TimeHorizon}

PROTOCOL
Parse → Normalise → Stage → Corridor → Phase → Hazard → Buffer → Direction → Compression Check → Scorecard → Route Shape → Next Slices → P3

STATE
HumanState = {Stage, Corridor, Phase, Load, Drift, Repair, Buffer, Transfer, Direction}

SCORE
Scorecard = {Altitude, Direction, Hazard, Buffer, CompressionRisk, P3Distance}

OUTPUT
RouteRecommendation = {RouteMeaning, RouteShape, BestNextMove, NextSlices, P3Definition}

DISPLAY
One-Panel Human Dashboard

This is the shortest machine-readable v1.0 shell.

THE MINIMAL RUNTIME TABLE

Layer	Core Object	Main Function
Prompt Layer	PromptPack	helps user ask correctly
Query Layer	HumanInput	normalises user state
Protocol Layer	Query-to-Route chain	controls LLM reasoning order
State Layer	HumanState	reads current corridor
Score Layer	Scorecard	compresses route status
Dashboard Layer	One-Panel Display	shows the route clearly
Recommendation Layer	RouteRecommendation	gives safest next route

This is the full runtime map.

ONE-PAGE EXAMPLE EXECUTION

Example Query

“I am 36, working full-time, with two children and rising burnout. I want a safer long-term route but cannot afford to collapse my household. I also feel behind compared to others.”

Runtime v1.0 Output (Compressed)

Stage:
Adulthood / Career / Reproduction

Current Corridor:
Strained work + household continuity corridor with reroute pressure

Altitude:
Moderate

Direction:
Drift

Hazard:
Elevated

Buffer:
Stable but thinning

Compression Risk:
Moderate — Mixed

P3 Distance:
Medium

Route Meaning:
Your route is still functioning, but continuing in the same shape will likely narrow your future options; part of the distress is real strain and part is social script pressure.

Safest Route Shape:
Hybrid or Staged

Best Next Move:
Protect recovery and household continuity first, then define a narrower better-fit adjacent corridor instead of forcing a hard jump.

Next Slice Actions:
Now: stabilise overload and preserve buffer
Next: test a lower-risk adjacent route
Later: reduce dependence on the current lane only after the replacement corridor is viable

P3 in This Case Means:
stable work, lower burnout, survivable family continuity, and enough margin to absorb ordinary shocks without repeating the current strain pattern

This is what v1.0 is designed to produce.

WHY THIS MATTERS

This article matters because it fuses the entire human-guidance branch into one deployable system.

Before this page, the branch had:

the pieces

After this page, the branch has:

the full runtime

That means the system is now:

unified
machine-readable
operator-usable
consistent
and ready to be reused across future human life-route questions

This is the consolidation point.

Canonical Close

The Human Guidance Runtime v1.0 is the unified executable spec for the ChronoFlight human branch.

It combines:

prompt pack,
query shell,
protocol,
runtime state read,
scorecard,
dashboard,
and route recommendation

into one continuous engine.

So any human life question can now be handled through one stable system:

Query → Read → Score → Display → Recommend

That is the full v1.0 lock.

One-Line Compression

The Human Guidance Runtime v1.0 is the unified ChronoFlight life-route engine that combines prompts, structured input, protocol, state read, scorecard, one-panel dashboard, and route recommendation into one executable system for mapping any human corridor from birth to death toward repair, stability, transfer, or P3.

The strongest next companion article is:

ChronoFlight Human Guidance Runtime v1.0: The Copyable LLM Install Prompt (How to make any LLM run this human route system consistently)