Quantum Foundations

Double-Slit Experiment

Interference arises from phase alignment during commit. A detector resets the pattern by creating a new particle under the CBF new-particle rule.

  • Wave propagation: A photon or electron leaves its source as a coherent field of wave cells. Each cell carries phase and direction data in T. The Event Ledger buffers all potential paths as uncommitted options.
  • Slit diversification: Passing through two slits diversifies the set of momentum vectors kᵢ. Their relative phases beat against each other, and the ledger’s temporal gate prefers commit points where phases align (Δθ ≈ 0). The observed intensity pattern follows |Σ e^{iθᵢ}|², the Born-rule map.
  • Commit event: The final detection is a single commit that satisfies all four gates—temporal, spatial, conservation, and informational. The pattern of likely commits emerges statistically from phase-matched candidates, not from multiple particles interfering with themselves in real space.
  • Adding a detector: Placing a sensor or quantum dot near a slit changes the ledger structure. The detector absorbs or re-emits a particle, triggering the new-particle rule: the old interference network is cleared, and a new rounded wavefront begins from the detection site.
  • Result: With both slits open and unmeasured, the commit field spans both paths, producing an interference map. When a slit is monitored, the event chain is reset at the detector, collapsing the multi-path coherence into a single emission.
  • Why this matters: The pattern changes because the causal structure changed, not because the particle “knew” it was observed. Every detection spawns a fresh source, preserving causality and enforcing forward-only ledger growth.
CBF Resolution: Interference is phase alignment across multiple candidate paths in the Event Ledger. When measurement creates a new emission, the old coherence is replaced by a single rounded wavefront— a direct result of the CBF new-particle rule.

Measurement Problem

In CBF, measurement is when two or more systems co-author a commit through the four gates. No collapse, no observer magic.

  • Definition: A measurement occurs when separate systems interact strongly enough to create a shared event in the Event Ledger. For a commit to succeed, all four commit gates must align: temporal, spatial, conservation, and informational.
  • Physical gates: The first three—timing, position, and conservation—are ordinary physics. They check that the exchange obeys phase, momentum, and energy rules. When these pass, a candidate commit forms.
  • Informational gate: The last gate ensures the new commit fits the global network of known states. It binds the event into the universe’s consistent storyline. This is not human consciousness; it is contextual alignment inside the global Event Ledger.
  • Why it looks mysterious: When the informational gate lags—such as in delayed-choice or entanglement tests—the commit waits for all relevant systems to reconcile. When reconciliation completes, the commit finalizes in one tick, giving the illusion of “collapse.”
  • Universality: Every interaction, from photon absorption to human observation, uses the same four gates. Human awareness is simply one more system participating in the synchronization.
CBF Resolution: Measurement is not collapse. It is the joint creation of an event when all four commit gates align, ensuring both physical and informational consistency across systems.

Particle–Wave Duality

In CBF, particles are spheres of wave cells that expand in flight and compress in atoms. We see commits as particles and oscillation as waves.

  • Wave-cell structure: Every particle is a coherent sphere of wave cells carrying both phase and momentum direction. In flight, the sphere inflates as T-mode translation dominates. Inside atoms, it compresses as M-mode maintenance holds it together.
  • Continuous oscillation: Each wave cell alternates its budget between T and M every tick. This oscillation is what we perceive as a wave—energy flowing between motion and maintenance phases.
  • Commit events: A commit happens when one region of the sphere satisfies all four gates—temporal, spatial, conservation, and informational. That small region interacts with an atom or detector, leaving the imprint we call a “particle hit.”
  • Why it feels dual: Between commits, the sphere acts like a field that spreads, interferes, and self-heals. At the moment of commit, it localizes as if it were a single particle. The apparent duality is simply the two phases of the same update cycle: propagation versus reconciliation.
  • Compression and inflation: Bound systems keep their wave cells compressed by continuous M-mode upkeep. Free particles inflate their cell lattice outward in T, distributing probability across space until the next commit resets it.
  • Human perspective: What we call “particle detection” is just the winning section of the wave sphere that succeeded in committing. What we call “wave behavior” is the collective oscillation of its wave-cell network between commits.
CBF Resolution: A particle is always a sphere of wave cells. In motion, it behaves like a wave of oscillating T and M budgets; on commit, it appears as a point-like particle. The duality is perception—one process viewed from two update phases.

Spatial Superposition

A single particle travels as a coherent sphere of wave cells that can touch many atoms at once. Only one site commits when all four Ledger gates are satisfied.

  • Particle as a touching field: A particle in flight is a spherical front of wave cells. Each cell can pollinate a nearby atom. This produces many eligible candidates at once in the Event Ledger.
  • Commit rule: four gates must agree: A physical outcome appears only where all gates reconcile: temporal for phase alignment, spatial for momentum and placement, directional for angular consistency, and the informational gate for semantic consistency when knowledge is involved. Exactly one site becomes the recorded commit, others are pruned in the D-ledger.
  • Why superposition is spatial: Before commit, the wavefront touches many atoms with nonzero eligibility. The particle is not many particles. It is one coherent front that offers many possible absorption sites. The final location is chosen by the gates, not by splitting the particle.
  • Interference and diffraction: Edges and apertures tear the phase map then the wavefront heals as it propagates. The healed front diffracts through the slit or slits, creating a richer set of directions. This increases the number of places where wave cells can touch atoms. The gate statistics over this expanded touching set produce the familiar fringe pattern.
  • Observation and uniqueness: When one site commits, competing offers are removed. The recorded event is unique. Other touched sites leave only pruning scars in the D-ledger that bias future attempts but do not count as additional particles.
CBF Resolution:
Spatial superposition is a single wavefront touching many atoms. One site wins when temporal, spatial, directional, and informational gates agree. Interference patterns arise because diffraction increases the number and phasing of touch points before the single commit is chosen.

See also: Spatial Relativity of Commits, Beat-Matching, Length Contraction, Measurement and the Ledger Gates.

Spin Superposition

Spin in CBF is a quantum spinor in M, not a classical rotor. SU(2) dynamics and Pauli measurements select outcomes at commit.

  • State: Each particle carries a two-component spinor |ψ⟩ ∈ ℂ² in the Maintenance channel. Superposition is genuine: |ψ⟩ = a|↑⟩ + b|↓⟩ with |a|²+|b|²=1.
  • Rotation (SU(2)): Internal spin updates are U(n,θ)=exp(-i θ σ·n / 2). The 720° property follows from SU(2) being a double cover of SO(3).
  • Measurement (Pauli): Along axis n, the observable is S_n = (ħ/2) σ·n. Commit projects with P_±=(I ± σ·n)/2. Outcomes are ±ħ/2 with Born weights ⟨ψ|P_±|ψ⟩.
  • Stern–Gerlach: Spin couples via H = -μ·B with μ = γ S. A field gradient produces F = ∇(μ·B), splitting trajectories by ± branches. The commit gate finalizes one eigenbranch with the Born distribution.
  • Entanglement: Pairs use a joint spinor in ℂ² ⊗ ℂ² (e.g., singlet). The ledger forms a Simultaneous Commit Group and resolves a single global outcome, producing quantum correlations without FTL signals or predetermined values.
  • Addition rules: Spin addition emerges from tensor products and Clebsch–Gordan reconciliation during commit (e.g., singlet j=0, triplet j=1 for two spin-1/2).
CBF Resolution: Spin is a quantum spinor stored in M with SU(2) dynamics. Measurements are Pauli projections at commit, yielding ±ħ/2 and the 720° feature. Entangled outcomes arise from a single global commit across the SCG, matching Bell-test results without local hidden variables.

Uncertainty Principle

In CBF, uncertainty comes from finite commit bandwidth, not fuzzy reality.

  • Finite sampling: The Event Ledger records commits in discrete ticks with limited phase resolution. Each tick can either refine T-mode translation (momentum) or lock a sharp position, but not both at once.
  • Position commits: A sharp location means many nearby wave cells synchronized their phases to produce a single spatial commit. This drains budget from tracking the continuous phase advance that carries momentum.
  • Momentum tracking: Smooth motion is represented by consistent phase advance between commits. When translation dominates, individual position commits blur across multiple cells.
  • Budget tradeoff: Δx Δp ≳ ℏ/2 emerges naturally from sharing a finite update budget. Precision in one domain uses commit capacity that would have refined the other.
  • No hidden randomness: The particle always follows deterministic CA rules; the uncertainty comes from how finely the ledger can sample phase and timing.
  • Measurement link: When a measurement locks position, it forces a high-resolution spatial commit, leaving momentum unconstrained until later gates realign.
