Causal Budget Framework One budget, one ledger, all of physics.
CBF simulates reality as computational using a cellular‑automata interpretation. Each system spends a shared budget between Translation (T) and Maintenance (M), forming the rule C = T + M. A global Event Ledger selects which proposed interactions become reality and re‑synchronizes frames. Space and time are the visible trail of those confirmed events.
Huygens' Principle Cellular Automata
Simple per‑step rules that spawn complex wave behavior, written as a cellular‑automata loop.
Cellular Automata (CA) is a computer method that uses simple rules to update a grid. Each pixel waits until the next turn to move by one unit or to process an internal state. Huygens' Principle says every point on a wavefront can act like a source of a new wave.
CBF mirrors this behavior. In CBF, particles are vector‑based cellular‑automata wavefronts made from individual wave cells. Each wave cell follows simple rules that produce diffraction, interference, and clean commit selection at detectors.
Core CBF CA Wave Cell Rule (C = T + M)
Each wave cell divides its per‑tick budget between translation and maintenance.
- Translation budget T: portion used to move the wave cell along its vector.
- Maintenance budget M: portion used to keep the wave cell coherent and alive.
- Budget cap C: total per‑tick limit, enforced as C = T + M.
- Photons: M = 0, all budget goes to T, pure translation.
- T vector: direction and phase component representing momentum.
- Phase and spin placement: phase oscillates in motion with T, spin and other bound ticks live in time with M.
In CBF this separation is deliberate, moving oscillation is handled by the translation share, while bound‑state upkeep, including spin and internal ticks, is handled by the maintenance share. This keeps photons as pure movers and gives matter a baseline maintenance cost.
Huygens' style CA spawning rules
- Replace absorbed neighbors: spawn new wave cells where adjacent cells were absorbed.
- Edge diffraction: set the new cell vector at 90 degrees toward the side with missing neighbors.
- Coverage upkeep: when neighbors drift too far apart, spawn child cells to maintain coverage.
Double‑Slit Wavefront
- Particle as finite wavefront: A particle is a finite wavefront of wave cells, often a hollow shell large enough to span the slit region. The slits carve and redirect parts of the same parent wavefront. Outside of atoms, wavefronts such as electrons expand naturally until their internal tension reaches equilibrium, forming roughly spherical shells of probability. This self-stabilizing shape minimizes boundary stress between neighboring wave cells. Only when the field is broken—by confinement, measurement, or diffraction—does the shell distort or split into new fronts.
- Photons and electrons follow the same mechanism: quantized wavefronts of wave cells. Photons use M = 0 (all translation), matter has a baseline M.
- Wave cells encountering absorbers: create event proposals rather than instant collapses; the final commit happens later when the Ledger’s gates align.
- Collapse timing: delayed until the Event Ledger’s spatial, directional, temporal, and informational gates are satisfied.
Single‑Slit: Interference as Breaking and Healing
In CBF, interference does not require two independent waves. A single wavefront passing through one slit fragments into separate wave‑cell streams that arrive at slightly different times. When these fragments grow and reconnect at the detector, their phases add or cancel, producing the familiar fringe rhythm.
- Single‑slit interference: internal timing differences of one wavefront.
- Atoms can receive multiple arrivals with evolving phase, revealing the fringe map over time.
Double-Slit: Phase Addition Explains Fringes
One parent wavefront spans both slits, then splits into two fronts that take slightly different routes to each point on the screen. Different route length means different travel time, so the arriving wave cells are at different phases when they wash over each other. At the detector, proposals add by their local phase, and commit odds follow the squared magnitude of the complex sum: |Σ eiθᵢ|². Aligned phases boost commit probability, opposite phases cancel.
- Same source, two routes: both fronts come from the same initial wave, they just travel different distances.
- Travel time sets phase: a small time offset Δt creates a phase offset Δθ, which controls local addition or cancellation.
- Fringe rhythm: positions where Δθ is near 2πn are bright, near (2n+1)π are dark.
- Ledger timing: commits are chosen after phases are compared at arrival, not while the waves are in flight.
Turning C = T + M into a Triangle
A geometric view that connects the CBF budget law to relativity and energy–momentum structure.
In CBF, the per-tick budget C = T + M can also be expressed as a right-triangle identity: T² + M² = 1. This form reveals a deep link between computational pacing and the geometry of spacetime. Translation and Maintenance behave like perpendicular components of one conserved effort vector.
- Lorentz Factor: When an object moves faster, its translation share T grows while M shrinks.
Using
T = v/candM = √(1 − v²/c²)reproduces the Lorentz factor γ = 1 / √(1 − v²/c²), showing time dilation as reduced maintenance share. - Energy–Momentum Triangle: Multiply by constants
candmand the same shape yields E² = (pc)² + (m c²)². Energy corresponds to total budget, momentum to translation, and rest mass to maintenance. - Minkowski Geometry: Expressing spacetime intervals as c² dτ² = c² dt² − dx² follows the same structure, with time-like steps corresponding to M and space-like steps to T.
This triangle view shows that relativity emerges naturally when the universe’s compute budget is split between motion and upkeep. The same CBF loop that moves wave cells also defines the invariant geometry that physics observes.
Maxwell and Spin from the Same Budget
The same budget law that governs motion also sets the rhythm of oscillation. Field waves, spin states, and charge polarity emerge from how Translation and Maintenance exchange energy each tick.
Maxwell’s equations describe continuous field oscillations, but in CBF they arise from discrete T↔M exchanges. Every step that trades translation for maintenance reverses direction in the complementary channel, creating a natural two-phase oscillation that behaves like an electromagnetic wave.
- Electromagnetic fields: The electric and magnetic components correspond to alternating T and M phases. When a wave cell uses more T, it advances the field; when it uses more M, it stores field energy. The alternation reproduces Maxwell’s curl coupling without external equations.
- Spin as phase geometry: Spin is the internal clocking pattern of T↔M exchange. A spin-½ particle completes its full orientation only after two complete T–M cycles, which is why a 360° rotation flips its sign and 720° restores it.
- Photon polarization: For M = 0, the T channel alone carries the oscillation. Polarization then becomes a geometric pattern of how T’s direction vector rotates during propagation.
- Charged matter: Adding a small persistent M offset biases the exchange, producing a standing imbalance that acts as electric charge. The field responds to restore balance, creating the familiar Coulomb interaction.
In this view, Maxwell’s continuous waves, quantum spin, and charge all trace back to the same discrete rule: each cell must share its compute budget between moving and maintaining itself. The alternation of those two actions is what nature interprets as oscillation.

