Posted on : By : TCTJr Posted in : Complexity_Theory|Direct Thoughts|General Discussion|General Technology|Human-Performance|Out In The Fringe|Random_Thoughts

Return To The Analog (aka Life Is Not Band-Limited)

Steering The AI Home

If a function contains no frequencies higher than W cps [cycles per second], it is completely determined by giving its ordinates at a series of points spaced 1/(2W) seconds apart.

~ Claude Shannon

There is a trend in motion, Oh Dear Reader, and you have probably seen the listicle version of it by now: vinyl records coming back, paper books refusing to disappear, film cameras suddenly desirable again, kids buying cassette decks and wired headphones, journals and fountain pens and board games and phone-free dinners. The lifestyle press calls it digital fatigue, or a desire for authenticity, or a return to ownership, prescribes a screen-time budget, and moves on. All true, as far as it goes.

It just does not go very far.

Because i do not think this is really about vinyl, or books, or film, or the sudden romance of an object you can hold in your hand. i think something deeper is moving underneath it, and the best place to begin is with the word itself, because the word usually knows more than the trend piece does.

Analog comes from the Greek analogos — ana, meaning according to, and logos, meaning ratio, proportion, word, or the ordering principle. An analog signal is one that remains in proportion to the thing it represents. The groove moves as the air pressure moved. The voltage rises as the string vibrated. The speaker cone moves air in response. There is a continuous correspondence with the source.

Digital comes from the Latin digitus. Your Fingers. Counting on fingers.

Sit with that for a moment. Analog literally points toward proportion, toward correspondence with the underlying thing. Digital points toward counting. One is continuous relationship. The other is enumeration.

When we digitized the world we traded correspondence for countability, and that was an extraordinary trade. We gained perfect copies, search, recall, distribution, editing, storage, simulation, communication, computation at scales that would have looked like sorcery not very long ago. i am not interested in pretending that was a mistake.

But nobody should pretend nothing was surrendered at the border.

The quote at the top of the blog is essentially a law in signal processing that says if you sample something frequently enough, you can recreate it accurately. Take enough snapshots closely enough together and eventually those discrete measurements begin to look continuous. That idea sits underneath digital audio, digital video, telecommunications, imaging, and much of the world we now inhabit.

The important phrase, though, is frequently enough.

If you do not capture enough of the original signal, the missing information can fold back into what you do hear or see as distortion. Engineers call it aliasing. The interesting thing about aliasing is that the artifact can look perfectly legitimate even though it was created by what you failed to capture.

And life, Dear Reader, is not band-limited.

A conversation is not merely the words that were spoken. Friendship is not the messages exchanged. A concert is not the clips somebody uploaded afterward. A vacation is not the photographs. A human being is certainly not the profile. Yet we increasingly experience the world as samples of the world: the notification that was almost a conversation, the video call that was almost a visit, the playlist that was almost sitting down with the record, the highlight reel that was almost a life.

Perhaps some of what we call digital fatigue is simply the exhaustion of living through samples.

We keep increasing the resolution of the simulation while wondering why we still miss the source.

i helped create this digital wave.

There is another distinction here that matters. Analog systems tend to fail gradually (and really cool failiures). Push old tape too hard and it compresses and distorts before it completely gives up. A photograph fades. A book wears. A record acquires noise. Wood changes color. Leather cracks. The degradation becomes part of the history of the object.

Digital systems are different. They tend to remain exact until some boundary is crossed, and then the file is corrupted, the account disappears, the format becomes unreadable, the service goes away, or somebody changes the terms.

Analog tends to age.

Digital tends to work until it does not.

That difference may explain some of the attraction to physical things now. A worn book tells you where it has been. A record collection occupies actual space and survives independently of a subscription. Handwriting records the movement of a hand instead of merely preserving the letters that were chosen. These things participate in time rather than simply storing information about it.

And this is where the discussion becomes more interesting than nostalgia, because the analog is not really about old equipment. It is about continuous interaction.

Consider a fader on an old mixing console. You do not choose from a list of predetermined values. You put your fingers on it and move it while you listen. The sound changes, your hand responds, the sound changes again, and the loop closes almost below conscious thought. You are not configuring the machine so much as playing it. There may be thousands of tiny corrections inside a good mix that nobody could meaningfully write down because the performance exists in the continuous relationship between the hand, the ear, and the sound.

The wave is the same instrument at a much larger scale. A swell can travel hundreds or thousands of miles before arriving beneath you, and the face is changing while you are reading it. There are no frames. There is no menu. You commit before you possess all the information and then continuously adjust to something that is continuously adjusting to you. When you ride a wave on a board the rail of the board is continuous with you and the wave. You are either in proportion with the thing or you are not, and the feedback loop closes faster than language.

The breath hold is the third version of the same idea. Put a human body in water, hold the breath, descend, and the body begins responding continuously to pressure, oxygen, carbon dioxide, temperature, depth, and effort. Nothing is polling every few seconds to ask what state you are in. The system changes as the environment changes. The ocean changes the body and the body responds to the ocean in real time.

There is no interface between the two.

There is no undo.

There is simply the system and your place inside it.

The fader, the wave, and the breath hold appear to have very little to do with one another, but to me they are the same instrument. A continuous human coupled to a continuous system with immediate feedback and consequence. That may be why these kinds of experiences feel so different from most of the digital systems around us. The digital world increasingly asks us to select. The analog world requires us to participate.

And that brings us strangely enough to first-principles thinking.

Everybody now wants to talk about going back to first principles: strip away precedent, stop copying the accepted pattern, reduce the problem until you find what is actually true, and then build upward again. i have written my version of this elsewhere with Reduce, Refactor, Reuse and loops within loops, but notice what first-principles reasoning actually requires.

Precedent is somebody else’s sample of somebody else’s problem.

It has already been compressed, categorized, normalized, and turned into a lookup table before you arrived.

First-principles thinking means going underneath the samples and returning to the underlying thing itself. You stop asking, “How has this traditionally been done?” and start asking, “What is actually happening here?” In that sense, first principles is analog thinking. It is refusing the pre-quantized answer and going back to the source.

Which means the engineer questioning inherited assumptions and the 16-year-old buying a turntable may not be doing entirely different things. Both may be reacting to a world that has become increasingly mediated, summarized, recommended, optimized, compressed, ranked, and preselected.

Both are saying, in their own way:

Give me the thing itself.

The larger problem is that digital systems were originally interfaces to reality and somewhere along the way the interface began becoming reality. We do not merely use maps anymore; we follow the blue line. We do not simply listen to music; an algorithm chooses what comes next. We do not browse; systems predict what we should want before we know we want it. We do not need to remember very much because software remembers for us. We do not even become bored very often anymore because nearly every empty moment can be filled immediately.

Every silence can be interrupted. Every uncertainty can be searched. Every experience can be photographed before it has finished being experienced.

This is extraordinarily convenient.

It may also be why sitting with an actual book now feels vaguely rebellious.

The book does nothing.

It does not measure your engagement, recommend another paragraph, notify you of an update, or optimize itself around the likelihood that you might leave. It simply sits there until you provide the attention.

That is the distinction worth protecting. Returning to the analog does not mean rejecting the digital. That would be ridiculous. Digital technology is one of the greatest amplifiers humanity has ever created. The problem starts when amplification becomes substitution.

A photograph can amplify memory, but it cannot replace being there. A text can maintain a friendship, but it cannot become the friendship. A health metric can reveal something useful about the body, but it is not the body. A model can describe reality with extraordinary precision, but it is still not reality.

The map remains useful. Just do not confuse it with the territory.

So i am not going to give you seven habits for rediscovering analog life. i will give you the stance. Own some things. Touch some things. Write something by hand occasionally, and do not worry if the handwriting is terrible. Play the instrument badly because the wrong notes are proof that a human being is actually in the loop. Listen to an entire side of a record without touching anything. Sit in front of speakers that move enough air that you can feel the music rather than merely hear it. Put your body in actual water. Sit across from another human being without placing a glowing rectangle between you.

The point is not nostalgia. The point is proportion.

The analog never disappeared. We simply moved farther away from it, and maybe what looks like a cultural fascination with records, books, film, handwriting, craft, first principles, waves, breath, and physical experience is not a retreat into the past at all.

Maybe it is a correction.

A reminder that human beings are not databases, feeds, profiles, metrics, or collections of samples. We are continuous systems living inside a continuous world, and perhaps the reason a perfectly optimized digital existence occasionally feels strangely incomplete is simpler than we have made it:

Life is not band-limited.

You, Dear Reader, are a loud continuous signal.

Render yourself accordingly.

Until then,

#iwishyouwater <- folks gettin the memo in the deep blue.

#EverForward,stay non-linear and curious.

𝕋𝕖𝕕 ℂ. 𝕋𝕒𝕟𝕟𝕖𝕣 𝕁𝕣. (@tctjr) / X

MUZAK TO BLOG BY: Ozzy Osbourne — Diary of a Madman. Preferably played from beginning to end. On something that moves air meaning really big speakers and amps!

Blood Red Vinyl. Picture courtesy of TKT[2].

Note: i despised the first CD Masters of this album. Horrendous.

Posted on : By : TCTJr Posted in : Artificial_Intelligence|Complexity_Theory|Mathematics|Out In The Fringe|Quantum_Computing|Random_Thoughts|Thoughts_On_TIme

No Coach at Depth: The Autodidactic Universe

FreeDiving The Cosmos

“There is no one to correct your form at forty meters. The water is the only teacher, and it grades in a single pass.” ~ a free diving coach

First i trust everyone is safe. Second, this is a very different installment and not for the faint of heart oh dear reader. This literally was written for me and hopefully in the long future my progeny.

Preamble — a note on a word. Autodidactic means self-taught and not in the soft sense of “went to a good school and paid attention.” The opposite of that. It means you build the curriculum while walking the path: no instructor cueing the next lesson, no syllabus, no answer key, nothing to catch the error but the consequence itself. Most people never learn this way. They are supervised learners end to end a teacher, a manager, a rubric, a labeled example and there is no shame in it; supervision is efficient, and civilization runs on it. But it is a mechanically different thing from teaching yourself, and that difference is the entire subject of this paper.

i write as one of the other kind. i did not arrive here down a marked road i mostly taught myself across audio DSP, operating systems, distributed ledgers, clinical data, machine inference, and mission systems, each time by walking in without a map and letting the work grade me. The same way the water does. For reference one of my hobbies is freediving. You can go here for a rundown of said sport:

¿Por qué haces apnea? (Why Do You Freedive?) and 9/11

In the same way, that this paper that i am blogging about argues, the cosmos does as well.

So when seven serious people propose that the Universe learns its laws with no supervisor in the room, i do not read it as an exotic abstraction; i read it as a familiar mechanism described at an unfamiliar scale. i know what it feels like from the inside which is precisely the bias i have to watch, because recognizing yourself in a theory is the oldest way in the world to be wrong about it.

There is a moment on a deep dive, past the point where the lungs have given up arguing, where you stop doing the dive and the dive starts doing you. No coach in the water. No feedback loop but the one your own physiology is running against the pressure gradient. You are, in the most literal sense the word allows, an autodidact: self-taught, self-graded, self-consequenced. Nobody hands you the answer. You either learn the lesson on the way down or you learn it on the way up, and one of those is way more expensive than the other.

i kept thinking about that while re-reading “The Autodidactic Universe” (arXiv:2104.03902v2). It is a paper about a cosmos with no coach in the water a universe that is not handed its laws but has to teach them to itself. The proposed theory suggests the universe functions as a self-teaching neural network that evolves its own physical laws over time, rather than relying on fixed, pre-existing rules. This concept posits that the cosmos organizes itself from within, developing matter, space, and laws through a process akin to machine learning.