CBF Resolution: Uncertainty is a computational bandwidth limit. The same tick budget cannot refine both position and momentum, so precision in one drains the other. Reality remains definite; our commits are just discretely timed.

Causality and Retrocausality

CBF never runs events backward in time. Apparent retrocausality comes from informational gate caching, not reversed cause and effect.

  • Forward-only ledger: The Event Ledger appends commits in causal order. Each tick consumes its local budget C = T + M and adds one new layer to history. Nothing ever rewinds or overwrites previous commits.
  • Informational gate caching: When systems are not yet synchronized, the informational gate can hold uncommitted correlations in a temporary cache. These cached relations store pending context so later events can finalize consistently without breaking conservation rules.
  • Late binding: Once all participants share enough information, the cached gate resolves and the ledger writes a single consistent commit. To observers, it can look like the earlier event “knew” about the later choice, but in CBF this is just deferred reconciliation of the informational cache.
  • Quantum experiments: In delayed-choice and entanglement setups, the informational cache keeps options open until all relevant systems are linked. When synchronization occurs, the commit appears to update both ends at once, giving a false impression of retrocausal influence.
  • Why it stays causal: Every commit still obeys forward tick order in the ledger. The informational cache adjusts eligibility, not the direction of time.
  • Predictive power: CBF predicts that any setup showing “retrocausal” behavior will involve delayed informational synchronization, never negative tick flow.
CBF Resolution: Retrocausality is an illusion created by informational gate caching. The Event Ledger always processes forward; cached context allows later knowledge to align earlier commits without rewriting time.

Quantum Erasure

CBF treats quantum erasure as deferred commit pruning. The ledger stores outcomes until the full informational context is known, then resolves backward through the chain.

  • Commit caching: When a particle passes through a dual-path system, each path writes a provisional entry in the Event Ledger. These partial commits store timing, momentum, and phase data but remain unfinalized because the informational gate has not yet cleared.
  • Why the delay: The ledger must know whether which-path information exists anywhere in the network. Until that context is resolved, both paths stay cached as viable options.
  • Erasure condition: When later equipment erases or scrambles which-path data, the informational gate reopens. The ledger then reconciles the cached entries into a single interference-style commit, as if no path distinction ever existed.
  • Pruning mechanism: The final decision propagates backward through the cached chain, pruning everything that would contradict the chosen informational context. It does not rewrite history—those entries were never finalized. They were pending buffers awaiting this global reconciliation.
  • Why it looks retrocausal: Because the backward pruning touches events that occurred earlier in classical time order, observers think the later measurement changed the past. In reality, the past was incomplete until the informational gate cleared.
  • Unified process: The ledger always runs forward in tick order. The erasure experiment simply delays the final commit until both the question and the answer are known, completing the ledger entry in one causal transaction.
CBF Resolution: Quantum erasure is deferred reconciliation, not retrocausality. Commits remain cached until the full informational context is available. When the answer arrives, it prunes backward through the pending chain, finalizing one consistent history across all systems.

Quantum Entanglement

CBF explains entanglement as a single global commit across a Simultaneous Commit Group (SCG), not faster-than-light influence.

  • Shared state: When two systems interact strongly enough to exchange conservation constraints, their local wavefronts merge into a joint state |Ψ⟩ ∈ ℂⁿ ⊗ ℂᵐ. Each subsystem keeps its own ledger entries but shares a common commit eligibility through the Event Ledger.
  • Simultaneous Commit Group (SCG): The ledger buffers all correlated participants in one group. A successful commit must satisfy the four gates—temporal, spatial, conservation, and informational—for the entire group simultaneously.
  • Global reconciliation: The commit is solved as a single contextual event. Once the ledger writes it, every member’s outcome becomes fixed at once, even if they are spacelike separated in classical geometry.
  • No faster-than-light signals: Correlations appear instant because there is only one global commit, not two independent local updates. No information travels between wings; they are resolved together inside one ledger transaction.
  • Bell-test alignment: The joint commit violates local hidden-variable bounds but remains within the Tsirelson limit. Outcomes are not predetermined; they are set contextually when the SCG passes the informational gate.
  • Universality: Spin pairs, photon polarization, or energy-time entanglement all use the same mechanism. The type of variable differs, but the commit logic is identical: a single causal ledger entry consistent across all observers.
