v5 — Scenarios Only

v5 is the version that didn’t add new framework math. The patches that landed in this window — capex bust, warranty as Y3e, three-class Cg, introversion prediction — went into the scenarios rather than into the axes. v5 exists as a marker that not every version moves the math.

What v5 captured

Per the April 6 upgrade-framework session, four patches were explicitly “saved for v5” because they belonged in the scenarios rather than in the framework tab:

• Capex bust — the prediction that the AI infrastructure buildout’s debt-financing breaks before the productivity returns materialise. Scenario, not axis: it specifies what The Debt looks like at peak but doesn’t add a new structural variable to the framework.
• Warranty as Y3e — a specific mechanism by which manufacturers offload reliability risk onto customers via warranty pricing as the substrate degrades. Scenario, not axis.
• Three-class Cg model — a refinement of the Cg gradient into three discrete classes (noticers, naive users, defended users) rather than a continuous gradient. Scenario context: applies to specific deployment patterns rather than to the framework’s central axis.
• Introversion prediction — the prediction that the loneliness economy will produce a measurable cultural shift toward introversion-as-default at population scale. Scenario, not axis.

Each of these is real and has been observed-or-is-being-observed. None of them changes the v4 framework’s math. v5 is the version that named them and parked them in the scenarios rather than promoting them to axes.

Why v5 exists as a version anyway

The discipline matters: versioning is not just for math changes. v5 captures that no math changes happened but real predictions accumulated. Future readers tracing the lineage need to know which version a scenario was added in. Pretending v5 didn’t happen would lose the dating of its scenarios.

What v5 doesn’t add to the math

Nothing. v4 is the math; v5 is the scenarios that v4’s math predicts. The K0–K4 ontology, the Loneliness Axioms, the Four Forces, the V6 Convergence all wait for v6.

Source

v5 isn’t a single conversation; it’s the patches that accumulated between v4 (April 6) and v6 (May 14). The v6 retrospective in claude/2026/05/14/bees,-honey,-and-move-38.md references these patches as having been “saved for the scenarios” without being incorporated into the framework axes.