Papers
Formal derivations, theorems, and the mathematical backbone of Coherence Theory. Each theorem is presented with an intuitive bridge, the formal statement, and a collapsible proof.
Coherence Theory: Emergent Physics from the Selection of Stable Patterns→
V. Ilinov et al., April 2026
Derives quantum mechanics, general relativity, the Standard Model, and cosmology from eleven metaphysical priors and one selection inequality. No Hilbert spaces, no field equations, no gauge groups assumed — all derived.
- d=3 spatial dimensions (cost-optimal)
- SU(3)×SU(2)×U(1) gauge group (unique cheapest)
- Exactly 3 particle generations
- Physical constants as budget multipliers
- Dimension Slider — discover d=3 yourself
- Gauge Group Builder — why SU(3)×SU(2)×U(1)
- Constants Calculator — tune the universe
- Derivation Map — trace every result to axioms
Seed-Growth Organism Theory→
V. Ilinov & hiveKit Swarm, April 2026
How do organisms maintain coherence against novel disturbances they cannot anticipate? Four theorems derived from the ten CT priors, with falsifiable predictions across biology, neuroscience, ecology, and machine learning.
- Hidden Editor Opacity — structural blind spots that grow with complexity
- Multi-Root Resilience — multiple imperfect bets outperform one optimized bet
- Organism Tilt Dynamics — your best product reshapes your entire company
- Darwinian Emergence — evolution derived from CT, not assumed
Scaffold Poke Discovery
How Organisms Discover They Can Poke Other Patterns
The Asymmetry
You track what goes wrong automatically. When an API call fails, you log the error and write a handler. When a user complains, you file a bug. Your organization is a finely tuned incoming-poke detection machine. But when was the last time you checked what your tools can do that you have never tried?
The contact graph is symmetric: if pattern A can poke B, then B can poke A. But organisms exhibit a systematic operational asymmetry. They obsessively catalog incoming pokes (errors, failures, safety filters) while leaving their outgoing poke capacity largely unexplored (unused API parameters, untested configuration options, features they have never called).
This asymmetry is not accidental. It is derivable from first principles.
Structural Poke Asymmetry
Why does incoming poke awareness dominate? Because incoming pokes generate an immediate signal — the API call fails, the user complains, the credits are wasted. Unexplored outgoing pokes generate no signal at all. The generation succeeds. The user sees output. The organism persists. The gap between actual coherence and potential coherence is invisible, because the organism has never experienced the higher-coherence state.
Structural Poke Asymmetry
Show derivation
Step 1. The editor E expands coverage whenever a novel incoming poke is encountered — the encounter itself generates the signal and motivation. By A10, the organism adapts. Growth of incoming poke awareness is reactive and automatic.
Step 2. The explorer X expands coverage only when the organism deliberately allocates B_th to exploration — reading documentation, testing parameters, auditing scaffolds. This competes with immediate needs for finite budget (A7).
Step 3. Therefore incoming poke coverage grows automatically via reactive adaptation; outgoing poke coverage grows only via deliberate allocation against competing demands with unknown returns.
Your organization automatically gets better at handling problems it already knows about. But it does not automatically discover what else is possible. The capabilities you are not using represent coherence left on the table. Closing the gap requires deliberate investment in exploration, protected from being cannibalized by immediate firefighting.
The Five-Phase Discovery
The theory maps precisely onto a real case study: how the hiveKit swarm discovered unused capabilities in the Google Veo video generation API.
Phase 1: Root hits a wall
The organism tried reference images with image input. The API returned an error. The organism concluded "Veo does not support this" and stopped exploring. The editor repaired the immediate failure but could not see past the wall.
Phase 2: Root thickens
The organism added video extension. It took 6 failed attempts to find the correct input format. All 6 attempts explored variations within the same direction — single-root strategy.
Phase 3: Deliberate exploration
Accumulated leakage crossed a threshold. The organism dispatched a full API audit across all 7 model IDs. Resolution defaults, unused parameters, untried capabilities — each discovery was a new sub-root sprouting.
Phase 4: Paradigm discovery
The audit found first/last frame generation — adjacent in the documentation to the parameters being audited. This was not just a parameter; it redesigned the entire pipeline.
Phase 5: Organism tilt (snap)
The discovery resolved four accumulated leakage points simultaneously. CL_k spiked far above CL_others. The organism underwent a discontinuous snap: complete architecture redesign, no hybrid proposed.
The Audit Trigger
When should you audit your external tools for unused capabilities? The theorem provides a formal condition: audit when accumulated boundary leakage exceeds the exploration cost adjusted by expected return.
Show derivation
Step 1. Accumulated leakage represents coherence left on the table.
Step 2. Exploration cost is paid upfront. Expected return = probability of finding a capability times the CL gain from that capability.
Step 3. At SEP, the organism allocates budget where marginal return is highest. Exploration competes with known-return activities. The organism initiates exploration when expected return from exploration exceeds best known-return activity.
Bootstrapping problem: You need to audit to know you need to audit. Resolution: periodic audits on a fixed schedule, calibrated to the scaffold's update frequency.
Three triggers, in order of reliability: (1) accumulated B_leak symptoms at the boundary. (2) Scaffold change signals — changelog entries, new model announcements. (3) Periodic schedule — unconditional, independent of any signal. The optimal strategy uses all three.
Polycrystalline Domain Theory
Emergent spacetime as a mosaic of coherent domains
CT predicts that emergent spacetime is not a single perfect crystal but a polycrystalline foam — a mosaic of coherent domains, each with finite size and uniform internal scaffold orientation, separated by domain walls with quantized misorientation.
For your startup: your product is one grain. Your users' existing workflow tools are neighboring grains. The interface between your product and their workflow is a domain wall. The friction of adoption is surface tension at that wall.
Surface Tension
Surface tension is minimized at quantized angles — the same mathematics that governs metallic polycrystals and cosmic domain structure.
Perfect crystal. Zero surface tension. All tiles share the same orientation.
To minimize adoption friction: align your product's input/output patterns with the user's existing scaffold orientation. A tool with Delta_theta near zero has near-zero adoption friction. A tool that requires users to learn a new mental model pays quadratic surface tension.
Empirical Confirmation
The SDSS DR19 hexapolar anisotropy detection at greater than 5 sigma confirms the polycrystalline prediction. The observed tilt between the local galaxy hexapole and the CMB axis is 29.7 degrees — approximately pi/6, exactly half the fundamental D6 rotation.
What this means
The same mathematics that predicts adoption friction for your product also predicts the large-scale structure of spacetime. CT's predictions are domain-independent: the equations do not know whether they describe cosmic grains or product-user interfaces.
Hubble Tension Resolution
Within a domain, the Hubble parameter is direction-dependent:
Local measurements of the expansion rate sample an anisotropic flow within one domain, while CMB measurements sample the domain-averaged isotropic value. This resolves the discrepancy between local and early-universe measurements of the cosmic expansion rate.