CBF Resolution: Entanglement is not communication at a distance. It is one contextual commit written across multiple systems within the same SCG. Bell violations arise naturally because outcomes form through a single non-local reconciliation, not hidden variables.

Quantum Tunneling

Barrier crossing in CBF comes from self-healing wavefronts navigating hazard and path cost.

  • Self-healing CA particle: A particle is a coherent shell of wave cells that heal and re-vectorize after losses. The shell keeps phase-coherent options alive by redistributing budget across directions in T.
  • Barrier model: Inside a barrier the MCF raises loss and phase lag, which increases local hazard h(x). Two-lane update: monitor lane applies attenuation and phase delay, collapse lane applies a stochastic absorption hazard. Budget in M does maintenance, T tries to advance.
  • Microchannels: The self-healing shell continuously re-aims around high-hazard cells, probing lower-cost paths through microscopic gaps, defects, or thin regions. Partial attenuation shrinks amplitude but does not kill the shell if coherence holds.
  • Commit rule: A transmit commit occurs when a surviving front reaches the far side while passing the four gates (temporal, spatial, conservation, informational). Failed attempts write small D-field scars that bias future paths away from dead zones.
  • Thickness and height: Transmission falls exponentially with effective path cost. Thicker or higher-loss barriers increase attenuation and absorption probability, so fewer self-healed fronts make it through.
  • Resonance windows: Cavities or layered barriers can return phase that assists healing. When accumulated phase aligns, the beat map improves and transmission spikes.
  • Equivalence with RF and materials: The same hazard accounting reproduces skin depth in conductors and evanescent coupling in dielectrics. Tunneling is the barrier limit of the same budget law, not a special case.
CBF Resolution: Tunneling is a self-healing wavefront finding a viable low-cost path through a lossy region. Hazard attenuates most candidates, a few survive, and a transmit commit records success. The D-field remembers failures, shaping future probability flow.

Schrödinger’s Cat (Cat in the Box)

CBF resolves the paradox by treating observation as ledger synchronization, not wave collapse.

  • Local commit: The decay, detector, and poison system inside the box follow the same C = T + M rule as anything else. When the decay reaches its threshold, a commit is written to the box’s local Event Ledger. The cat is either alive or dead from that tick onward.
  • Isolation boundary: The sealed box prevents information flow, so an outside observer’s ledger has not yet synchronized with the box’s internal ledger. “Unobserved” means not yet reconciled, not undecided.
  • Observation: Opening the box merges the observer’s ledger slice with the box’s record. The observer receives the existing commit rather than creating a new one.
  • Outcome: The cat’s state is definite the entire time. Superposition describes the observer’s uncertainty, not the cat’s existence. The universe never splits, because the Event Ledger appends commits in one linear timeline.
CBF Resolution: The cat is not both dead and alive. The Event Ledger operates on linear causal time, so only one consistent commit can exist. Observation is synchronization between ledgers, not creation of reality.

Relativity & Time

Twin Paradox

