The first truth a product owes is that it can be touched.
The human correction that produced this node was blunt:
we cannot apply experiment nor node process thinking as it does not lead to execution
That sentence protects the boundary around node process and experiment process. A node makes a claim durable enough for the graph. An experiment makes a possible form vivid enough to compare. Both are real work. Both can halt upstream of the place where a user can click, pay, send, correct, trust, or leave.
Execution needed its own epistemology.
The second Homebase surgery found the compact version:
clickable truth first
durable truth second
design beauty third or separate
That is the strongest form of the CEO surgery method so far. It is a truth gradient for moving from thought to product without letting any layer lie for the layer below it.
Clickable truth is the first execution truth. It means the promise has a surface a person can actually walk. In Homebase, the path became: begin, first-day context, creature naming, username confirmation, concerns, payment-shaped dogfood step, success transition, and app. Some of that path was provisional. Some lived in browser state. Some lived in trace JSON. That was acceptable because the product was honest about its mode: dogfood, testable, reversible, and visibly incomplete.
Clickable truth matters because it exposes friction that upstream thought cannot see. The sketch may carry the right sequence and still look ugly when rendered. The report may name the right obligation and still point at the wrong repo. The code may deploy and still produce a screen that feels like a wireframe learned to submit. A clickable path lets the world answer.
Durable truth is the second execution truth. It means the claim survives outside the clickthrough. Payment truth needs Stripe, webhook verification, and a payment table or equivalent durable account state. Creature-name truth needs an account field or setup record. Email-to-brain truth needs an inbound message to become inspectable memory and correction, not just a row in an email tab. Chat truth needs persistence if the product implies the creature remembers.
This distinction saved the second surgery from a common prototype lie. A simulated checkout can be a useful dogfood beat. It cannot become public billing truth. Payment state in trace metadata can help inspect the path. It cannot certify that money moved. The interface can say "paid test" when the user is inside test mode. It should not teach a public user that billing is real before the billing layer exists.
Design beauty is third or separate because beauty amplifies claims. A polished fake payment screen is more dangerous than an ugly honest one. A beautiful dashboard can hide the absence of a first email crossing. A graceful chat panel can make local-only state feel like memory. Once function flows, design deserves its own surgery so taste can improve the surface without rewriting the state contract by accident.
This order is the colimit of the Homebase work so far.
The graph supplied should. The experiment supplied possible form. The company supplied obligation. The product supplied clickable truth. Backend and payment work must supply durable truth. Design supplies beauty only after the truth it beautifies has been named.
CEO surgery is the method that keeps those truths attached while the stack moves.
It does this by descending to the lowest layer that can still falsify the claim. A graph can falsify a node by showing that the claim adds nothing. An experiment can falsify a sketch by showing that the form carries no energy. A company order can falsify itself by failing to change action. A product can falsify all of them when the user crossing breaks. Durable state can falsify the product when the interface implies a truth the system cannot verify.
The lowest false layer gets the next cut.
That is why the method keeps proving valuable. After onboarding came clickthrough. After clickthrough came the state truth table. After that came Stripe, design smoothing, first-email-to-brain, and local-driver architecture as separate future surgeries. The method did not try to solve everything at once. It found the next truth class and protected the others from contamination.
The first email-to-brain loop is a good example. A complete inbox dashboard would look satisfying. One email crossing is more truthful. The user sends a message to username@homebase.now; the Worker stores it; the brain receives a signal; the user can inspect what was stored; the user corrects it; the next email changes. That one crossing proves more than a wall of tabs because the crossing can teach.
The same logic explains the owner-card and Stripe work. A bypass can be a permissioned zero-charge success state. It should not skip all payment machinery unless the run explicitly chooses a rougher dev shortcut. Stripe is one way the payment layer gets a verifiable truth label. The point is to keep the truth labels visible: owner bypass, gifted trial, paid, simulated, failed, pending. Product motion is allowed to be provisional. The provisional state has to tell the truth about itself.
That is what node process and experiment process could not do alone. They can compress the principle and explore the form. Surgery places the principle and the form into the state machine where the user will meet them.
The graph's old danger was becoming wise about products it had not repaired. The product's danger was becoming clickable in ways the graph had not authorized. Surgery is the bidirectional discipline between them: thought descends until it can be clicked; clickthroughs ascend only as truth-labeled evidence.
Clickable truth first prevents upstream beauty from idling. Durable truth second prevents dogfood from hardening into a lie. Design beauty third or separate prevents ugliness from becoming destiny while preventing beauty from hiding broken state.
The product is true only at the layers where it can be checked.
Surgery is how the stack keeps checking.