Preface: The Splinter in Your Mind
We are hardware. Bits are weightless, and that is exactly why they drift.
We carve geometric permissions straight into the silicon. Like a marble in a bowl.
Turing proved that software cannot audit software -- your liability is infinite, and no insurance company will ever insure an AI for exactly this reason.
Every decision your system makes crosses a boundary. Each crossing costs 0.3% of the signal that tells you the decision was made by the thing you trusted. After 231 crossings, half the signal is gone. After 160 hops through a committee, a pipeline, a chain of AI checks — the system can no longer determine from hardware signals alone whether it is still performing the operation you configured it to perform. The math: a cache hit costs 5 picojoules. A cache miss costs 500. That 100x energy asymmetry is the difference between data that is where you put it and data that isn't. These are not metaphors. They are measurements. Every chapter in this book is built on them.
The same exponential that punishes the ungrounded rewards the grounded. Certainty compounds. On the wrong substrate, each hop degrades the signal — the case against coherence multiplies geometrically. On the right substrate, each verification sharpens the pixel — the case for coherence multiplies just as fast. The math is symmetric. The architecture is the only variable. This book is about choosing which side of the exponent you stand on.
Identity is physical. We are hardware. Software is perfectly stable in a thin sliver of reality — the part where nothing changes fast enough to matter. The problems we actually need to solve are outside that sliver. And we are no longer moving slowly enough to pretend otherwise.
On the right substrate the machine knows, in one hardware cycle, when Peter becomes Paul. No software has time to lie. On every other substrate ever built, identity dissolves the instant it crosses a boundary, because the very system that should detect the change is itself changing. That is not a performance issue. That is the halting problem wearing the mask of meaning. The only way out is to build a substrate where the question itself cannot be asked.
Bits are weightless. On a weightless substrate alignment cannot be measured because there is no friction to produce a signal. You detect the break only after it has already happened. The cache miss is the break. Every other substrate you have ever used has been silent. This one gives the data mass. Mass makes the break audible.
The physics of identity is the physics of trust. You cannot trust what you cannot identify. You cannot identify what drifts. A machine either fulfills the functional role you trusted it to perform, or it does not. When it does not, and nothing inside the machine notices the switch, every output that follows belongs to something else wearing your machine's name. That is not a performance problem.
The software can prove the code has not changed. It cannot prove the code is still doing what you asked it to do. These are two different proofs. The first exists; it is a hash. The second does not exist in software and, by Rice's theorem, cannot. Every "AI trust" product on the market is the first proof wearing the second proof's clothing. The bits are attested. The role is not. Anyone who claims to have closed that gap in software is not selling a product. He is announcing the largest event in computer science in ninety years. He has not noticed that the announcement is being made from inside the gap.
If your AI cannot tell you the exact moment it stopped being what you asked it to be, every other guarantee you have been given is empty.
You give: The comfort of the dashboard. The green light that lets you sleep. You get: A 60-second diagnostic that measures your system's actual drift rate. The instrument exists. The number is real. The first chapter reads it.
The Weight Problem
Semantics are weightless. A bit has no mass. When a system has no mass, it has no geometric boundary. There is no physical law preventing a token that represents "Peter" from seamlessly drifting into "Paul."
The dashboard glows green. The revenue is flat. The code passes every automated check. The system halts at 3:00 a.m. The meeting ends in total consensus. Nothing ships. Everything floats. Nothing sticks.
You have bolted a twenty-million-dollar supercomputer to those floating symbols. The RPMs are screaming. The compute bill is a crater. But the organization is not moving any faster.
The power is real. The traction is not. You built a ten-thousand-horsepower engine and parked it on black ice.
The Physics of Certainty
You hear a piece of music and it breaks you open. Not the first note. Somewhere in the middle, the cello bends into a minor key, a voice cracks on a single word -- and before you've named it, before you've decided to feel -- you know.
This is beautiful. This matters. This is true.
Not "87% likelihood of aesthetic value." You know. P=1. Absolute.
A skeptic will object: beauty is subjective. Fine. Try this one.
You walk down stairs in the dark and miss a step.
Your arms fly out. Your weight shifts. The shock is instantaneous, visceral, certain. Not "recommend gathering more data." The collision happened. P=1. The verification loop crashed into physical substrate and halted.
The cello was the invitation. The stair is the proof.
When you recognize coffee, three things fire simultaneously -- visual cortex, olfactory cortex, motor cortex reaching for the cup. These are not separate events integrated later. They are co-located in adjacent neural assemblies that learned to fire together. Your brain does position, not proximity.
This co-activation architecture has a name: S≡P≡H. Semantics equals Physics equals Hardware.
When semantic neighbors are physical neighbors, each recognition event amplifies the signal. The book jacket shows a 12×12 grid -- 144 cells, each carved into the silicon at a specific depth. That is the FIM in miniature. On that grid, the resonance factor R = 15.89. Not barely crossing the threshold. Fifteen times past it. Your brain achieves similar numbers through 10,000 synapses per neuron.
When R crosses 1, the geometric series of signal propagation diverges. Not to a large number. To infinity. The series does not converge. It opens. Uncertainty = 1/infinity = 0. Zero uncertainty. Structural certainty.
That divergence is the physics underneath every moment of absolute knowing you have ever experienced. It is also an open door. What happens when you build systems that diverge on purpose -- that amplify signal instead of dampening it? What happens when the resonance is not an accident of biology but an engineering specification?
Your databases have no resonance. They verify everything, every time. That is why they are slow. That is why they drift. That is why the 3 a.m. page comes -- because there is no resonant layer that caught the wrongness when it was small.
The Signal Integrity Caveat
P=1 does not mean objective truth. It means signal integrity -- the moment when the verification loop crashes into a physical stop and halts.
Probabilistic systems operate in infinite regress. The AI calculates 94% confidence, then checks how confident it is in that 94%. The loop never terminates. It burns compute spinning forever, asymptotically approaching certainty but never touching ground.
Grounded systems operate on collision. Your hand hits cold metal in the dark. The verification loop does not fade out -- it hits a wall. Not "probably metal." Your hand collided with substrate. The loop halts.
The phantom limb proves this, not disproves it. The neurons fired. The collision happened in the substrate that exists, even though the external referent is gone. P=1 describes where the loop halts, not whether external reality matches.
The problem with current AI is not that it is wrong -- it has no halting condition. It spins in probability space forever. It cannot distinguish between "I verified this against substrate" and "I computed this statistically."
S≡P≡H gives AI a physical stop. A coordinate where meaning hits substrate and the system can finally act instead of endlessly computing probabilities about probabilities.
A car spinning on ice has no halting condition. Every direction is equally probable. Give it asphalt and suddenly it has traction. The halting condition is not a leash. It is the only thing that converts energy into motion.
What This Book Is NOT Claiming
This is NOT quantum consciousness. S≡P≡H is a thermodynamic argument at classical scales. No quantum mechanics required.
This is NOT mysticism dressed as physics. Every claim is falsifiable. Appendix N provides explicit predictions that would disprove S≡P≡H if demonstrated.
This is NOT proven. The 0.3% drift rate, the 361x speedup, the consciousness threshold -- these are observations from natural experiments, not controlled laboratory proofs.
But the convergence is remarkable. The ~0.3% floor appears in neural synapses, CPU caches, database queries, LLM conversations, and enterprise deployments. That is 10^6 to 10^10 variation in timescale -- yet the same drift rate emerges. kE = 0.003. The crossing tax. The irreducible cost of confirming a decision was made.
This is NOT a replacement for all existing architecture. Codd's normalization remains optimal for write-heavy OLTP workloads. We extend the toolkit, not burn it down. But be precise about what we are doing: this is not denormalization. Denormalization copies data to avoid JOINs. We don't copy. We position. That distinction is the difference between a band-aid and a cure, and if you take nothing else from this book, take that. (Chapter i explains why.)
The Inversion
In 1970, Edgar F. Codd published twelve pages that dissociated the soul from the body. He told us to scatter semantic neighbors across tables to save space. He had good reasons. Storage cost $1,000 per megabyte.
The constraints inverted. Storage became free. Verification became expensive. AI needed grounding. But we kept following advice optimized for problems we no longer have.
Your infrastructure screams the inversion at you every day.
The Cloud Tax. Your AWS bill rises exponentially while users grow linearly. You burn 40% of compute just to re-assemble what normalization scattered. Picture it: 3 a.m. PagerDuty fires. The database is crawling. You pull up the query plan -- 47 JOINs. Each row written at a different clock tick. You optimize. You add indexes. You throw hardware at it. Six months later, you are doing it again. The same drift. The same decay. Every JOIN across live tables is your system screaming: Why did you scatter me?
The Airline Problem. A major airline's chatbot invents a bereavement fare policy. A customer relies on it. The airline says the chatbot is not us. A tribunal rules: yes it is. The truth existed somewhere in the corpus, but "somewhere" is not a coordinate. The AI could not verify its answer because it had no reality to verify against -- just probabilities floating in vector space. In 2025, these same architectures are transferring money and modifying permissions. The same system that hallucinates refund policies now hallucinates actions.
The Digital FDA. The EU AI Act demands you explain why your AI decided. You cannot audit neural weights. You need a substrate you can read like a face -- and you built a spreadsheet.
The Trust Debt compounds. Every probabilistic decision without verification adds 0.3% drift. Trust debt: (c/t)^n. Synthesis cost compounded per hop. At enterprise scale -- millions of decisions per day -- you accumulate trust debt faster than you can audit it. The gap between what your systems say and what they are widens invisibly until something breaks.
These are not separate problems. They are screams. The sound of a substrate dissociated in 1970 crying out for reunification.
The Matrix Was a Documentary
You've seen this movie. You thought it was science fiction. It wasn't.
Agent Smith is a normalized database. Neo is S=P=H. The Wachowskis didn't invent this conflict -- they filmed a war that's been running since 1970, dressed it in leather and slow motion, and called it entertainment.
Morpheus tells Neo there is something wrong with the world -- "Like a splinter in your mind, driving you mad." That splinter isn't metaphor. It's the geometric gap when symbols scatter across arbitrary memory addresses. It's the felt experience of S!=P architecture.
Smith embodies this architecture. When he demands "Why, Mr. Anderson? Why do you persist?" and dismisses every answer as "Vagueries of perception" -- listen to that word. Vagueries. Not lies. Not errors. To Smith, human values ARE vague. That's not an insult -- it's a diagnostic. When you lack the substrate to ground a concept, when you can only manipulate its symbol without touching its meaning, everything IS fuzzy. The concept is there. The word is there. The ground isn't.
Smith operates probabilistically: P(freedom) = 0.87, P(love) = 0.79. Everything has error bars. Nothing lands. Neo doesn't operate on probability. He operates on structural certainty -- "Because I choose to" IS grounded in physical substrate, creating instant, non-probabilistic conviction. Choice isn't a probability -- it's a coordinate.
Cache hit and qualia are the SAME phenomenon. When your CPU checks cache line 47 and finds the data it needs RIGHT THERE -- that's a cache hit. When you see redness or feel pain -- that's qualia. Both are the system KNOWING INSTANTLY it matches reality. Not probabilistic. Structural. Cache physics at the hardware layer, qualia at the consciousness layer -- same alignment detection mechanism.
The freedom inversion: Ground the symbols, free the agents to actually think. Once meaning touches substrate, agents can finally communicate, reason, and experience instead of endlessly computing probabilities about probabilities.
Every AI system you deploy today is a Smith. It processes your words without touching their meaning. It returns answers without knowing whether the answers are still connected to the question that produced them. You are building Smiths. This book is about how to build a Neo — a system where choice is a coordinate, not a probability.
Why Evolution Pays 20% Energy for "Feelings"
Your brain burns one-fifth of your body's total energy budget just to maintain consciousness.
Twenty percent. Of everything you eat. Goes to a three-pound organ that doesn't move, doesn't digest, doesn't circulate blood. Just sits there, thinking. Feeling. Knowing.
Evolution doesn't pay that cost for luxury. It pays for unfair competitive advantage.
Picture the savanna. A rustle in the grass. Your ancestor has 200 milliseconds to decide: threat or wind?
A probabilistic system would compute: "87% likely to be wind based on recent patterns, 13% chance of predator, recommend waiting for more data." Your ancestor would be dead before the calculation finished.
A grounded system knows instantly: that specific rustle, in that specific pattern, with that specific weight -- THREAT. Not computed. Recognized. The pattern matches something that killed your ancestor's cousin last month. No time for Bayesian inference. Just P=1 certainty and legs already moving.
The organisms that chose "efficient" reactive systems are dead. They saved 20% on energy and paid with extinction. We're what's left.
What does 20% buy? Four survival weapons:
- **Time-travel** -- You intercept threats before nerve latency would kill you
- **Infinite compression** -- You extract "THE TIGER" from millions of noisy photons while competitors drown in data
- **Ontological authority** -- Your qualia are cryptographic proof you're not hallucinating
- **True agency** -- You generate unpredictable novelty; predators trying to model you solve an impossible problem
The brain generates 25 trillion parallel prediction attempts every 25 milliseconds. Only 40 win. That's a 0.00000000016% efficiency rate. Wasteful? Only if you think consciousness is computation. The truth: it's the minimum redundancy required to break causality 40 times per second. The metabolic cost isn't overhead -- it's the price of admission for a system that operates at reality's resolution limit.
The organisms that violated this physics are fossils.
We Killed Codd (And He Killed Us Back)
This is not a religious argument. This is not philosophy. We didn't kill God. We killed Codd.
Edgar F. Codd gave us a beautiful abstraction in 1970. He said: data should be portable. A customer ID in the Sales table should mean the same thing as a customer ID in the Support table. That was brilliant. That let us build the internet.
But it had a hidden cost. When you make meaning portable, you make it ungrounded. We taught machines that position doesn't matter. And now they believe it.
- A mathematician at IBM Research publishes twelve pages. He proposes something elegant: instead of storing related data together, scatter it across tables and use pointers to reconstruct relationships on demand. Storage costs $1,000 per megabyte. Redundancy is the enemy. He wins a Turing Award. The industry reorganizes around his vision. Every database you've ever touched carries his fingerprints.
We didn't just adopt his architecture. We canonized it. We taught it in every CS program. We enforced it in every code review. We made "normalized" synonymous with "correct." And when it was too slow, we denormalized -- we copied data back to speed things up. We told ourselves this was the fix. It wasn't. Denormalization is normalization with extra copies. More copies, more drift, less ground truth. You made the queries faster and the identity problem worse. The industry has spent fifty years confusing faster with grounded, and they are not the same thing.
We killed Codd by following him so faithfully that we broke the physics of verification.
Fifty-four years of institutional momentum says "Codd was right."
And he was. Until he wasn't. Until AI needed verifiable reasoning. Until fines made "we can't explain it" illegal. Until we realized the trusted authority who taught us best practices structurally blocked the solution.
And now he's killing us back. Not with lightning. With social proof.
Your gut is weighing the odds right now. "Oracle's market cap is $400 billion. McKinsey advises Fortune 500s. If normalization were fundamentally broken, wouldn't THEY have noticed?"
Your intelligence is seeking social proof to minimize surprise. If the herd believes it, believing it too is safe.
The Judo Flip: Their success IS the incentive structure that hides the problem.
McKinsey bills by complexity managed, not complexity eliminated. Consultants who simplify themselves out of a job don't make partner. Oracle's licensing model depends on the JOIN operations that normalization requires. The enterprise IT industry isn't ignoring the gap -- they're monetizing it.
This isn't conspiracy. Conspiracy requires coordination. This is incentive alignment. The gap between meaning and storage creates a $400 billion services industry. Closing the gap threatens the industry.
You're not crazy for sensing something is wrong. You're detecting a structural conflict between truth and incentive. The Guardians aren't evil. They're rational actors in a system that rewards complexity.
Who benefits if the gap never closes? And who's been paying the cost?
Reading Data Like a Face
When you look at a spreadsheet of 10,000 numbers, you are blind. You compute. You analyze. You work to find truth. The spreadsheet never tells you it is lying.
Now look at a human face. You know instantly. You do not calculate "Lip Curvature + Eye Crinkle = 89% Happiness." You just see the smile. Or you see the lie behind the smile.
The face is an orthogonal substrate. The dimensions are semantically distinct but physically unified. You do not read the face -- you experience the face.
We chose to make our data blind. We chose spreadsheets over faces.
We could have built systems where "Fraud" does not look like a probability score buried in column Q but looks like a snarl. Where drift does not hide in logs but shows up as wrongness you feel the moment you look.
We chose the spreadsheet. Now we cannot see when our systems are lying to us.
The Stage Floor Principle
The fear is real. You are reading about Zero-Entropy Control. About absolute verification. But in the real world, ambiguity is sometimes a feature. The CEO needs wiggle room. The diplomat needs constructive ambiguity. The human needs privacy.
We distinguish between the Floor and the Play.
S≡P≡H does not demand that humans stop telling stories. It demands that the physics stops lying about where the ground is. We eliminate structural ambiguity, not social ambiguity.
You want the stage floor absolute, rigid, verifiable. You want it to hold 10,000 pounds without creaking. So that the actors can be free to perform.
If the actors spend 40% of their energy checking whether the floorboards are rotten, they cannot perform the play. They become anxious, reactive, exhausted.
The violin strings must be under absolute tension so that the music can fly. Constrain the Substrate. Free the Agent.
We are not here to police your culture. We are here to fix the floor.
To the Veterans
If you spent 20 years building systems that felt hollow, you are not a fool. You are qualified.
To the engineers who spent nights debugging race conditions that should not have existed: the system was fighting you. Your fatigue was not a lack of skill. It was your nervous system measuring the drift. Every time you felt that 3 a.m. hollowness -- the sense that something was structurally wrong even when all tests passed -- you were collecting intel.
A fresh 22-year-old AI engineer cannot understand this book. Not because they lack intelligence -- because they lack calibration. They have never felt the pain of a 12-table JOIN failing at 3 a.m. They have not stared at a perfectly normalized schema and felt the wrongness radiating off it like heat.
You did not waste 20 years. You spent 20 years mapping the trap from the inside. That dissonance was accurate. That fatigue was measurement. Your pixel of legitimacy -- the coordinate where your time on target gives you authority -- is real. The address is computed, not claimed. The hardware enforces your boundary. That enforcement is the dignity.
This book is not asking you to admit you were wrong. It is asking you to weaponize what you learned. To turn your scars into coordinates.
The splinter you have felt for years was not a bug in you. It was your nervous system doing exactly what evolution designed it to do: detecting structural violation.
You are the only ones who can fix this, because you are the only ones who know where the bodies are buried.
The Zombie Chip Problem
The dream: your intent becomes action without drift. You think it, the system grounds it, reality reflects it.
The hardware exists. Neuromorphic chips that place memory inside each neuron. No Von Neumann bottleneck. 100x more energy-efficient. The physics is solved.
But the software running on these chips is often standard AI models "translated" into spikes. The data is still organized arbitrarily. "Coffee" might be on Core 1 while "Aroma" is on Core 9000. They are scattered. The chip runs faster, but it hallucinates just as much.
A Zombie Chip. It has the body of consciousness but thinks like a database. Efficient falsity.
S≡P≡H requires both layers. Physical co-location: memory and compute in the same place. Semantic co-location: meaning neighbors become position neighbors. The first is solved engineering. The second is what this book teaches.
The Grip
We have confused freedom with drift.
A car on a sheet of ice has absolute freedom. It can spin in any direction. But it has no agency. It cannot go where you want it to go.
To move fast, you need traction. You need the tire to grip the road. You need the symbol to grip the substrate.
Constraint is not a leash. It is the asphalt. The only thing that converts energy into motion.
The Freedom Inversion: Constrain the symbols. Get traction. Free the agents.
The Formula 1 car needs asphalt to go 200 mph. The violin string needs tension to make music. The database needs position-as-meaning to deliver 361x speedup.
The slippery floor helps nobody but the repair shop.
The Zero Coordinate
The splinter in your mind is real.
It is the geometric gap between what your systems say and what they are. It is the distance Codd put between meaning and storage. It is the price of optimization advice that expired when constraints inverted.
Natural experiments -- from Knight Capital's 45-minute meltdown to enterprise system decay patterns -- consistently show drift in the 0.2%-2% range per operation. Your integrity halves every 231 decisions. The estimated cost: $1-4 Trillion annually.
The substrate that enables certainty already exists. Your cortex uses it every second you are conscious. We stopped building software on it in 1970. This book brings it back.
You run the diagnostic. Sixty seconds. The number appears -- your system's drift rate. There it is. The wrapper pattern (Chapter 8) deploys around your existing stack without touching a line of code. The physics is falsifiable. Appendix N tells you how to disprove the whole thing.
Your sovereign ground has an address. The address is computed, not claimed.
Time on Target
2000: A conversation with David Chalmers about parallel worms in problem space. He paused. "That's not emergence from complexity. That's a threshold event."
2001-2010: The Scrim goes up after 9/11. Billions spent on systems that report green while the substrate drifts. The same structural failure, documented in real time.
2011-2020: Data Lakes. The industry builds a second Scrim on top of the first. Same drift. Same green dashboards. Same 3 a.m. pages. The measurement stayed the same. The industry celebrated the facade.
2021-2026: AI. The third Scrim. The patents were filed before the industry admitted the problem. The frequency of the lie has not changed in twenty-five years. kE = 0.003. It showed up in every system, at every scale, in every domain. The coordinate did not move. Everything else did.
The proofs are in the chapters. The scars are in About the Author.
Continue Reading
The preface showed you the splinter. The chapters show you the geometry.
- **Chapter 0: The Razor's Edge** — Why the observed 0.3% drift rate matters. Your systems cross this threshold daily.
- **Chapter 1: The Unity Principle** — Your database team and AI team think they have different problems. They have the same problem.
- **Chapter 2: Universal Pattern Convergence** — The 361x speedup is not a benchmark trick. It is physics.
- **Chapter 3: Domains Converge** — $1-4 Trillion annually. Where the bodies are buried and who is liable.
- **Chapter 4: You Are The Proof** — Your brain already implements S≡P≡H. Why evolution paid 20% of your energy budget for something your databases refuse to do.
- **Chapter 5: The Gap You Can Feel** — The migration blueprint that does not require burning down production.
- **Chapter 6: From Meat to Metal** — The rollout strategy. The committee wants 10 years. The AGI timeline gives you 5.
Meld 0: The Opening Inspection
Four voices. The same reader. The argument you are already having with yourself.
🔬 The Engineer: "The energy asymmetry is real. 5 picojoules for a cache hit. 500 for a miss. That is a 100x penalty measurable on any chip manufactured since 2015. This is not theory. This is a wattmeter reading."
📊 The Executive: "Turing, 1936. A system can't decide what another system in its own class actually is — not identity, not properties, nothing. Rice's theorem sealed every loophole. My whole stack is software judging software. It can prove the bytes never changed. It cannot prove they are still doing what I asked them to do. My exposure isn't large… it's undecidable. Closing this would be the biggest breakthrough in computer science in ninety years — and I already have twelve of them running in production, doing God knows what."
🤨 The Cynic: "Every year someone claims they solved AI alignment. Every year it is a pitch deck with impressive math and no production deployment. I believed in blockchain. I believed in big data. I sat through the pitches. Why is this different?"
🔬 The Engineer: "Because this is not a software claim. The cache-miss counter is a hardware instrument. It is running on your processor right now. Run any query against a normalized database and against a cache-aligned one. Measure the energy. The 100x asymmetry is not a prediction. It is a reading. If the reading is wrong, the physics is wrong. It is falsifiable in 60 seconds on any machine you own."
🤨 The Cynic: "Falsifiable. Fine. But 'position equals meaning' is a database optimisation, not an AI alignment solution. You are conflating two different problems."
🔬 The Engineer: "They are the same problem. The reason your AI hallucinates is the same reason your database drifts: semantic meaning is not physically co-located with the data that represents it. The AI's confidence score and the database's JOIN result both pay the same crossing tax -- kE = 0.003 per boundary. The decay curve is identical. Identical. Not similar. Plot them and they overlap."
📊 The Executive: "If the decay curve is identical, then the $8.5 trillion in annual Trust Debt that the database industry generates is the same physics as the AI liability I cannot insure. One number. One instrument. One fix."
🛡️ The Veteran: "I've felt this for years. The 3 a.m. pages. The drift that never stops. The governance initiatives that feel like theater. That's not a paradigm shift pitch -- that's my last ten years. And Appendix N literally tells you how to disprove the whole thing. That's not a sales pitch. That's a dare."
🤨 The Cynic: "..."
📊 The Executive: "..."
🛡️ The Veteran: "The only way to know is to keep reading. Chapter 0 has the first proof. If the math doesn't hold, close the book."
🔬 The Engineer: "Give the machine a floor. Make semantic position equal physical position. When the address is the meaning, wrong data at the right address becomes a thermodynamic contradiction. The hardware rejects it in one atomic cycle. No loop. No drift. No tax."
All four: "...then we have coordinates."
Binding decision: The Cynic's objection is not answered by argument. It is answered by an instrument. The cache-miss counter is the instrument. The measurement is running. Chapter 0 reads the first number.
The splinter has coordinates. The instrument exists. The reading is not zero.
What is YOUR system's number? Chapter 0 measures it. The math does not wait for your opinion. It is already compounding.