In CBF, aging depends on how each observer splits their causal budget. The traveler uses more T and less M, so their ledger queue grows and they age slower.

  • Budget law: Every system follows C = T + M. T handles motion and translation; M handles maintenance and internal processing (aging).
  • Earth twin: The twin on Earth devotes most of their causal budget to M. Their local queue drains quickly, keeping biological and atomic processes fully maintained—what we call “normal” aging.
  • Traveler twin: The twin on the spaceship invests more budget into T to maintain high-speed translation. With less M available, their internal maintenance ticks process more slowly, so fewer internal updates occur per global ledger tick.
  • Queue buffering: Both twins experience time symmetry visually, since each sees the other’s clock running slow through queue buffering. But when they reunite and the ledger synchronizes, the twin who spent more budget on T shows fewer completed maintenance commits—less elapsed aging.
  • No acceleration paradox: Acceleration isn’t required in CBF. The time difference comes directly from the ongoing T↔M tradeoff, not from frame changes or spacetime curvature.
  • Why time symmetry is illusionary: The apparent symmetry between moving frames arises because each twin only sees the other’s queue buffering, not the true budget allocation. Real ledger processing is asymmetrical—less M means slower internal evolution.
CBF Resolution: The twin who spends more of their causal budget on translation and less on maintenance ages slower. Time dilation is just a bookkeeping effect of C = T + M, not a paradox. SR’s symmetry is visual only—each twin’s true aging rate is set by how much M they have left to process their own ledger queue.

Length Contraction

A projection created by pacing differences. Motion alters how often a system commits to the Event Ledger, and the slower frame’s α-slice re-aligns those commits into a single view. The result looks shorter or slightly rotated toward the observer, even though nothing bends or compresses in the Ledger itself.

  • Ledger perspective: Every collapse happens at a definite place and tick. The object’s world-tube stays straight and unbroken. What changes is the angle at which the observer’s α-slice intersects that world-tube.
  • Commit pacing and motion: A moving system spends more of its causal budget on translation (T) and less on maintenance (M). Fewer commits per global tick mean that its internal updates occur less often than those of a stationary observer. This timing mismatch is the real source of both time dilation and the apparent shortening along motion.
  • Reprojection through the slow frame: The observer’s slower α-slice gathers arrivals that occur together in their pacing, even if those emissions left the moving system at different ticks. Earlier emissions from the trailing side have more time to advance before the image is assembled, so the object appears tilted or bent toward the observer. The slower frame always sees faster systems leaning in its direction, because its temporal gate must stretch their sparse commits into simultaneous arrivals.
  • Geometry of timing: What appears as contraction or rotation is the spatial imprint of timing reconciliation. A single α-slice through differently paced worldlines never cuts them at equal ticks, so its projection onto the observer’s coordinates becomes skewed. That skew is the visual or measured “shortening.”
  • Unified view: Whether caused by motion or by slower α regions near mass, the same rule applies: slower pacing pulls apparent direction toward itself. Motion and gravity are both forms of temporal-projection curvature, not mechanical deformation.
CBF Resolution:
Length contraction is the visible footprint of pacing reconciliation. Fast systems commit less often; slow frames re-sync those commits through their α-slices, producing a projection that looks shortened or curved toward the observer. The Ledger remains unchanged—the geometry we see is the geometry of timing, not of matter.

Andromeda Paradox

Time in CBF is linear in the Event Ledger but relative to each observer’s queue buffering. The paradox disappears once signaling limits are included.

  • Linear ledger time: The Event Ledger processes all commits in strict tick order. There is only one global timeline of accepted events—no branching or multiple presents.
  • Observer queues: Each observer maintains a local commit queue based on their motion and α(x) pacing. The faster they move, the more events accumulate before synchronization, giving them a slightly different sense of “now.”
  • Relative perception: Queue buffering lets both the stationary observer and the jogger perceive each other’s clocks as offset, even though both live on the same ledger timeline. This creates the illusion that distant events—like the Andromedans deciding to attack—occur at different moments for each observer.
  • Signaling constraint: True reconciliation only happens when information actually arrives through light-speed communication. Because Andromeda is millions of years away, neither observer’s local queue can be updated in real time, so both share the same unresolved state.
  • What this means: Both the person sitting and the person jogging exist on the same ledger tick as the Andromedans. The perceived difference in “now” is just a phase lag in each observer’s buffered view, not a real difference in universal time.
  • Why the paradox vanishes: In CBF, simultaneity is not absolute but derived from queue drain rate and signal connectivity. The Event Ledger never splits; only the observers’ update schedules diverge temporarily.
CBF Resolution: The Andromeda Paradox is an illusion of queue buffering. Time in the ledger is linear, but observers drain their event queues at different rates. Without direct signaling, distant events remain unsynchronized yet still occur on the same universal tick.

Arrow of Time

Time moves forward because the Event Ledger processes commits in tick order. Apparent symmetry is a queue effect, not reversal.

  • Ledger tick: Every update in the universe follows the same budget rule C = T + M. Translation (T) handles motion, Maintenance (M) handles local state. Each tick finalizes new commits, extending the ledger in one direction.
  • Forward-only processing: The ledger is append-only; once a commit is written, it cannot be undone or rewritten. This one-way growth defines the physical arrow of time.
  • Apparent symmetry: Time-symmetric laws emerge because queue buffering lets two observers see each other’s clocks as running slow. Both drain and fill their commit queues at different rates, creating the illusion of reversible symmetry while processing remains strictly forward.
  • No backward ticks: Even when equations look time-reversible, the ledger never processes negative ticks. Every event consumes its causal budget and moves the system toward higher reconciliation depth.
  • Entropy as queue density: Growing queues of unresolved commits correspond to rising entropy. When reconciliation succeeds, local order increases but global backlog still grows, giving the overall sense of time’s flow.
  • Meaning of now: The present moment is the active tick being processed. The past is committed history, the future is unprocessed budget still waiting in the queue.
CBF Resolution: Time’s arrow is the ledger’s tick processing direction. All commits append forward under C = T + M. Observer symmetries arise from queue buffering, not genuine reversibility.

Grandfather Paradox

The Grandfather Paradox requires a block universe. CBF has no block—only an ever-growing ledger of forward commits.

  • No pre-written timeline: The Event Ledger is not a static block of spacetime. It is an ongoing computation that appends new commits one tick at a time. Once written, past commits are immutable history, not interactive regions of space you can re-enter.
  • No past access: Time travel to the past would require reopening a closed commit, which the ledger forbids. Each entry has a permanent checksum linking it to previous commits. Altering one would invalidate the entire chain.
  • Why loops fail: A causal loop like “go back and stop your grandfather” has no ledger pathway. The necessary retro-commit would conflict with already reconciled entries, so it fails the conservation and informational gates.
  • Block universe myth: In classical relativity, time appears like a frozen 4D landscape. CBF treats that geometry as the **rendered output** of prior commits, not an editable file. The universe isn’t stored; it’s continually being processed.
  • Why time feels continuous: Queue buffering smooths the append cycle into a seamless flow, creating the illusion that the future already exists. In truth, it’s just the next tick waiting to be committed.
  • Self-consistency rule: Any attempted retro action automatically fails reconciliation. The ledger allows only consistent forward solutions—no paradoxes survive commit filtering.
CBF Resolution: The Grandfather Paradox cannot occur because the universe is not a block. The Event Ledger appends commits forward only. The past is read-only memory; the future doesn’t exist yet. No causal loop can be written into a system that never rewinds.

Gravity

In CBF, gravity is frame synchronization at two levels: wave-cell alignment for particles and queue buffering for matter.

  • Particle level: Free particles adjust their phase and direction so their wave cells stay in sync with the surrounding α-field. This “frame syncing” naturally bends trajectories toward slower pacing regions, creating curvature-like motion without a force.
  • Atomic level: Atoms are dense systems of internal particles whose T-mode motion is constantly being re-aimed downward by local α gradients. Queue buffering makes these falling translations accumulate as M-mode vibration—what we experience as gravitational potential energy.
  • Energy exchange: When the object is released, stored M relaxes back into T. The system renormalizes its motion, converting vibration into translation. However, deeper in the well, the baseline α is slower, so the process repeats at a lower overall tick rate.
  • Unified field view: Gravity and time dilation are the same pacing effect seen from different sides: α(x) sets the local clock rate, while g(x) is the directional derivative of that pacing field.
  • No extra force law: There is no separate gravitational “pull.” It is simply the system’s continuous attempt to keep all wavefronts frame-synchronized while conserving C = T + M.
  • Potential energy as bookkeeping: Stored M is just queued maintenance budget awaiting release. The deeper you go, the longer each tick takes to process, which is why time runs slower in stronger gravity.
CBF Resolution: Gravity is the result of frame synchronization across α(x). Particles bend because their wave cells align to slower ticks, and matter stores that delay as M-mode vibration until released as T when the queue empties.

Gravity & Cosmology

Many-Worlds vs CBF

CBF allows only one successful commit per event, so there is only one world.

  • One ledger: The universe maintains a single Event Ledger. Every commit is appended in linear causal order, never duplicated or branched.
  • Alternatives: Possible outcomes exist temporarily as pending entries in the buffer. When reconciliation succeeds, one commit is written and the rest decay as D-field scars.
  • No branching: There is no mechanism for spawning parallel ledgers because budget and conservation rules must balance globally. The same compute resources cannot sustain multiple copies of history.
  • Perceived probability: The familiar quantum probabilities describe which pending paths are most likely to pass the commit gates, not parallel worlds being born.
CBF Resolution: Only one consistent commit can exist per event. The universe evolves as a single, continuously updated ledger—not an expanding forest of worlds.

No Block Universe

CBF treats reality as an active computation that grows one commit at a time, not a static 4-D block.

  • Continuous creation: The Event Ledger is append-only. Each new commit adds to the history chain, extending reality forward in causal time.
  • Past, present, future: Past commits are recorded and immutable. The present is the latest successful commit. The future exists only as uncommitted possibilities in the buffer.
  • Time’s flow: Time advances because new commits appear sequentially, not because observers move through a fixed spacetime block.
  • Relativity preserved: Different observers may disagree on commit ordering, but all agree on the single growing ledger they share once synchronized.
  • Implication: The universe is an ongoing process of reconciliation, not a completed structure waiting to be read.
CBF Resolution: Reality is not a frozen block of spacetime. The Event Ledger is a live computation that appends new commits in causal order—an ever-evolving universe rather than a finished film reel.

Black Holes and Singularities

CBF replaces infinite curvature with finite-precision stalls in α(x). Black holes are commit slow zones, not tears in space.

  • Finite pacing, not infinite gravity: The α-field defines the local tick rate of commit processing. Near a dense object, α slows continuously toward zero but never reaches it, so there is no true singularity—only a region where new commits stall.
  • Queue saturation: As α → 0, translation T halts and all incoming motion converts into M maintenance load. The object becomes a queue-buffered ledger region storing immense amounts of unresolved state (potential energy).
  • Horizon definition: The event horizon marks where local commit time exceeds the rest of the universe’s tick pace. From outside, no new commits appear; inside, updates continue at vanishingly slow rates relative to external frames.
  • Information conservation: All information remains encoded in the stalled ledger region. Nothing is destroyed—commits are just deferred. Slow leakage at the boundary (radiation or tunneling) gradually re-synchronizes stored data with the global ledger.
  • Singularity reinterpreted: Infinite density is an artifact of continuous math. The CBF ledger is discrete, so curvature saturates when cell spacing reaches the local tick precision limit.
  • Recycling mechanism: When load eventually dissipates, stalled commits flush outward, reseeding the surrounding field with synchronized history—potentially forming jets or new star systems.
CBF Resolution: Black holes are not singularities. They are regions where α-field pacing collapses toward zero and commits stall into M-mode storage. The ledger never breaks or erases information; it simply slows its processing until reconciliation can resume.

Dark Matter & Scars

CBF explains dark matter as the residual pruning scars of failed or vetoed collapse paths stored in the D-field.

  • Two-tier structure: The universe tracks events through two ledgers. The S-ledger records stable atomic commits that shape α(x) and gravitational curvature. The D-field stores all failed, vetoed, or incomplete collapse attempts as persistent computational scars.
  • Origin of scars: When overlapping wavefronts or unstable atoms attempt commits that cannot reconcile, their budget drains without a successful event. These failed collapses leave localized distortions in the D-field that bias future commits, even though they carry no mass themselves.
  • Macroscopic effect: Regions with long histories of collapse activity—supernova remnants, galaxy formation zones, or decayed atomic regions—accumulate dense scar networks. The scars act like invisible scaffolding that guides later gravitational pacing, producing halo-like lensing without new matter.
  • Microphysics link: Each scar represents residual hazard written as h(x) ∝ E² × loss(x, ω). In conductive or lossy materials this shows up as absorbed field power; in space it persists as inert dark-matter structure.
  • Persistence: Scars decay slowly because they exist outside normal atomic maintenance cycles. Their cumulative bias explains why galaxies retain massive halos long after their baryonic cores settle.
  • Observation tie-ins: CBF reproduces gravitational-lensing offsets (such as the Bullet Cluster) by weighting each region’s effective gravity by its stability factor η = λ_keep / (λ_keep + λ_fail). Hot plasma contributes weakly (η ≪ 1); long-lived stars dominate (η ≈ 1).
CBF Resolution: Dark matter is the scar tissue of the universe—residual D-field structures left by unresolved or failed commits. They guide future gravitational pacing but add no new mass, giving halos and lensing their shape through history, not substance.

Dark Energy / Expansion

CBF interprets cosmic expansion as slow tick-rate drift between galactic frames, not the stretching of space itself.

  • Global tick drift: Each region of the universe runs on its local pacing field α(x). Over vast distances, tiny calibration offsets accumulate, producing an apparent expansion when comparing remote ledgers.
  • Calendar-leap analogy: The drift acts like a cosmic leap-year correction. Locally, physics remains perfectly synchronized, but between far-separated galaxies the tick alignment drifts, giving redshift patterns that mimic expansion.
  • No space stretching: Space itself does not grow. Photon travel obeys the same hop length and tick duration. The perceived wavelength increase comes from comparing the emitter’s αₑ to the absorber’s αₐ, not from expanding distance.
  • Energy accounting: Because photons conserve their T-budget through propagation, a slower absorbing frame measures a lower frequency without any energy loss in transit. The shift is relational, not dissipative.
  • Cosmic acceleration illusion: Over billions of years, accumulated tick-rate drift makes distant galaxies appear to recede faster, creating the impression of accelerating expansion without new energy input.
  • Dark energy redefined: The so-called dark energy term represents global timing correction across the ledger, ensuring that far-field reconciliations stay self-consistent despite gradual α(x) divergence.
CBF Resolution: Cosmic expansion is not spatial stretching. It is the slow drift of tick pacing between distant frames. Redshift reflects the difference between photon emitter and absorber α-rates, not a loss of energy to expanding space.

CMB and Redshift

CBF explains cosmic redshift as a pacing difference between emitter and absorber frames, not as photons stretched by expanding space.

  • Frame comparison: A photon always propagates with the same hop length and tick rate c = a/τ inside the Event Ledger. Redshift arises when the emitter and absorber run at slightly different α(x) pacing. The photon’s T-budget is constant; only the receiving frame’s clock measures a slower beat.
  • No stretching: Space does not expand between galaxies. The wavelength increase seen by observers comes from comparing two independent frame rates—α_emit and α_absorb—not from stretching wavefronts in transit.
  • Energy conservation: The photon’s internal C = T + M bookkeeping remains exact through propagation. What changes is the tick-rate baseline of the observer, so energy is never lost to empty space.
  • Blackbody precision: Because every photon preserves its phase density, CBF automatically maintains the perfect blackbody curve of the CMB (|μ|, |y| ≲ 10⁻⁵). No frequency-dependent drain is needed; α-rate differences alone account for the uniform redshift.
  • Brightness and distance duality: CBF respects the Tolman relation D_L = (1 + z)² D_A because the same pacing offset that redshifts light also stretches apparent timing intervals in the ledger’s accounting.
  • Redshift drift: As the global α calibration slowly changes, ongoing measurements see the expected secular drift (dz/dt) matching the history of tick-rate divergence, not dynamic metric expansion.
  • CMB origin: The background itself is the frozen statistical residue of ancient large-scale commits—massive early synchronization events whose collective emission remains phase-coherent today.
CBF Resolution: Cosmic redshift is relational, not expansive. Photons never lose energy to stretching space. The CMB’s smooth spectrum, brightness law, and drift behavior all follow from comparing emitter and absorber pacing in the universal ledger.