StayVS — Stabilizing Versioning System#

StayVS (Stabilizing Versioning System) tracks the maturity of any information artefact — from a back-of-envelope intuition through formal proof to global community acceptance. It was developed by LLoL for Evolvix since 2014 and is applied here to every axiom, theorem, model, and claim in the matheology system.

StayVS has four pillars:

  1. StayC (Stability Codes) — a maturity lifecycle from MM (Mockup Model) through SS (Stable Source). See StayC — Stability Codes for Maturity Tracking.

  2. OKScale (BioBinary Verdicts) — a four-state verdict system for individual tests: OK (held), KO (breached), OKO (undetermined), MIS (misclassified). Replaces the ambiguous N/A. See OKScale — BioBinary Verdicts for Adversarial Testing.

  3. VVN (Versioned Variant Numbers) — attribution strings that encode StayC level + assessor + version + date, ensuring every assessment is traceable to a person. Example: iv_LLoL_QQv2r0p0_2026m03d22.

  4. POST pipeline integration — the POST codes jj (JammedJob) and kk (KnownKiller) handle claims that encounter blockers or terminal failures, providing structured paths for rescue or documented retirement. See POST — Project Organization Stabilizing Toolkit System.

How StayVS Connects to POST#

The StayC lifecycle (MM through SS) tracks the forward journey of a claim toward maturity. But claims also encounter blockers — problems that stall progress or kill it outright. The POST system provides two codes for these situations:

JJ (JammedJob): A claim at any StayC level can become jammed — a known problem exists but hope remains that it can be fixed. The problem is documented, and the claim waits for a resolution. A JJ entry can lead to:

  • Revival: the fix is found, and the claim re-enters the StayC pipeline at whatever level it fell from (typically NN, then back toward OO or PP).

  • Escalation to KK: the problem is shown to be unfixable.

KK (KnownKiller): The definitive graveyard. A KK entry documents a failure that is well-understood, has no known workaround, and is considered terminal. Unlike NN (which carries hope of rescue), KK is a final verdict with a clear explanation of why this fails and why there is no fix.

The relationship:

StayC claim at any level
     │
     ├── (problem found) ──→ JJ (JammedJob: documented, hope of fix)
     │                           │
     │                           ├── fix found ──→ NN ──→ re-enter StayC
     │                           │
     │                           └── proven unfixable ──→ KK (KnownKiller: retired)
     │
     └── (continues normally through StayC lifecycle)

VVN Structure#

A Versioned Variant Number encodes four components:

Regime_Assessor_StayCVersionReleasePatch_Date

  • Regime: iv (IjtihadVersioning, long-term commitment) or dv (DeveloperVersioning, current practices), among others.

  • Assessor: nickname of the person making the assessment (e.g., LLoL, ClaOp46Max).

  • StayC + VRP: maturity code + version-release-patch (e.g., QQv2r0p0).

  • Date: YYYYmMMdDD format (e.g., 2026m03d22).

Critical rule: VVNs are personal assessments. A VVN must NEVER be attributed to someone other than the person who made the assessment. Different assessors can legitimately assign different StayC codes to the same claim.

References#