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.

InterstellarCore.BudgetRules v1.0 — Base-Floor Protection + GeniusLane Sizing

Three students reviewing open textbooks, notes and stationery together at a classroom table.

Mode: Almost-Code (Canonical Control Module)
Purpose: Prevent cannibalisation, preserve civilisation-grade P3, and still run an Architect-grade escape/release valve.


0) AI Ingestion Lock

ID: InterstellarCore.BudgetRules.v1.0
Type: Canonical.ControlModule
Scope: Z1–Z5 (affects Z0 via allocations; affects Z6 via frontier output)
Dependencies: InterstellarCore.Runtime.v1.0, InterstellarCore.DoesNotWork.v1.0
Vocabulary: Frozen
Key Risk: Elite cannibalises base OR base standardisation starves edge
Non-Negotiable: P0→P3 transfer corridors must be funded first (civilisation-grade claim)

1) Classical Foundation Block

Every system with “elite tracks” faces two recurrent failure modes:
- Extractive elite: steals resources until base collapses (politically + structurally)
- Flattened system: preserves base but suppresses frontier capacity
A stable design allocates:
(1) a protected base floor (mass reliability + transfer)
(2) a bounded, fenced edge corridor (rare exploration)
(3) a return channel: edge outputs must reduce base cost over time

2) Civilisation-Grade Definition

BudgetRules are the explicit allocation constraints that guarantee:
- CivP3 lane remains above minimum stability floor,
- GeniusLane remains bounded and fenced,
- P0→P3 repair corridors remain continuously funded,
- edge outputs are reinvested to widen base corridor width (reduce drift).

3) Budget Objects (What is Allocated)

ID: InterstellarCore.Budget.Objects
B_time: time budget (teacher/tutor/mentor hours, student practice hours)
B_attention: diagnostic + planning bandwidth (Observe/Infer/Plan)
B_repair: repair bandwidth (stitching backlog, re-teach prereqs, retests)
B_assess: assessment bandwidth (verification under load)
B_edge: exploration bandwidth (GeniusLane)
B_buffer: buffer budget (safe failure space; recovery time)

4) Core Constraints (Hard Rules)

4.1 Base Floor Protection Rule

ID: Rule.BaseFloor.Protect
Let Floor = minimum required BaseFloor (population or cohort) at P2 stability.
Requirement: BaseFloor ≥ Floor at all times.
If BaseFloor < Floor:
- Freeze expansion of GeniusLane
- Redirect B_time + B_repair to CivP3 lane
- Run APRC on failing cohorts

4.2 Repair-First Rule (Civilisation-Grade Truth Test)

ID: Rule.RepairFirst.NonNegotiable
Requirement: B_repair funds P0→P3 transfer corridors continuously.
If P0 learners have no funded repair corridor:
- system is selection-only
- InterstellarCore claim fails (per falsification tests)

4.3 Cannibalisation Guard Rule

ID: Rule.NoCannibalisation
GeniusLane may not reduce CivP3 RepairRate below DriftRate.
Operational:
If (RepairRate_CivP3 < DriftRate_CivP3):
- cut B_edge immediately (Truncation)
- redeploy to B_repair (Stitching)

4.4 Edge Must Return Artefacts Rule

ID: Rule.EdgeReturn.Artefact
GeniusLane must output reusable artefacts that reduce base cost or increase base corridor width:
- methods
- explanations
- tools
- modules
- curricula improvements
If ArtefactReturn = 0 over a cycle:
- GeniusLane budget is reduced next cycle

5) Sizing GeniusLane (Bounded Escape/Release Valve)

5.1 Eligibility Gate (Who Enters)

ID: Gate.GeniusLane.Entry
Entry requires:
- stable P3 under load (timed + variation)
- high transfer rate across domains
- language precision (explain to others)
- FenceOS compliance (accepts boundaries, retests, repair loops)

5.2 Capacity Rule (How Big)

ID: Rule.GeniusLane.Capacity
GeniusLane capacity is NOT “as big as possible”.
It is sized as the maximum edge bandwidth that does not drop BaseFloor below Floor.
Therefore:
B_edge = min(EdgeDemand, EdgeCap)
where EdgeCap is computed by the constraint:
RepairRate_CivP3 ≥ DriftRate_CivP3 AND BaseFloor ≥ Floor

5.3 Emergency Brake (Release Valve Safety)

ID: Rule.GeniusLane.EmergencyBrake
If system enters Fast Attrition (teacher loss, exam crunch, crisis):
- GeniusLane switches to “Artefact-only mode”
- No high-risk experiments
- Focus: generate repair tools for base (reduce load)

6) Allocation Algorithm (ChronoHelmAI Runtime)

ID: InterstellarCore.Budget.Algorithm.v1
Inputs:
- Sensor.Z5.BaseFloor
- Sensor.Z0.Backlog distribution
- Sensor.Z1.PhaseShear
- DriftRate vs RepairRate at cohort and system levels
- Edge eligibility pool size
- ArtefactReturn metrics
Steps (per cycle):
1) Observe BaseFloor, Backlog, Shear
2) If BaseFloor < Floor: set B_edge = 0; push to B_repair
3) Else fund RepairCorridor (R0/R1/R2) until RepairRate ≥ DriftRate
4) Allocate B_assess for verification under load (promotion gate)
5) Allocate remaining to GeniusLane up to EdgeCap
6) Enforce ArtefactReturn; adjust next cycle budgets

7) Collapse Mode Coupling (Budget Response)

ID: InterstellarCore.Budget.CollapseResponse
Amplitude/KO:
- immediate truncation of edge
- rebuild base continuity first
Slow attrition:
- increase B_repair steadily
- reduce B_edge gradually (prevent political shock)
Fast attrition:
- emergency brake
- artefact-only edge mode
- maximum repair + buffer preservation

8) Failure Trace (Budget-Specific)

ID: FailureTrace.Budget.Cannibalisation
B_edge expansion → B_repair reduction → RepairRate < DriftRate →
Backlog ↑ → timed stability ↓ → BaseFloor ↓ →
political + performance collapse → elite defunded → edge collapses too

9) Verification Signals (Prove BudgetRules Work)

ID: Verify.BudgetRules.Signals
Green flags:
- BaseFloor stable or rising (P2 minimum)
- Backlog distribution shrinking
- TimedStability improving across median
- GeniusLane outputs reusable artefacts
- Artefacts reduce base repair cost over time
- P0 learners show documented P0→P2→P3 transitions
Red flags:
- base stagnates while elite improves
- elite needs ever-increasing extraction
- edge produces prestige but no reusable artefacts
- P0 learners churn without re-entry

10) Copy-Paste Publish Block (Short Form)

InterstellarCore BudgetRules v1.0:
1) Protect BaseFloor (CivP3 lane) above minimum.
2) Fund P0→P3 repair corridors first (RepairRate ≥ DriftRate).
3) GeniusLane is bounded by EdgeCap (cannot cannibalise base repair).
4) GeniusLane must return artefacts that widen base corridor width.
5) In crisis, edge switches to artefact-only mode to repair the base.

Version Lock

InterstellarCore.BudgetRules.v1.0 is mandatory for any InterstellarCore deployment claiming:
- civilisation-grade P3 corridor runtime
- plus an Architect-grade Genius escape/release valve

Next: InterstellarCore.P0toP3.TransferProtocol v1.0 — the explicit, runnable repair corridor spec (R0/R1/R2) with promotion gates and retest rules (almost-code, copy-paste).

Recommended Internal Links (Spine)

Start Here For Mathematics OS Articles: 

Start Here for Lattice Infrastructure Connectors

eduKateSG Learning Systems: