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.

CivOS Runtime — Release & Governance SOP (v1.0)

eduKate Secondary students reviewing open books for How Super Intelligence Works: Attention.

“`text id=”r3p8m1″
TITLE: CivOS Runtime — Release & Governance SOP (v1.0)
SLUG: /civos-runtime-release-governance-sop-v1-0/
PAGE.ID: CIVOS.RUNTIME.SOP.RELEASE_GOV
VERSION: v1.0
STATUS: CANONICAL_OPS_PAGE
PARENT.RUNTIME: /civos-runtime/
PURPOSE: How to ship new pages/modules forever without drift.

text id=”k3n8ds”

CIVOS RUNTIME — RELEASE & GOVERNANCE SOP (v1.0)

0) CORE PRINCIPLE (LOCKED)
CivOS Runtime evolves by version-forward pages, not edits.
We preserve history, lock IDs, and gate “Deploy” with retest proof.


1) ROLES (AVOO) — WHO DOES WHAT

Architect:

  • generates new module corridors (in Sandbox)
  • proposes new ModuleID + draft spec page

Visionary:

  • decides whether the corridor matters (promotion from draft → publish)
  • approves what becomes “Recommended Latest”

Oracle:

  • checks correctness, thresholds, and anti-drift compliance
  • runs Drift Tests + ensures version-map/registry updates

Operator:

  • publishes pages, updates runtime index links, ensures no overwrites
  • enforces “Do not rename / do not overwrite” discipline

2) RELEASE TYPES (CHOOSE ONE)

R1 New Module (new capability):

  • new ModuleID
  • new page
  • add to registry + version map
  • optionally add to /civos-runtime/ recommended list

R2 New Version of Existing Module:

  • publish new version page (v1.2 → v1.3)
  • do NOT edit old version page
  • update Version Map row + Registry mapping
  • optionally promote to “Recommended Latest”

R3 Hotfix / Patch Note:

  • publish patch page (does not replace core)
  • patch pages may recommend install order changes
  • later consolidate into next version

3) NON-NEGOTIABLE LOCKS (ANTI-DRIFT)

Never rename:

  • ModuleID, SensorID, PlaceID, CityID, InstitutionID, RoleID, IndividualID

Never overwrite:

  • old versions
  • archive snapshots

Core law and core primitives are frozen.
All expansion ships as plug-ins.


4) THE 7-STEP PUBLISH PIPELINE (EVERY TIME)

Step 1 — Draft (Sandbox)

  • write new page using plug-in template
  • include: META, Extends, DoesNotChange, Sensors, Actions, Retests, Failure trace

Step 2 — Drift Tests (Oracle)

  • run: /civos-core-drift-tests-v1-0/
  • must pass especially:
  • no ID rename
  • no “Deploy without retest gate”
  • truncation + stitching present

Step 3 — Publish (Operator)

  • publish as NEW URL (versioned)
  • do not edit old pages

Step 4 — Update Version Map (Operator)

  • append row:
    /civos-runtime-version-map-v1-2/

Step 5 — Update Registry (Operator)

  • append mapping:
    /civos-registry-moduleids-and-sensors-v1-2/

Step 6 — Optional Promote (Visionary)

  • if promoted: update /civos-runtime/ “Recommended Latest”
  • do not change anything else in /civos-runtime/

Step 7 — Link Closure (Operator)

  • ensure page footer includes:
    Parent Control Tower + Version Map + Registry + Drift Tests

5) DEPLOY GATING (REQUIRED)

Deploy is “opening up expansion”:

  • new topics, new scope, new lanes, new complexity, new coupling.

Deploy is allowed ONLY when:

  • retests passed (PromotionGate)
  • 2 consecutive passes if stability-sensitive
  • TTC rising (not shrinking)
  • ρ not flooding Operator corridor

Otherwise:

  • remain in Freeze/Sandbox mode (FenceOS discipline)

6) DEPRECATION POLICY (CLEAN, NO DELETION)

When a version is superseded:

  • mark it “DEPRECATED” at the top (one line)
  • keep it accessible forever
  • Version Map shows:
  • active recommended version
  • older deprecated versions

Do NOT:

  • delete pages
  • merge content by overwriting older pages

7) EMERGENCY RULE (WHEN YOU’RE TIRED / RUSHED)

If you’re rushed:

  • publish the new page anyway (versioned)
  • but DO NOT promote it to “Recommended Latest”
  • only promote after Drift Tests pass and registry updates are done

8) RUNTIME FOOTER (MANDATORY)

Parent Control Tower: /civos-runtime/
Version Map: /civos-runtime-version-map-v1-2/
Registry: /civos-registry-moduleids-and-sensors-v1-2/
Drift Tests: /civos-core-drift-tests-v1-0/

============================================================

END SOP

### Patch lines to “install” this SOP into your registries
Paste into **`/civos-runtime-version-map-v1-2/`**:

text

  • CivOS Runtime Release & Governance SOP v1.0:
    /civos-runtime-release-governance-sop-v1-0/
Paste into **`/civos-registry-moduleids-and-sensors-v1-2/`**:

text
CIVOS.RUNTIME.SOP.RELEASE_GOV → /civos-runtime-release-governance-sop-v1-0/
“`

Recommended Internal Links (Spine)

Start Here For Mathematics OS Articles: 

Start Here for Lattice Infrastructure Connectors

eduKateSG Learning Systems: