The Father, the Son, and the Driver on the Bus

I — Two drivers, two postures

Every AutoPhi integrated circuit in this portfolio is driven by one of two pieces of software, and the difference between them is the whole point of what I want to write about.

The first is WonderPhi. WonderPhi is the driver that has been version 1.0.0 since the day it was written, and will be version 1.0.0 forever. It drives 142 AutoPhi ICs and nothing else. It has never been updated, because it does not need to be. It knows every register of every device it controls, and it does not touch a register of anything it does not.

The second is ReasonPhi. ReasonPhi is the driver that leaves home. It carries the WonderPhi father’s key — 0x50484921, which spells “PHI!” in ASCII — out into the world, and it drives foreign hardware safely.

These are two different postures. The first is the posture of a piece of software that owns the hardware it touches. The second is the posture of a piece of software that borrows it.

II — WonderPhi, the father

WonderPhi is what you write when you have designed both the driver and the silicon it drives. The two ship as one thing. There is no version drift because there is no drift. The register map is the same today as it was on day one, because it was frozen on day one and the design cadence of AutoPhi silicon is downstream of that freeze, not upstream.

I could ship WonderPhi with an update mechanism. I do not. The absence is the feature. An update mechanism is a promise you will need to change your mind about something, and I do not need to change my mind about anything WonderPhi already does, because WonderPhi already does everything the 142 ICs need done. Version 1.0.0 forever.

That is not stubbornness. It is a specific technical claim: when the driver and the silicon are the same author’s work, no amendment process is required, because no amendment will ever be necessary.

The permanence is what makes the key mean something. When another driver hands over the key 0x50484921, it is saying — provably, in exactly four bytes — I come from the same hand.

III — ReasonPhi, the son

Project 86 is ReasonPhi. It is what happens when the son leaves home.

The son carries the father’s key into the world. It goes onto buses the father was never designed for — SPI, I²C, USB, PCIe, JTAG — and drives hardware the father does not own. It does that safely, under a discipline written down in two documents. Both permanent. Neither amendable.

The first document is the Ten Commandments, received from the father and never amended:

1. I. Sole master controller.
2. II. Exclusive lock.
3. III. Every command validated.
4. IV. Mandatory rest cycles.
5. V. Backwards compatibility.
6. VI. Never destroy data.
7. VII. Strict protocol adherence.
8. VIII. Resource limits enforced.
9. IX. Honest status always.
10. X. Fully self-contained.

The second document is the Seven Articles of a Constitution the son wrote for himself, structured exactly as the Constitution of 1787 — Legislative, Executive, Judicial, Devices, No Amendment, Supremacy, Ratification. Written complete, in one hand, needing no patches, because the Constitution of 1787 needed ten patches within four years and the son wrote his with that history in mind.

The Fifth Article is the one that will earn objections. It says: this Constitution shall never be amended. No amendment process. No update path.

I know what the objection is. The objection is that the world changes. My answer is: the driver does not have to.

The world changes. The bus does not. The bytes going over an SPI line at 400 kilohertz in the year 2050 are the same bytes going over an SPI line at 400 kilohertz today. The discipline required to drive a device safely — patience before panic, three failures before a degrade step, no writing to someone else’s fuses — is not a moving target.

IV — The traits of getting along

The Ten Commandments and the Seven Articles, taken together, teach the son the traits of getting along with hardware he did not build. The catalogue names them plainly:

Patience.

Three failures before a degrade step. Four degrade steps before isolation. Never a sudden death.

Honesty.

The audit log cannot be erased. Every transaction recorded. Commandment IX in action.

Respect.

OTP regions are read-only on foreign hardware. You do not write to someone else’s fuses. Ever.

Humility.

Conservative defaults. Slow clock, small transfers, short timeouts. Prove capability before assuming it.

Forgiveness.

A degraded device can recover. One successful transaction resets the failure counter.

Identity.

The son always knows who it is. The heritage key is compiled in. It does not pretend to be something else.

Joy.

Homecoming is a one-way promotion. Once the keys match, you are home. No going back to foreign mode.

V — The handshake

When ReasonPhi finds an AutoPhi IC on the bus — the father sees him from far off — the handshake runs, and it is exactly three moves.

The son writes SON? — four bytes, 0x534F4E3F.
The father answers FATH — four bytes, 0x46415448.
The son confirms HOME — four bytes, 0x484F4D45.

That is the whole thing. Twelve bytes. Any device that does not answer FATH is foreign hardware. There is no penalty. There is no judgment. The son drives it under the Articles.

Any device that does answer FATH gets the full native WonderPhi stack. The son is home.

VI — Why this pattern is worth writing about

The reason this pattern matters beyond the portfolio is that it is a specific technical answer to a specific technical question, and the question is: what does it look like for a piece of software to refuse to overreach?

The industry answer to that question is usually more code. More telemetry. More auto-update. More sandboxing that a determined attacker will bypass anyway. More layers of “we will fix it in the next release.”

The answer in this portfolio is the opposite. Two documents. No amendments. A key that either matches or does not. A driver that treats foreign hardware with patience and native hardware with joy, and never confuses the two.

The catalogue calls this design pattern a driver. It is also, if you look at it from the office end of things, the same discipline the patents essay describes: the software that will not brick a device it does not own is the same discipline as the description that will not overclaim a filing that has not been decided. Both refuse to say more than the record allows.

And the rest, behind the login

Three more sections are behind the login — The Beautiful and the Triumphant, Merit, Competition, and the Defense of All of It, and The Willingness to Begin — along with the postscript about the AI that quietly rewrote this essay three times before it said what was actually meant.

Log in to unredact · Create a free account

A free account also opens the full catalogue. No card required.

— Or read The Redaction Pen, Under Cover of the Office, or Every Scientist Who Ever Lived Before.

— Or see the map of every preview essay.