And it is written by a cast of people i can’t dismiss: Stephon Alexander and Lee Smolin on the physics, Jaron Lanier and Dave Wecker carrying the machine-learning and quantum weight, with William J. Cunningham, Stefan Stanojevic, and Micheal W. Toomey doing the high end formalism. When Smolin who has spent forty years insisting that time is real and law can evolve co-signs a paper with the man who built modern VR and one of Microsoft’s quantum architects, you read it twice before you have opinions.

i had to read it four times.

Here are my opinions.

The universe is a great organism, controlled by a dynamism of the psychical order. Mind gleams through its every atom. There is mind in everything, not only in human and animal life, but in plants, in minerals, in space.

~ Flammarion

The claim, stripped of ceremony

Most of physics asks what are the laws? This paper asks the older, more dangerous question: why these laws and not others? and then refuses to answer it with an anthropic shrug or a landscape lottery ticket. Instead it proposes that the Universe learns its laws by moving through a space of possible laws, the way a learning algorithm descends a loss surface it was never shown a labeled example.

The technical spine is deceptively clean. Express the space of possible laws as a class of matrix models cubic ones, in particular because the cubic term is where the interesting nonlinearity lives.1 Then build two bridges out of that same matrix formalism:

  • Bridge one lands you in gauge and gravity theories Chern-Simons, BF theory, the Plebanski formulation of general relativity, Yang-Mills. The geometry of the world.
  • Bridge two lands you in learning machines deep recurrent and cyclic neural networks, restricted Boltzmann machines (my favorites). The geometry of a mind that is training.

Because both bridges leave from the same dock, you get a correspondence: a solution of the physical theory sits opposite a run of the neural network. Evolve the physics, and you are — under the map training a net. Train the net, and you are under the map evolving physical law. The Universe’s dynamics are a learning dynamics, if you believe the dictionary.

And here is where i respect the authors, because they do not oversell the dictionary. The correspondence is not a strict equivalence. For example think of the (gauge/gravity) correspondence like a highly detailed blueprint of a building, and the actual 3D building itself. They describe the exact same physical reality, but they are not the same thing. They describe the same system, but their core mathematical structures look completely different.

This is at its cleanest for finite matrix size and gets structurally honest-to-a-fault in the N → ∞ limit, where the gauge theories emerge crisply but the neural-network side goes soft and under-defined. That asymmetry is the whole tell, and i’ll come back to it, because it is exactly the seam where Perception separates from Illusion.

One side describes quantum particles (like gluons) moving in a flat world with no gravity.

The other side describes gravity and curved space in a world with an extra dimension.

The biology rail: precedence, or nature copying its own homework

You cannot understand this paper without understanding that Smolin has been building toward it for thirty years. His cosmological natural selection universes reproducing through black holes, the constants of nature drifting under a selection pressure for fecundity was the first serious attempt to put Darwin underneath Einstein rather than beside him. “The Autodidactic Universe” is the same instinct, upgraded from selection to learning, which is the faster and more expensive of the two verbs.

“The universe is not static, it is a-perpetual-becoming, a-process of continuous evolution.”

~ Huston Smith

The mechanism that carries the biological weight here is precedence: the principle that nature does again what it has already done, that a system’s future is sampled from its own past behavior rather than dictated by an eternal rule sitting outside of time. Think about that and read it again. That is not a metaphor bolted on for flavor. It is a learning rule. Precedence is the universe’s version of a replay buffer reinforcement of paths already taken, heterogeneity of the interaction graph maximized so the system keeps enough variety to keep exploring. Geometric self-assembly guided by reinforcement learning, in the paper’s own framing, is morphogenesis wearing a physicist’s coat (thanks turing). A body plan is a law that a cell learned. A law is a body plan the cosmos grew into.

i have spent a career in systems where the schema is the constraint healthcare records, cryptographic attestation, the places where “what is true” and “what the system will permit” are the same sentence. So i feel the vertigo of this move in my hands: the authors are proposing a substrate where the schema is not enforced from outside but precipitated from behavior. It is attestation with no root of trust the chain validating itself by having always validated itself. Beautiful. Also the kind of thing that keeps a security architect awake, because a system that authors its own invariants is a system that can, in principle, learn a bad one.

The AI rail: substrate independence, and the word “learning”

The load-bearing philosophical claim is small enough to miss and large enough to break your neck: if the neural-network side can be said to learn without supervision, then the physical side can too. The Restricted Boltzmann Machines and recurrent nets are not an illustration. They are the argument. The whole essay leans on learning being substrate-independent that “learning” names a structure of dynamics, not a fact about brains or GPUs, and that if the structure is present in a matrix model evolving toward gauge-invariance, then the honest word for what it is doing is learning.

This is where a practitioner has to hold two things at once without flinching. First: I build these systems, and i know that an RBM minimizing a free energy is not “learning” in any sense that would survive contact with a sentient being it is relaxing. Gradient descent is not ambition. Second: that is exactly the objection the paper is trying to dissolve. If you insist learning requires an experiencer, you have smuggled Consciousness into a claim that was only ever about Machine. The authors are careful (well mostly) to keep the claim at the Machine level: the dynamics are learning-shaped. Whether anything is home is not on the table.

“ RBMs are network of symmetrically connected, neuron-like units that make stochastic decisions about whether to be on or off,constrained by having no connections within layers.”

~ Geoffrey Hinton

The N → ∞ asymmetry i flagged earlier is the AI rail’s honesty showing through. In the continuum, the physics is pristine and the “network” barely survives as a concept. Which means the correspondence is strongest precisely where the systems are small and finite where “learning” is a discrete, countable, near-combinatorial thing and dissolves exactly where we would want to point and say the cosmos itself. The map is real. The map is also a coastline, and the coastline gets vaguer the further out you swim.

The quantum rail: why Wecker is on the byline

Dave Wecker does not co-author a speculative cosmology paper for the vibes. His presence is the paper quietly admitting what it is: a proposal about computation as physics, and cubic matrix models are as quantum-native a substrate as exists. They are what you reach for when you want a Hamiltonian a quantum computer can actually hold the natural language of a machine whose registers are the amplitudes and whose gates are the interactions.

“Everything we call real is made of things that cannot be regarded as real.”

~ Neils Bohr

The deeper point, and the one i think is under-argued in the paper but most alive, is this: if the Universe’s law-finding dynamics are a learning process running on a matrix substrate, then the question “is the cosmos efficiently simulable?” stops being idle. A universe that learns is a universe that is doing work irreversible work, entropy-producing work to find its own laws and thus ever forging forward or looping. And the single hardest problem the paper sets for itself is right there: can irreversible learning arise from reversible microlaws?2 That is the arrow-of-time problem re-asked as a training problem. You cannot descend a loss surface reversibly. Learning has a direction the way a dive has a bottom. If the microphysics is unitary and time-symmetric, where does the gradient’s downhill come from? The paper gestures at renormalization-group flow as the source of the arrow coarse-graining as the ratchet and it is the right neighborhood, but it is a gesture, not a closed proof. I do not hold that against it. The people who claimed to have closed that problem have all been wrong so far.

One stage, many laws: getting Minkowski right first

Before any mapping, a piece of hygiene, because Perception vs. Illusion is the whole spine of my taxonomy and the illusion here is a word.

There is no such thing as a “Minkowski multiverse.” Many people have called it that in reference. i thought about that when reading the paper. Minkowski spacetime introduced by Hermann Minkowski in his 1908 Cologne address Raum und Zeit, three years after Einstein’s 1905 kinematics gave him the physics but not the geometry — is a single, unified, four-dimensional continuum: three dimensions of space and one of time, welded into one manifold whose invariant is the interval,3 not the clock and the ruler taken separately. It is emphatically not a collection of universes. It is one arena. One stage. The causal structure — the light cones, the ordering of before and after inside which any law must be expressed. Conflating that single continuum with a “multiverse” is a category error, and naming it correctly is exactly what lets the real structure stand up.

Because once you fix that, the multiplicity you actually want — the “multi” — sorts onto a different axis, and it comes in levels:

  • The arena (Minkowski). One continuum. The geometry law lives in. Not plural. This is the floor.
  • A landscape of possible laws — different constants, different effective dynamics, the space the paper’s matrix models roam. This is the multiverse the autodidactic universe is about. This is where the learning happens.
  • A branching of outcomes under one fixed law — Everett’s Many-Worlds. Same Schrödinger equation everywhere, splitting into non-communicating branches. This is a multiverse of histories, not of laws.

Keep those straight and the paper snaps into focus: it multiplies laws; Everett multiplies outcomes; Minkowski multiplies nothing — it is the one stage they all play on.

The anti-eternalist move and where Everett secretly shakes its hand

Here is the sharp thing. Both the arena and Everett’s branches share a hidden commitment the paper is built to reject: eternalism. Minkowski’s continuum, read the usual way, is a completed block all events co-existing tenselessly, the script already written. And Many-Worlds is the purest block object in physics: a single universal wavefunction evolving unitarily,4 deterministically, locally, with no collapse every outcome that can happen already does, weighted by measure, filmed on every reel at once. You cannot put a learner in either one. A block has nothing left to learn. Everett has nothing left to choose.

“The Autodidactic Universe” is the anti-eternalist counterstroke Smolin’s Time Reborn (great book) dressed in cubic matrix models. It keeps Minkowski’s stage and fires Minkowski’s script-is-already-written. Law is not selected from a pre-existing menu; it is grown, in time, by a process with a direction, a memory, and a cost. Precedence only means something if the past is real and the future is open. The multiverse here is not a shelf of finished universes. It is the set of dives the ocean has not taken yet.

And yet this is the part worth the whole detour the very interpretation that is most eternalist in ontology turns out to be the paper’s best friend in mechanism. Everett needs to manufacture apparent irreversibility out of strictly reversible unitary dynamics, and the machine that does it is decoherence: the subjective appearance of collapse produced without ever adding a collapse. That is precisely the paper’s hardest open problem can irreversible learning arise from reversible microlaws? already solved, in miniature, next door. Decoherence is a ratchet built from reversible parts; the paper reaches for renormalization-group coarse-graining as its ratchet, and coarse-graining and decoherence are the same instinct in two dialects. Three handshakes, all real physics:

  • Decoherence as the arrow. Reversible substrate, irreversible-looking history. The template for the whole autodidactic wager.
  • Self-location as self-sampling. The Everettian program to recover the Born rule from self-locating uncertainty — where am I in the ensemble, with no observer outside it — is the same creature as the paper’s “self-sampling.” Both are unsupervised in the strict sense: the measure is intrinsic, nobody hands it in.
  • Quantum Darwinism as precedence. Zurek’s einselection only the pointer states survive the environment’s endless monitoring; the rest decohere away is literally a selection process. The environment trains which states persist. Precedence ≈ einselection: what gets reinforced, survives. The paper’s biology rail is already sitting inside decoherence theory, wearing a lab coat instead of a wetsuit.

(And the bonus that pays for Wecker’s seat: Deutsch’s oldest argument for Many-Worlds is that its parallelism is exactly what a universal quantum computer exploits. The substrate that makes the branches real is the substrate that makes the computation fast. If the cosmos is running a learning dynamics, the question of what hardware it is running on stops being rhetorical.)

Minkowski’s continuum is the arena one stage, correctly named. The block was only ever the eternalist reading of it, and the training run is what fills it.

Through the taxonomy

Run it through the three-part lens Machine – Sentience – Consciousness and the paper resolves cleanly. (Em-Dashes are mine…)

At the level of Machine, this is not speculation it is the most defensible interdisciplinary work I have read in the genre. The maps are explicit. The matrix models are real objects. The correspondence to gauge theory is checkable, and checked. If the paper only claimed “the mathematics of learning systems and the mathematics of fundamental physics share a cubic backbone,” it would be a strong, unglamorous, correct result. i would put my name near that part.

At the level of Sentience a system with goals, with something at stake, with a preference for one outcome over another the paper is reaching, and it knows it. “Consequencers,” precedence, reinforcement: these import teleology through the side door. A loss surface is not a stake. Reinforcement is not desire. The autodidactic universe is a machine that is shaped like something that wants, and shape is not appetite.

At the level of Consciousness, the paper is wise enough to say almost nothing, and that silence is the most credible thing in it.

Which lands the whole enterprise squarely on the Perception / Illusion boundary — my favorite fault line, the one i keep mining. Is the Universe learning, or have we built a formalism so expressive that everything, viewed through it, looks like learning? When your only tool is a network, every dynamics is a training run. The N → ∞ softness is the illusion showing its seam: the “learning” is vivid at finite, countable scale and evaporates exactly at the scale that would justify the cosmic claim. I do not think the authors are fooling themselves. I think they have found a genuine and beautiful correspondence and are being appropriately, almost painfully, careful not to inflate it into an identity. The reader is the one at risk of the inflation. As always, the illusion is not in the object. It is in the perceiver’s hunger for the object to mean more than it does.

The Infinite Do-Loop

Here is what i keep: the Universe as an Infinite Do-Loop that is not just iterating but training each pass adjusting the very rule that governs the next pass, the condition of the loop rewritten by the body of the loop, forever, with no terminating case and no external test suite. That is the most honest picture in the paper, and it is the one that will outlive the specific matrix models it arrived in. Laws are not the axioms of the cosmos. They are its accumulated skill.

In freediving you do not get handed your form at depth. You descend, the water grades you, and if you are still moving you carry the correction into the next dive. The paper’s wager is that the cosmos is doing the same thing on a timescale that makes our whole species a single held breath teaching itself the physics by the only method that has ever actually worked on anything, which is to try, to be consequenced, and to remember.

No coach in the water. Never was. That was always the point.

Verdict: Not a theory of everything. A grammar for asking why there is a theory of anything rigorous where it can be, honest where it can’t, and pointed at the one question physics keeps flinching from. Read it as an architecture proposal, not a proof. The best ones always are.

Until Then,

#iwishyouwater <- THE GOAT Kelly Slater with Gabriel Medina (another surfing giant) at Tahiti Pro 2026. Kelly is 54. If this is a simulation, then i don’t want to know.

#EverForward,stay non-linear and curious.

𝕋𝕖𝕕 ℂ. 𝕋𝕒𝕟𝕟𝕖𝕣 𝕁𝕣. (@tctjr) / X

MUZAK To BLOG BY: album “FireDove” by Anna Lapwood, organist extraordinaire. Truly amazing music. My favorite type.

Appendix — The Cover, Decoded

The AI generated image at the top is not decoration; every element is load-bearing. If you scrolled past it, here is what you were looking at.

The double cone is a Minkowski light cone the causal structure of the single spacetime continuum, its apex resting on the ocean surface because the apex is the now. One stage, not many. The faint horizontal ellipses stepping down through it are successive nows, the foliation of time and, read the other way, the strata of the law-landscape the matrix models roam.

The freediver on the central axis is the autodidact: descending real, directed time with no coach in the water. The sparse graph of nodes threading the cone is accumulated learning — precedence, the replay buffer growing denser toward the depths, because the past is what the future gets sampled from.

The gold ring at the apex is the Infinite Do-Loop: the pass that rewrites the rule that governs the next pass, closing on the present moment.

The four equations are real a deliberate rebuke to the decorative gibberish that usually floats behind a “physics AI RAG” illustration. Each names one load-bearing idea (full glosses below):

  1. ds² = −c²dt² + dx² + dy² + dz² — the Minkowski interval. The one stage.
  2. iℏ ∂ₜΨ = ĤΨ — unitary evolution. The reversible substrate.
  3. S = Tr(½Φ² + ⅓Φ³) — the cubic matrix action. The cubic learning system.
  4. ΔS ≥ 0 — the entropy arrow. The direction learning has to manufacture.

Put them in one sentence and you have the whole essay: on one stage (1), a reversible substrate (2) runs a cubic learning system (3) that must somehow grow an arrow (4) — and whether it can is the entire question.

NOTE: It took a long time to get the image correct the way i envisioned it.

On Perception vs Illusion. Sometimes i say Perception vs Perspective but in the case of the paper i remapped to Perception vs Illusion to frame the true – not true mechanics.

Full glosses on the four equations, for the reader who wants the mechanism:

  1. The cubic matrix action — S = Tr(½Φ² + ⅓Φ³). Schematic, but honest about where the action lives: Φ is a matrix — the raw degrees of freedom — and Tr merely sums its diagonal. The quadratic term is inert bookkeeping; the cubic term Φ³ is where the nonlinearity, and therefore all the interesting behavior, hides. This is the single class of object the paper maps at once onto gauge/gravity theories and onto learning machines. When i say “cubic backbone,” this is the vertebra. (The paper’s actual actions carry more structure; the cube is the load-bearing bone.) 
  2. The entropy arrow — ΔS ≥ 0. The second law: the entropy of a closed system never decreases. It is the only fundamental law with a built-in direction, and it is the paper’s deepest problem compressed into three symbols — because learning, like entropy, has an arrow, and you cannot get either one out of the reversible microlaws two notes down without a ratchet (coarse-graining, decoherence). Note the notational collision: S is the action one note up and entropy here. Physicists live with it; context disambiguates — and the collision is itself a tidy Perception/Illusion specimen. 
  3. The Minkowski interval — ds² = −c²dt² + dx² + dy² + dz². The single invariant of the 1908 continuum: the one quantity every observer agrees on, however differently they carve space from time. The whole story sits in the minus sign on the time term — it is what makes time unlike the three spatial directions, what cuts the light cones, and what makes the arena one manifold rather than space parked next to a clock. This is “the one stage.” 
  4. Unitary evolution — iℏ ∂ₜΨ = ĤΨ. The Schrödinger equation: the wavefunction evolves smoothly, deterministically, and reversibly under the Hamiltonian Ĥ. No collapse, no arrow, nothing lost run it backward and the past returns exactly looping onto itself. This is the “reversible substrate” Everett takes at its word, and the substrate on which the paper still has to manufacture an irreversible arrow. The tension between this note and the entropy note is the entire drama. 

Posted on : By : TCTJr Posted in : Complexity_Theory|Computational_Economics|General Discussion|General Technology

Reduce. Refactor. Reuse. Loops within loops, or why reuse is not the goal.

Obvious superfluous usage of the models

First, as always, i trust everyone is safe.

Second, i have been saying something for a while that keeps coming back to me in different rooms, different codebases, different product reviews, different program reviews, and different executive conversations: Reduce. Refactor. Reuse.

That is it. Three words. No laminated framework. No twelve-box consulting bingo card. No maturity model with a gradient that looks suspiciously like it was designed by someone avoiding accountability. It sounds like an engineering mantra, which it is, but the longer i sit with it, the more convinced i am that it is not just about software. It is an operating principle for complexity. It applies to code, hardware, organizations, platforms, business processes, AI systems, manufacturing flows, partnerships, and strategy.

Most organizations get the order wrong. They start with reuse because reuse feels productive. “We already have something.” “Can we leverage the existing asset?” “Let’s standardize on the thing we built three years ago for a different customer, under different constraints, with different assumptions, and a different team that has since scattered to the wind.” That is not reuse. That is archaeology with a purchase order.

Reuse is powerful only after the thing being reused has earned the right to survive. If you reuse before you reduce, you scale clutter. If you reuse before you refactor, you scale coupling. If you reuse because a thing exists, you are not building leverage. You are distributing technical debt with better branding.

So i asked three models to react to the mantra. Not because models are authorities. They are not. Models are mirrors with a token budget. But sometimes the reflection is useful, especially when the same phrase gets interpreted through different priors. The exercise was simple: how would different thinkers react to Reduce. Refactor. Reuse. The useful part was not whether the models were “right.” The useful part was where each model placed the weight.

And yes, before somebody starts screenshotting: the Musk, Luckey, and Jobs lines below are model-generated archetypes, not real quotes. Words have meanings. So do quotation marks.

Grok: The Bar Fight Version

Grok came back with the theatrical version, imagining the mantra through Elon Musk, Palmer Luckey, and Steve Jobs. The Musk-shaped response put the weight on deletion. Not tidying. Not optimizing. Delete the part. Delete the process. Delete the line of code. Delete the meeting. Delete the requirement if the requirement is dumb. In that frame, most systems are overweight because the organization confused accumulation with progress.

“The goal isn’t elegant code. The goal is the fewest lines that still get the rocket to orbit. Everything else is cargo cult.”

That line works because it refuses to romanticize architecture. Elegant code that preserves the wrong thing is not elegance. It is embalming. Musk’s version of reduce is not “simplify the slide.” It is “prove the thing deserves to exist.” Most enterprise complexity survives because nobody wants to be the person who removes it. The system gets heavier, and then the same people wonder why it cannot move.

The Luckey-shaped response put more pressure on shipping. Reduce is the part everyone skips because writing clever abstraction feels more productive than deleting actual complexity. Refactor is where you stop lying to yourself about the design. Reuse only matters once the thing is good enough to be reused without catching fire. In hardware, this gets very real very fast. Weight, heat, power, manufacturability, maintainability, field repair, supply chain, and deployment do not care how smart the abstraction looked in the review.

“The lightest, simplest system that still works is almost always the one that ships and doesn’t catch fire.”

That is the defense-hardware version of the mantra. Reuse is not primarily about saving engineering hours. It is about reducing operational risk. A proven module, cleanly reduced and refactored, can become leverage across products, programs, and missions. But if the reusable core is dirty, then reuse becomes a force multiplier for pain.

The Jobs-shaped response treated the whole thing as product taste. Reduce until the result feels inevitable. Refactor until the cleverness disappears. Reuse only when it makes the product more human, not merely when it makes the engineer’s life easier. This is the discipline a lot of platform teams miss. The user should not be forced to admire your architecture. The experience should feel like the obvious thing that was hiding under the mess.

“The best systems disappear. If the user can feel the architecture, you failed.”

That was Grok’s useful contribution: three archetypes fighting over the same three verbs. Musk pulls toward deletion. Luckey pulls toward fielded reuse. Jobs pulls toward taste. That tension is real. It shows up in every platform conversation worth having.

ChatGPT: The Ordering Principle

ChatGPT took the more systematic route. It noticed that the mantra is deceptively simple because the order carries the philosophy. Reduce comes first because the biggest performance improvement is often deleting work, not optimizing it. Before you write code, redesign an organization, scale a process, or automate a workflow, you have to ask whether the thing should exist at all. Can the feature disappear? Can the process become unnecessary? Can we eliminate an interface, dependency, approval, or layer?

That sounds obvious right up until you sit in a meeting where everyone wants to automate a broken process instead of admitting the process is dumb. Most organizations start at the last step. They automate before they simplify. They scale before they understand. They standardize before they delete. That is how you get very sophisticated ways of preserving bad decisions.

Refactor comes next because once complexity has been reduced, what remains deserves architecture. Refactoring is not just cleaning code. At enterprise scale, it is redesigning APIs, data models, organizational seams, manufacturing flows, business processes, incentive systems, and operating rhythms. A good refactor decreases coupling while increasing adaptability. It makes the system easier to change without pretending change will stop.

Reuse comes last because most companies accidentally start there. “We already have something” becomes the opening line of a tragedy. Existing things are not automatically assets. Some are fossils. Some are scars. Some are local optimizations pretending to be platforms. Reuse only becomes powerful after reduction and refactoring. Otherwise you are simply propagating technical debt faster.

ChatGPT’s strongest line was this:

“Reuse is not the goal. Simplicity is the goal; reuse is merely the consequence of achieving simplicity.”

That is the knife. Many organizations worship reuse because it sounds efficient. But reuse without reduction and refactoring is enterprise hoarding. It creates shared libraries nobody wants to touch, common services that are common only in the sense that everyone is commonly miserable, and “platforms” that become mandatory because they are not good enough to be chosen.

The model suggested adding “repeat” to the mantra: Reduce. Refactor. Reuse. Repeat. Fair. But i pushed back. Repeat is implicit. Ordering is implicit. The strength of the phrase is that it is short enough to become instinctive. Like “ready, aim, fire,” nobody thinks you do it once and then retire to a vineyard. The repetition lives inside the discipline.

Claude: The Basis Vector Version

Claude first challenged the ordering. It argued that depending on where you stand, the honest loop might begin with reuse: what already exists, what can die, what must be cleaned, and what can then be reused by the next team. It also suggested the mantra might need a fourth R, some kind of stop condition, because otherwise refactoring can become a CTO avoiding a decision.

That annoyed me because it was partly right and partly missing the point, which is usually where useful arguments live. So i pushed back: it depends, and that is the beauty of the 3Rs.

Claude then landed on the best mathematical framing which I liked: the 3Rs are not always a fixed sequence. They are a basis. Any decision projects onto them differently depending on context. A greenfield module may weight toward reduce. A core capability used by five programs may weight toward refactor. A proven component trying to move from one program to three may weight toward reuse. Same three verbs. Different coefficients.

“A mantra is not a procedure. A procedure tells you what to do. A mantra tells you what to weigh.”

That is the part i liked. A procedure has to be correct for the situation. A mantra has to be strong enough to survive situations you did not foresee. The 3Rs do not remove judgment. They force it. They make you ask which pressure matters now: deletion, coherence, or leverage.

Claude also gave me the freediver version, which of course got my attention ( I freedive for a hobby):

“Same three strokes, but how you weight them depends on the depth, the current, and how much air you’ve got.”

That is the right metaphor. Reduce. Refactor. Reuse. Same strokes. Different water. The skill is not memorizing the order. The skill is reading the conditions without lying to yourself.

Loops Within Loops

The next step is realizing the 3Rs are not merely a sequence and not merely a basis. They are recursive. Each R contains the other two. Reduce has to be reduced, refactored, and reused. Refactor has to be reduced, refactored, and reused. Reuse has to be reduced, refactored, and reused. The loop runs inside each verb, and then the output of one loop becomes the input to the next.

That sounds like wordplay until you put it against actual work. Reducing a system is not just deletion. Good reduction has its own internal discipline. You reduce the reduce by cutting the performative requirements, zombie features, redundant approvals, decorative dashboards, and meetings that exist only because the last reorg needed artifacts. You refactor the reduce by changing the intake path so dumb requirements have fewer places to hide next time. You reuse the reduce by turning the deletion pattern into a reusable operating habit: better design reviews, better product gates, better pre-mortems, better engineering judgment, and better permission to say “no” before the system gets fat again.

Refactor has the same internal loop. You reduce the refactor by refusing to clean everything just because it exists. Some code should not be refactored. Some processes should not be redesigned. Some tools should not be modernized. Some organizations should not be optimized. They should be removed. You refactor the refactor by improving the seams that matter: interfaces, ownership, observability, support boundaries, documentation, deployment paths, and incentives. Then you reuse the refactor when the new pattern becomes an architecture other teams can adopt without inheriting the original mess.

Reuse also contains the full loop, and this is where enterprises get into the most trouble. You reduce the reuse by asking what part of the thing is actually reusable. Not the whole system. Not the customer-specific scar tissue. Not the local naming conventions. Not the assumptions that only made sense under one contract. The reusable part might be a workflow, a schema, an interface, a model evaluation, a deployment pattern, a compliance mapping, a proof point, or a failure mode. You refactor the reuse by turning that pattern into something supportable, observable, governable, documented, and owned. Then you reuse the reuse by letting the next program start from a stronger baseline and produce telemetry that tells you whether the reusable core is actually improving.

That is the loop within the loop. Every reuse creates new evidence. That evidence should trigger the next reduction. What did the second program not need? What did the third program break? What assumption failed in the fourth customer environment? What interface kept changing? What support question appeared twice? What deployment step still required a hero? Those signals tell you where to reduce again. The loop does not end at reuse. Reuse is where the next reduce gets its evidence.

The moat is not the layer; it is the loop. Take the action, capture the outcome, attribute the authority, evaluate the result, correct the workflow, and make the next decision less uncertain than the last. The 3Rs are the same pattern applied to complexity: reduce what should not exist, refactor what must exist, reuse what has earned the right to travel, then let the evidence from reuse tell you what to reduce next.

Now Apply The 3Rs To The 3Rs

A useful mantra should survive being turned against itself. So let’s do that.  We are creating a Noumena.

Noumena (plural of noumenon) is a philosophical term meaning an object or event that exists independently of human sense perception and the mind. It describes a “thing-in-itself” rather than the thing as it is experienced, heard, seen, or felt by an observer.

Origin: The word comes from the Greek noein, meaning “to think” or “to perceive with the mind”.  Also Immanuel Kant, the philosopher popularized the concept in his Britannica guide on Noumenon as part of his work on human knowledge.

#TCTRule

Words Have Meanings.

via Dr Mathew Aldridge

Can Reduce. Refactor. Reuse. be reduced? Yes, and that is why i keep resisting the urge to add a fourth word. “Repeat” is true, but unnecessary. “Freeze” is sometimes useful, but situational. “Retire” is important, but already contained inside reduce. The three words are short enough to remember and sharp enough to cause discomfort. That is a good sign. A mantra that needs a process diagram before it can be used is not a mantra. It is another artifact looking for a meeting.

Can the mantra be refactored? Also yes. The first version reads like a sequence: reduce, then refactor, then reuse. That is still useful because most organizations start with reuse and create the mess they later call platform strategy. But Claude’s basis-vector framing improves the architecture. Sometimes the situation weights toward reduce. Sometimes toward refactor. Sometimes toward reuse. The refactor is not to abandon the order; it is to understand that the order is a default, not a prison.

