4QX already had a clean core story. V₃ gives the four-quadrant dual-triangle holon: TL/TR/BL/BR, two Teloi, one public seam, no BL↔BR shortcut, and a six-phase Generic Organisation cycle. The open question was whether the later seven department-capabilities were merely a useful organisational catalogue, or whether they could be derived from the kernel in a serious way.
The answer is now much stronger than the original question. V₄ does not merely justify a seven-item department list. V₄ objectifies V₃. It turns the V₃ dual-triangle board into seven existentially closed objects: four quadrant objects and three TelosLeg objects. Those seven objects have unique maintenance powers, assemble into structural holon-object interfaces, form a closed seven-object society, and—given runtime-supplied evidence—realise full Generic Organisation closure across a convergent chain of canonical cycles.
This is the important point: V₄ is not “more quadrants.” It is the first object-space of the 4QX holon itself.
Full operator cycle on the dual field: Fit → Offer → Accept → Run → Publish → Integrate. (HOL-VIS-002)
## From V₃ grammar to V₄ object-space
At V₃, 4QX has its static grammar: the first stable 2×2 square, read as public/private × structure/continuity. In ordinary 4QX language this is:
“` TL = Pattern / public Form TR = Event / public Flux BL = Resource / private Form BR = Metric / private Flux “`
The V₃ board is the holon-form. It gives the four sites, the seam, the two triangular loops, and the six lawful phases.
V₄ asks a different question. Instead of asking “what are the four corners?”, it asks: what are the live ways to take a meaningful cut through the whole V₃ board?
A V₄ mode is not just a subset `S`. It is the complement-pair:
“` S ↔ Q ∖ S “`
where `Q` is the whole V₃ board. That means the object is always a two-sided aperture: object and co-object, face and support, exposed side and hidden side. The report calls this existential closure: an object exists by being a distinction whose complement remains present as support/context. The proof-carrying `V4ExistentialObject` makes this formal: every object must prove object ∪ support = whole board, object ∩ support = empty, and complete traces over both Class and Instance teloi.
Once the degenerate void/whole pair is removed, V₄ produces seven live modes:
“` 4 quadrant closures: TL-object TR-object BL-object BR-object
3 TelosLeg closures: Seam-object Walk-object Merge-object “`
This is the first key result: seven comes from V₄ closure structure, not from a hand-written department table. The seven objects enumerate the seven closure kinds: four corners plus three legs.
## The seven are objects first, capabilities second
The earlier vocabulary was “seven department-capabilities”: Assess, Observe, Plan, Report, Coordinate, Delegate, Revise. That language remains useful, but it is now downstream of a cleaner structure.
The derived objects and their unique maintenance powers are:
| V₄ object | Closure kind | Maintenance power |
|---|---|---|
| TL / public-Form object | `corner .TL` | `assessPattern` |
| TR / public-Flux object | `corner .TR` | `observeEvent` |
| BL / private-Form object | `corner .BL` | `planResource` |
| BR / private-Flux object | `corner .BR` | `reportMetric` |
| Seam object | `leg .Seam` | `coordinateSeam` |
| Walk object | `leg .Walk` | `delegateWalk` |
| Merge object | `leg .Merge` | `reviseMerge` |
The central maintenance theorem says that for every existential object, exactly one capability role maintains it. Crucially, the relation is grounded in closure kind—geometry—not in “equals the assigned role.” That avoids the Potemkin version of the proof where one merely names seven things and proves there are seven names.
This reframes departments. A department is not primarily an org-chart box. It is the stable place where one existential closure is maintained. A capability is the active power by which that closure is maintained.
So the seven are noun/verb duals:
“` object-place = department face maintenance = capability face “`
## V₄ as “V₃ objectified”
The conceptual breakthrough is that each V₄ object is a way the whole V₃ holon becomes Nameable.
A TL-object is not merely the TL quadrant. It is TL distinguished from its co-face, while still carrying a complete trace over both Teloi. A Seam-object is not merely the TL→TR edge. It is the seam as an existential closure over the whole V₃ board. The same holds for Walk and Merge.
This is why V₄ matters. V₃ gives the grammar of one holon. V₄ gives the object-space in which that grammar can be enacted by a society of holon-like objects.
The resulting shape is:
“` V₃: one holon grammar four quadrants two Teloi three TelosLegs six phases
V₄: seven objects of that grammar four quadrant-objects three leg-objects
V₄ enacted: the seven objects form a society whose interactions realise the 4QX cycle “`
Society enacts the same dual-loop grammar it is built from — Fit through Integrate on the holon board. (HOL-VIS-002)
That is the precise version of the intuition: “a group of 4QX holons together enacting 4QX.”
## What the final theorem proves
The H3 theorem is now Green, with a crucial condition: it depends on runtime-supplied evidence. The one-page proof note states the claim this way: given runtime evidence for a welded chain of strict-progress coherent GO cycles, the seven V₄ holon-objects realise canonical Generic Organisation cycles whose seam-visible runtime steps are phase-coherent, owner-leg-correct, seam-log-replayable, RuntimeExecution-conformant, Integrate→next-Fit recursive, H-monotone, strictly decreasing off-equilibrium, fixed at H=0, convergent to H=0 within `H₀` cycles, and persistent at equilibrium.
The final theorem lives at:
“` 4QXProd/Conformance/V4GenericOrganisationClosure.lean
theorem v4_generic_organisation_closure (c : V4GenericOrganisationClosure) : V4GenericOrganisationClosureHolds c “`
The theorem bundles twelve fields over the converging chain:
“` 1. seven-object society 2. canonical Fit→Offer→Accept→Run→Publish→Integrate order 3. actor↔phase coherence 4. owner-leg correctness 5. seam-log replay 6. per-cycle RuntimeExecution conformance 7. Integrate→next-Fit recurrence 8. H monotonicity 9. strict decrease off-equilibrium 10. fixed point at H = 0 11. convergence to H = 0 within H₀ cycles 12. equilibrium persistence “`
Those are not prose promises. They are the fields of `V4GenericOrganisationClosureHolds`.
## Why the runtime-evidence condition matters
The theorem is not unconditional liveness. It does not say the runtime can always produce the required welded strict-progress chain. It says: given such runtime evidence, V₄ composes it into Generic Organisation closure.
That condition is not a defect. It is the anti-Potemkin boundary that makes the theorem credible. The report states that every H value and every `RuntimeExecutionFrame` is supplied by the runtime; V₄ composes and manufactures no frame, digest, or H atom.
This division of labour is essential:
“` V₄ owns: structure objecthood closure kinds unique maintainers phase coherence owner-leg correctness seam-log replay shape composition of runtime-supplied H evidence
Runtime owns: H values RuntimeExecutionFrames digests kernel/drain certificates threshold and constitution evidence actual artifact/environment/process facts “`
This is exactly the “read what you run” discipline: Lean verifies the structural linkage, while the runtime must supply the actual execution evidence. The proof stack explicitly avoids pretending that Lean computed hashes, verified OS/container attestation, or manufactured runtime H facts.
## Why this is stronger than the original seven-department story
Originally, the seven looked suspiciously like an assigned organisational taxonomy. The Class/Instance table was a direct match expression, not a derivation. The V₄ route corrected that by abandoning the wrong question.
The right question was not:
“` Which of the seven is Class, and which is Instance? “`
The right question was:
“` What are the seven existential closures of the whole V₃ holon? “`
Once that question was asked, the structure fell into place:
“` V₄ over V₃ → seven live complement-pair modes → seven existential objects → unique maintenance powers → structural holon-object interfaces → seven-object society → runtime GO cycles → H-convergent conditional closure “`
The department-capability names are now best read as renderings of maintenance powers, not as primitive axioms. Assess maintains the public-Form object. Observe maintains the public-Flux object. Plan maintains the private-Form object. Report maintains the private-Flux object. Coordinate maintains the Seam object. Delegate maintains the Walk object. Revise maintains the Merge object.
## What V₄ does not prove
The theorem is strong because it is bounded. It does not claim that the English names Assess, Observe, Plan, Report, Coordinate, Delegate, and Revise are forced. They remain a rendering layer. It does not prove full runtime holon-hood beyond the structural interface. It does not prove liveness, fairness beyond the canonical six-phase cycle, content-specific Publish/Integrate payload determination of the next Fit, or cryptographic / OS / container attestation truth.
The axiom footprint is also clear. The pure GO/coherence/convergence surface is choice-free, while the full runtime-facing closure inherits `Classical.choice` through the Bindings conformance predicates, specifically because their `String.length > 0` clauses pull it in from Lean core. The report explicitly treats that as a Bindings detail, not a V₄ defect.
## What V₄ means now
V₄ is the point where 4QX stops being merely a single holon grammar and becomes an object-space capable of enacting itself.
At V₃, 4QX says:
“` Here is the minimal holon form. “`
At V₄, 4QX says:
“` Here are the seven objects generated by that form. “`
At H3, the theorem says:
“` Given runtime evidence, those seven objects realise Generic Organisation closure. “`
That is a remarkable form of self-reference. The structure does not merely describe organisation. It produces its own organisational organs. Those organs are themselves holon-objects. Together, under runtime evidence, they execute the canonical cycle, replay through the seam, recurse Integrate into next Fit, and converge to H=0.
The slogan version is:
V₄ is V₃ becoming a society of its own meaning-objects.
The proof version is:
The seven V₄ holon-objects conditionally realise Generic Organisation closure as a runtime-facing, replayable, phase-coherent, owner-leg-correct, RuntimeExecution-conformant, Integrate→Fit-recursive, H-convergent cycle chain.
## The honest residue
The H3 line now has an intended stopping point. The report records the theorem as Green/conditional, locks the public surface so drift fails to compile, and opens follow-up gaps for full runtime holon-hood, name-forcing or rendering policy, runtime liveness, Bindings de-classicalisation, and content-specific Publish/Integrate-to-Fit strengthening.
That is the right outcome. The V₄ theorem should not be enlarged until those separate gaps are genuinely solved.
What has been proven is already substantial: the seven are no longer merely a department catalogue. They are the existentially closed holon-objects generated when V₄ objectifies V₃, and their society can conditionally realise the full Generic Organisation closure interface.