Cathedral Machines, Tangent Fixtures

In June I argued that most enterprise UI is going fast-fashion: tangent surfaces spawned for a request, cathedral surfaces that carry trust, and named arbitrators of taste so "everyone can generate an interface" does not mean nobody is accountable. Hardware is the same split with mass. Teams can now spawn CAD variants, HMI screens, twin cameras, and fixtures at the speed of a prompt. Industrial culture still treats every surface as capital because metal is expensive. Half right. The other half is how you lose ninety days to a PLM baptism for a jig that should have died on Friday.

Autodesk will sell you an agentic thread that makes everything look like a cathedral, AutoTimeline, AutoAssemble, assistant-driven Inventor, natural language over Vault. Some of that is real leverage. All of it is a temptation to put a six-month process on a Tuesday object. You need both speeds, labeled honestly, or you will either freeze the line or erode the product.

Cathedral: the object that signs your name

The shipped product. The safety-related HMI. The drawing a regulator will read. The brand-bearing machine in a customer plant. These deserve craft, rehearsal, accessibility of the operator interface, performance of the control loop, cited materials, a ladder of evals, and owners who treat them like infrastructure. They are rare. They compound. Skills here are low-freedom: scripts, forbidden states, allowables that exist.

Machine-readable brand still applies. If you make physical products, the cathedral is not only CAD. It is how the thing feels in the hand and on the floor, the same instinct as DESIGN.md as velocity, aimed at atoms.

Tangent: packaging for a decision this week

The fixture you print to hold a test. The one-off jig. The twin camera you spawn because someone asked a question the dashboard could not answer. The HMI that exists for a shutdown. The review shell for a single lot. These are fast-fashion software with a print farm. The UI and the geometry are packaging for a decision. They may be wrong by Friday. Nobody should mourn them.

Pretending they deserve cathedral governance is how central engineering becomes a queue. Letting them leak into production without a label is how you get an unqualified part in a customer machine. The skill is the label: cathedral or tangent, written, at birth.

Assign arbitrators of taste (they need DfM)

When anyone can spawn a part, "everyone is a designer" becomes "nobody is accountable for what gets cut." Named arbitrators hold the compounding bar:

• What a cathedral must feel like and how it must fail-safe.
• Which skills are low-freedom (safety, materials, brand) versus high-freedom (fixture, review).
• When a tangent is trying to become a cathedral without paying the cost, eval ladder, owner, qualification.
• Permission to clone, invert, sunset without a change board for objects that were born disposable.

These people are not a design-system police. They are closer to a chief engineer who still opens the model. If the arbitrator only sees renders, you have rebuilt summary leadership in CAD.

Skills split the same way

Cathedral skills: tight tools, cited materials, evals that fail CI, compatibility that names the air gap. Tangent skills: high freedom, allowed to die, no obligation to live in the thread. Clone / invert / sunset is not sloppiness. It is how a library stays a library instead of a museum of every jig.

Hot work / deep work still rhymes. Cathedrals are deep work. Tangents are often hot. Silently blending them is how a Tuesday fixture becomes an undocumented production step.

Failure modes

Everything is a cathedral. PLM baptism for a print. The line waits. Shadow CAD wins.

Everything is a tangent. Unqualified geometry in the field. Trust erodes. Legal learns your name.

No label. The twin view from March is now "how we run cell B." Nobody remembers it was a sketch.

Arbitrator as CoE. Every spawn needs a ticket. You reconstituted the monolith.

Vendor thread as law. Agentic PLM is useful. It is not a substitute for taste.

This month

Pick one cathedral object and write the non-negotiables as skills. Pick three tangent types (fixture, review shell, shutdown HMI) and write the sunset rule in a paragraph. Name the arbitrator. Make the label visible in the repo. If you cannot tell which folder is allowed to die, you do not have two speeds. You have a mess.

Cathedral machines, tangent fixtures. Two speeds, labeled at birth, taste assigned, skills matched to fragility. Generate freely. Qualify rarely. Sunset in public. That is how hardware inherits the fast-fashion lesson without inheriting the recall.

Related: Fast-Fashion Interfaces, The Last Mile Was Always Atoms, and The Digital Thread Is a Harness.