v4 — The Ci Axis

v4 adds Ci (Cognitive Infrastructure) as the buffer against Ep. The Ep × Ci interaction means a poisoned information environment is only structurally catastrophic if the cognitive infrastructure that buffers against it has also collapsed. v4 also refines Ae (bloom/distillation) and Sq (attack/defence asymmetry).

Ci — Cognitive Infrastructure

Ci names the substrate of clean, navigable, durable knowledge that humans rely on to interpret the information environment (Ep). The library, the archive, the encyclopedia, the indexed research corpus, the curated reading list, the experienced editor, the mentor who can tell you which paper is the right paper. Ci is the apparatus that lets a human turn a polluted Ep into a usable signal.

v3 had Ep but no Ci. The implicit assumption in v3 was that the information environment poisoning was the catastrophe by itself. v4 corrects this: Ep poisoning is only structurally catastrophic if Ci has also collapsed. If Ci is intact, a thoughtful human can still navigate a polluted Ep — they have the reference points to triangulate from.

The framework’s diagnostic claim sharpens: the library was civilisation’s Ci factory and it’s closed. The structural failure isn’t that the information environment got poisoned; it’s that the apparatus to navigate it was simultaneously dismantled. Library budgets cut. Newspaper investigative desks gutted. Encyclopedia maintenance disinvested. The curation labour that produced Ci was the first thing the productivity calculus eliminated.

Ep × Ci interaction

The new structural variable: Ep × Ci. The poisoning of Ep is multiplied by the collapse of Ci. A small Ep degradation against a strong Ci is recoverable. A small Ep degradation against a weakened Ci compounds into catastrophic interpretation failure.

This is the v4 reason why the flywheel has accelerated faster than v3 predicted. v3 was modelling Ep alone; v4 sees that the apparatus for buffering Ep — Ci — was dismantled in parallel by the same Rc forces. The cannibalisation that fed Ae also cannibalised the people, institutions, and budgets that produced Ci.

Bloom and distillation — refinement to Ae

v3 had Ae as a single axis: compute efficiency inverts due to demand growth. v4 splits this into two opposing forces:

• Bloom — the rapid expansion of compute capacity (frontier model training, RL post-training, agentic environments) drives the cost-per-query down on the unit basis but pushes total spend up.
• Distillation — the compression of frontier capability into smaller, cheaper models that run at the edge. Distillation is the good side of Ae; it transfers capability outward and reduces concentration.

The Ae axis now lives in the tension between bloom (concentrating) and distillation (distributing). The framework’s prediction depends on which side wins on what timescale. Bloom is winning in 2026; distillation is two release cycles behind but compounding fast.

Attack/defence asymmetry — added to Sq

v3 had Sq (software quality degrades) as a downstream consequence of pressure. v4 adds the attack/defence asymmetry explicitly: in software, attacks compound geometrically while defences scale linearly. A small Sq regression doesn’t produce a small security failure; it produces a security failure proportional to the attacker capability now amplified by AI tooling.

The asymmetry means: as long as attackers can use AI tools at parity with defenders (or close to it), and as long as Sq is degrading at all, the security posture of the substrate is getting worse faster than the framework’s earlier versions predicted. v4 names this; v6 absorbs it into the Four Forces.

What v4 keeps and what it doesn’t add

v4 keeps everything from v3 (the five-axis flywheel, McLuhan as Physical Law #9, Section 174A as the 14x Problem, the Debt as proof). It adds Ci, the Ep × Ci interaction, bloom/distillation, and attack/defence in Sq.

v4 doesn’t add:

• The K0–K4 ontology. v6.
• The Loneliness Axioms. v6.
• The Four Forces. v6.
• The V6 Convergence scenario. v6.

Source

The v4 articulation is across claude/2026/04/06/bees-for-honey,-upgrade-framework.-{1..15}.md. This is the session where v4 is built; the conversation explicitly threads “this is the v4 with Ci integrated” / “save those for v5” markers throughout.