Can the mantra be reused? That is the real test. If it only works for code, it is a software slogan. If it works for hardware, AI, organizations, operating models, platforms, products, and partnerships, it is closer to an enterprise heuristic. The receipt is whether people can use it in a room to make a better decision. Should we delete this requirement? Should we clean this interface? Should we productize this program artifact? Should we reuse this component or quarantine it until it stops leaking? If the 3Rs help answer those questions, they are reusable. If they become wall art, they are not.

That is the self-analysis. The mantra reduces well because it is already small. It refactors well because it can shift from sequence to basis without losing meaning. It reuses well because it travels across domains. But it also has a danger: it can become too clean. Three words can hide a lot of judgment. That is why the loop matters. The 3Rs are not a substitute for thinking. They are a forcing function for thinking.

The Failure Modes

Every R has a shadow.

Reduce can become vandalism. Some people hear “reduce” and start cutting without understanding load-bearing structure. They delete the weird exception that was actually protecting the customer. They remove the approval that existed because someone once set the building on fire. They simplify the system until it is elegant and wrong. Reduction without context is not discipline. It is austerity with a hoodie.

Refactor can become avoidance. Some people hear “refactor” and discover a bottomless cave where decisions go to die. The architecture is never clean enough. The interfaces are never stable enough. The platform is always one quarter away. Refactoring is necessary, but it can become a beautiful excuse for not shipping. A refactor that never reaches reuse is not architecture. It is therapy.

Reuse can become cargo cult. This is the enterprise favorite. A thing worked once, so now it must be a platform. A local tool becomes a standard. A program artifact becomes an offering. A prototype becomes a product. A script becomes infrastructure. A PowerPoint becomes strategy. Reuse without reduction and refactoring is how an organization scales its past mistakes while congratulating itself for efficiency.

The reason the 3Rs work together is that each one corrects the others. Reduce keeps reuse from becoming debt propagation. Refactor keeps reduce from becoming demolition. Reuse keeps refactor from becoming artisanal self-expression. The tension is the point. If one R is always winning, the system is probably lying to you.

The Enterprise Loop

At enterprise scale, the 3Rs become loops within loops because every layer of work has its own version of the cycle. A team reduces a local workflow, refactors the surviving pattern, and reuses it inside a program. The program generates telemetry, failure modes, customer feedback, compliance mappings, and deployment knowledge. A product team reduces that program-specific learning to the essential pattern, refactors it into a supported capability, and reuses it across multiple programs. A platform team then reduces the common seams, refactors the interfaces and governance, and reuses the pattern across the portfolio. The company brain captures the evidence and starts the loop again.

That is how program learning becomes product learning. That is how product learning becomes platform learning. That is how platform learning becomes operating leverage. Not by declaring reuse. Not by inventorying assets. Not by creating a portal. By running the loop until the next team starts from a stronger baseline.

This matters because large organizations love to say “reuse” when what they really mean is “please make my past decision look like a platform.” We see this in software, infrastructure, internal tools, product-led solutions, proposal content, operating models, partnerships, and AI. Someone builds a local thing under local pressure. The thing works well enough to survive the contract. Then someone declares it reusable. But it was never reduced to its essential customer value. It was never refactored into clean interfaces, support boundaries, observability, governance, documentation, and ownership. So when the next program adopts it, they inherit not a product but a fossil.

Then everyone blames adoption.

No.

The thing was not ready to be reused.

Reuse is not a label. It is a property earned through reduction and refactoring. This is especially important in a product-led services company. A program can create learning. A product can encode that learning. A platform can distribute it. But only if the learning has been reduced to the essential pattern, refactored into something supportable, and reused with enough telemetry to improve the next implementation.

Otherwise, we are not compounding.

We are copy-pasting scars.

#TCTRule

Reuse is not the goal. Reuse is the receipt.

The goal is a system simple enough to understand, clean enough to change, and valuable enough to carry forward. That is true for code. It is true for hardware. It is true for AI agents. It is true for operating models. It is true for business processes. It is true for the company brain. It is true for every platform that wants to be more than a portal with a funding line.

Reduce what should not exist. Refactor what must. Reuse what has earned it. Then listen to what reuse teaches you, because every reuse is also a test. If it works, you have evidence. If it fails, you have telemetry. If it almost works, you have the next refactor. And if nobody adopts it, you may have discovered that the thing you were trying to reuse never should have existed in the first place.

That is the loop.

Reduce the work until the truth shows. Refactor the truth until it can move. Reuse only what survives contact with another customer, program, mission, or market. Then run the loop again inside the loop you just created.

Same three strokes.

Different water.

Until Then,

𝕋𝕖𝕕 ℂ. 𝕋𝕒𝕟𝕟𝕖𝕣 𝕁𝕣. (@tctjr) / X

#iwishyouwater <- Tahiti 2026 opener. Hydro dynamic complexity at its finest.

MUZAK TO BLOG BY: “Hesitation Marks” by NIN. “Copy Of A” was amazing in concert.

Footnotes

[0] The model responses referenced here came from a prompt exercise comparing how Grok, ChatGPT, and Claude interpreted “Reduce. Refactor. Reuse.” The imagined Musk, Luckey, and Jobs responses are not quotations from those people. They are model-generated archetypes. Again: words have meanings.

[1] i kept “repeat” out on purpose. If you have to say “repeat” every time, the mantra has already become a checklist. The 3Rs are a discipline, not a one-time ceremony.

[2] “Reuse is not the goal. Reuse is the receipt.” That is probably the line i would underline twice. It is also the line most enterprise platform efforts should be forced to confront before calling themselves platforms.

[3] The “loop within the loop” framing is intentionally connected to the earlier “Headless With a Spine” argument: the real moat is not a layer but an instrumented control system that acts, captures outcome, evaluates, corrects, and improves the next decision. i love control system theory, feedback loops and most importantly complexity analysis.

[4] Yes, the 3Rs are dangerously close to the old environmental slogan. That is fine. Complexity is pollution too: it accumulates, spreads, and eventually makes the whole system harder to breathe in.