Matter vs Photons
Interactions only occur when at least one participant carries Maintenance share (M). Photons are pure Translation (T) and therefore do not interact with each other directly.
In CBF, every event requires at least one side to possess an M component— the capacity to pause, evaluate, and commit. Photons have M = 0, meaning they spend their entire budget on translation. They can transmit influence but cannot host an event themselves. Matter, on the other hand, always retains a nonzero M, providing the internal time needed for collapse processing.
- Photon–photon non-interaction: Since both are pure T, there is no shared maintenance channel to synchronize or exchange state. Their paths may cross, but no commit can form without M.
- Photon–matter interaction: Matter contributes the necessary M, allowing the Ledger to evaluate the event and perform a collapse. This is why light can be absorbed, emitted, or scattered by atoms but not by other light.
- Rest mass as baseline M: Each particle species has a built-in resting maintenance share that defines its stability and half-life. Heavier particles simply allocate more of their per-tick budget to M, leaving less for motion.
- Mass as commit capability: Having M means the system can host collapses. Photons travel as information carriers, but matter provides the memory surface where events become facts.
The distinction between matter and radiation is therefore not a different type of substance but a different budget allocation. Mass measures how much of a system’s compute share is reserved for maintaining its own state and participating in new collapses.
Role of the Atom
Atoms act as finite-state machines that host commits, store energy, and re-emit it as photons.
In CBF, atoms are compressed particle systems that operate like finite-state machines. They take particle inputs, process them using their internal state, and expel particle outputs. Because atoms carry nonzero M, they can host commits and maintain stored energy between events.
- T transfer into atoms: Incoming particle Translation, T, can be deposited into an atom, changing the atom’s T vector. In a lattice, this deposited T can be held as combined M+T vibrations, potential energy that can later be released as kinetic energy.
- Storage and release: When stored vibration is released as a photon, the emitted wavelength reflects the emitter’s clocking at emission, set by the atom’s current Maintenance share, M, and local pacing.
- Redshift in CBF: Observed frequency records the emitter’s proper time at emission, then may be further shifted by pacing differences along the path. In CBF, this maps to how T and M are transferred between systems since the Big Bang, which is what CBF calls entropy.
- Why atoms matter for commits: Atoms provide the M needed to evaluate, synchronize, and finalize events. Photons can carry information between atoms, but atoms supply the maintenance channel where interactions become facts.
Mass Hierarchy and Binding Energy
Baseline maintenance share sets species mass. Binding reshapes the budget, changing total rest mass.
In CBF, rest mass is the built-in M share a particle must reserve each tick to maintain its identity. Species differ by baseline M, set at creation by the background configuration that fixes their upkeep cost. Composite systems pool and constrain their members, which changes how much M they need together.
- Baseline M per species: Each particle type has a characteristic maintenance requirement. Higher baseline M means more “upkeep,” which appears as larger rest mass.
- Composites are not simple sums: When particles bind, some internal upkeep becomes shared. Constrained motion and phase locking reduce the net M the group needs.
- Binding energy and mass defect: The drop in required M is released as radiation or kinetic work. The bound system’s rest mass becomes mbound = mfree,total − Δm, consistent with E = Δm\,c².
- Hierarchy: Quarks inside hadrons, nucleons inside nuclei, and electrons in atoms each give up some independent freedom. Less free translation means less separate upkeep. Stronger binding, larger Δm.
- Stability and budget: More efficient M sharing improves stability. If constraints are weak, the system must spend extra M to stay bound and can decay.
- Photons carry off the savings: When binding tightens, the saved M is exported through the T channel as emitted photons, which take the released energy away.
Mass hierarchy follows from how much maintenance a structure must budget. Binding reorganizes that budget, lowering total M and releasing energy, which matches observed mass defects across scales.
Arrow of Time
Events are processed in order. CBF is not a block universe.
In CBF, the universe advances by selecting and committing Events in sequence. There is no pre-written block, and the cellular automata does not warp space. Space and time are flat and linear. What feels like curvature to an observer is a change in local pacing, often called clock speed in CA terms.
- Clocking: The substrate may run at a universal clock rate, but each system experiences time through its own Maintenance share M.
- Aging rule: Using more Translation than Maintenance means fewer internal ticks, so the system ages slower.
- Direction, not symmetry: At this level there are no time symmetries, only a forward arrow set by your current M.
Event • Commit • Collapse • Prune
From many possibilities to one outcome, then cleanup.
As wave cells pass through the world, they propose many tiny Events wherever interaction could occur. A single particle can seed thousands of these proposals before anything is finalized — CBF refers to this stage as pollination of atoms. At some point a selection step chooses one outcome, the Commit. Commits are all that can be processed by observers, not atoms or particles, only their valid interactions.
- Commit: The one proposed Event that wins and becomes reality. Everything else in that set is no longer eligible.
- Collapse: After a commit, all invalid proposals are globally erased along with the particle wavefront.
- Prune: The invalid or out-of-step proposals that are discarded during cleanup leave subtle routing biases, long-lived scars that steer later waves without adding mass. This behavior aligns with the large-scale dark-matter halos and Bullet Cluster lensing patterns seen in astronomy.
- Why double-slit observation changes things: A nearby sensor can force an early commit, thereby collapsing the interference into a fresh particle wavefront.
- Observer: Just another particle or atom to compare to.
- Commits create reality: Commits are created at a real time and place in the universe, independent of other observers. A Commit defines a successful interaction that can trigger new events, such as releasing photons or bouncing particles. In that sense, commits are the only way an observer can experience the universe. Particles and atoms only indicate where commits are likely, they are not experienced directly.
In short, many possibilities are generated, one is selected, the rest are cleared. The next section explains the decision rules behind that selection step.
Global Event Ledger
A single decision layer that coordinates proposals and selects one Commit for everyone involved.
The particle cellular automata and its interactions with other systems are coordinated by a global Event manager called the Event Ledger. Local, pairwise rules alone cannot explain gravity at a distance, entanglement, or collapse cleanup. The Ledger ties each candidate interaction to all relevant parties (particles and atoms) and makes one consistent decision.
A particle’s wave cells propose many Events. Before one becomes the Commit, proposals pass four gates:
- Spatial: which absorber is eligible at that location. The Ledger filters candidates to the correct place.
- Directional: which momentum direction matches. Signals must arrive with a compatible vector.
- Temporal: when phases align and clocks synchronize. Proposals wait until timing is consistent.
- Informational: what is known or hidden, including delayed choice. Eligibility depends on available information.
Responsibilities
- Collect proposals: gather all candidate Events from wave-cell “pollination.”
- Apply eligibility test: evaluate proposals with the four gates.
- Frame syncing (temporal gate): align local clocks and phases so candidates can be compared fairly.
- Select one Commit: choose the single winner shared by all involved systems.
- Frame syncing (post-commit): re-synchronize participants so timelines line up for the next update cycle.
- Collapse & prune: clear losing proposals and reset the spent wavefront.
- Write routing bias: record subtle, non-mass scars that can steer later waves (Dark Matter).
- Maintain global consistency: ensure the same outcome is seen across observers and frames.
Special Relativity and Time Symmetry
The temporal gate of the Event Ledger naturally produces relativistic timing and apparent symmetry between observers.
In CBF, the temporal gate that synchronizes interactions is the mechanism behind Special Relativity. Two systems with different Maintenance shares (M) cannot communicate on a one-to-one tick basis. Each must synchronize so that both experience the same interaction in their own local time. This synchronization occurs at the Ledger’s universal clock level but is observed differently in each system’s proper time.
- Temporal gate and relativity: Synchronizing commits across systems with different M values means that faster-moving frames must delay their interactions until both sides can align. The result is apparent time dilation, a direct outcome of the Ledger’s scheduling process.
- Collapse buffering: Because each interaction waits for this synchronization, collapses are delayed. This buffering gives rise to relativistic pacing—events appear stretched in time for fast or low-M systems.
- Local vs global clocks: The universe processes commits in a single sequence, but each observer’s M defines how many of those global ticks they can process per their own second.
Time Symmetry and Queue Buffering
Observers experience time symmetry not because motion is reversible, but because the waiting time between mismatched frames balances out communication. A system with less M (faster time) must wait for responses from a system with more M (slower time), while the slower frame accumulates pending signals from the faster one. The result is the illusion that both clocks slow equally when viewed from the other’s perspective.
- Queue buffering: The backlog of pending commits between mismatched frames produces apparent symmetry in time dilation.
- Mutual waiting: Each frame’s progress depends on the other returning signals, creating a natural reciprocity.
- No true reversal: The symmetry is only visual; the underlying universe still runs forward through sequential commits.
Special relativity in CBF therefore emerges from temporal gate synchronization and queue buffering within the Event Ledger—no continuous spacetime fabric is required.
Queue Buffering and General Relativity
High traffic slows local pacing. The global Ledger matches incoming signals to the queue, which appears as gravity.
The same synchronization that produces time symmetry also produces gravity in regions with heavy interaction load. When an area is buffering many interactions, unrelated signals build up in the queue. The global Event Ledger slows all incoming proposals to match the current traffic. Observers experience this as local time running slower. In CBF, C in C = T + M is a scalar pacing variable that depends on local traffic, not a fixed constant. Where traffic is high, C(x) is smaller, so fewer translation and maintenance steps fit in the same universal tick.
- Queue depth sets pacing: More pending proposals in a region mean a smaller effective C there. Local clocks slow.
- Global fairness: The Ledger delays distant arrivals so they enter at the slowed pace. Signals respect the queue.
- Relativistic outcome: Slower local pacing reproduces gravitational time dilation and path bending.
Queue Buffering in Cellular Automata
The Ledger must keep a particle’s wave cells coherent. Near a gravity well, cells closer to the well have a smaller C and therefore a smaller M than cells farther away. To prevent shear, the system normalizes all wave-cell vectors toward the imbalance. This restores internal agreement and produces a slightly rotated net direction.
- Step 1: Queue causes a gradient in C(x). Lower C near the well, higher C away from it.
- Step 2: To keep one particle intact, wave-cell vectors are re-aimed toward the lower C side.
- Step 3: The lower side now sits deeper in the well, so the imbalance repeats.
- Result: Iterated normalization yields continuous acceleration toward the well.
This update rule bends paths without curving the substrate. What looks like spacetime curvature is the visible trail of many synchronized, slowed commits in a gradient of queue depth.
General relativity in CBF is the large-scale outcome of synchronized pacing and queue management. Gravity is how the Ledger keeps traffic coherent when many proposals compete in one region.
Friction and Inertia as Queue Effects
- Inertia: Changing direction or speed requires re-aiming many wave cells against the current queue pattern. The need to re-establish coherent vectors appears as resistance to change.
- Friction: In a lattice with a pacing gradient, collapses are preferentially accepted along slower paths. Repeated small prunes drain translation into local maintenance and heat, which appears as drag.
Gravity in an Atom Lattice
Downward particle flow plus slower clocks at the bottom create stored vibration, potential energy.
In a solid lattice, gravity appears as two linked effects. First, particles and wave-cell proposals drift toward the lower pacing region, downwards. Second, atoms deeper in the well process more slowly than atoms above them, so arrivals queue up. The lattice stores incoming Translation, T, as M+T vibration, potential energy, until conditions allow release.
The double effect
- Downward flow: Queue depth increases toward the bottom, so effective C(x) is smaller. Wave cells normalize toward the imbalance and drift downward through the lattice.
- Queue storage: Bottom atoms have less available pacing per tick, so proposals accumulate. Translation that cannot be processed is held as local vibration, M+T, inside bonds.
Hold, then release
- Holding an object: External supports prevent net translation. Incoming T is redirected into lattice vibration, potential energy. The queue at the bottom grows and the structure warms slightly.
- Letting go: When supports are removed, stored T is re-routed into translation. The object accelerates downward as vector normalization repeats at deeper levels.
- Stepwise fall: Each tick restores coherence by re-aiming wave cells toward the lower C. Energy appears as a swap between stored vibration and translation during descent.
Friction and heat
- Microscopic prunes: Small inelastic commits convert some downward T into permanent lattice vibration, heat.
- Path preference: Collapses are accepted where pacing allows, which biases motion along slower channels and surfaces.
In this view, gravitational potential energy is queued translation stored as lattice vibration. Releasing the object lets the queue drain into motion while the same normalization rule bends the path toward the well at each step.
Informational Gate
Where knowledge, environment, and timing meet to select globally consistent events.
The Informational Gate is the part of the Event Ledger that scores candidate events using locally valid physics plus what is known, what is hidden, and when information becomes available. This makes the commit step information-sensitive without violating causality. In simulations, a learnable scoring function reduces trial counts and biases selection toward stable outcomes. If an analogous mechanism exists in nature, it could help explain why we observe a single, coherent history rather than many inconsistent branches.
- Context matters: Proposals are weighted by physics, data availability, and information delays (for example, delayed-choice style setups).
- Learnable scoring in simulation: The gate’s scoring can be tuned from past commits to improve stability and consistency. This replaces brute-force sampling with guided selection.
- Global consistency: Commits must fit both local constraints and the Event Ledger’s global history. The goal is a single coherent outcome, not many worlds.
The Informational Gate ties knowledge to dynamics. It keeps commits causal and consistent while allowing practical, data-aware selection in simulations.
Theory in a Nutshell
A cellular-automata loop with a per-tick budget C = T + M and a global Event Ledger.
Particles are wavefronts of wave cells. Each cell either moves one unit (T) or services internal state (M). Interactions create event proposals. The Ledger selects one commit, prunes the rest, and advances the world by one tick.
- Budget law: C = T + M per tick, per entity.
- Ledger: Four gates choose commits, then everyone re-syncs.
- Relativity from sync: temporal alignment across frames produces time dilation and symmetry.
- Gravity as pacing: queue depth slows local C, bending paths without curving space.
- Fields: local guides that shape rates and routes.
- Photons vs matter: photons have M = 0, matter has baseline M.
- Commits create reality: only committed interactions are experienced by observers.