Design, with a capital D

An influence on Dinis Cruz — entry 13 of 25 in his register.

Discovered by mining and confirmed by Dinis Cruz the day the commissioning pack shipped — the first DISCOVERED → confirmed transition, before the site existed. The strongest trace on this site: an influence that became a mandatory step in the pipeline.

Block 1 The anchor

“Design is how it works” — the Jobs formulation the estate's Designer role is built on — Steve Jobs

↗ the anchor work

Linked, never rehosted. This site explains why the work resonated and traces where it was applied; the work itself stays where its author put it.

Anchor unconfirmed. The formulation is from the 2003 New York Times Magazine profile linked above; the candidates for what actually did the shaping are that piece, the MP3-to-CD whiteboard story, a keynote, or a specific product. Asked as Q2b.

Block 2 In his own words

First person is the house style on this site and nowhere else in the network — what resonates with me and why is the genre, and paraphrasing it into corporate third person would destroy the evidence. Until the briefing document for this entry arrives, this block carries the first-person statements that already exist in the corpus, cited by file.

Design is the coherence between the internal structure and the external experience.

The estate's own extension of the Jobs formulation, and a sharper one: it says the two halves must agree, which is a testable claim about a codebase rather than a slogan about products.

Good design is invisible… the only way to notice it is to go back to the previous version and think: “This is way worse.”

And this is the sentence that became a test. Read it again with the next block in mind.

The reason this is the strongest-traced entry on the site is not the number of citations. It is that the influence turned into process. The brief's section is titled The Jonathan Ive Principle: Good Design Starts with the User; the observation is that you notice good design only by reverting and feeling the loss; and the estate turned that observation into the Jonathan Ive test — is it simpler? would reverting feel worse? — which is a mandatory validator for every UI change.

That is the difference between a quote on a wall and an influence. A gate in a pipeline is checkable, dated, and possible to fail. Most entries in this register aspire to a trace table; this one had its trace table written as a workflow before anyone asked for the register.

What is genuinely missing is the personal history. The corpus shows the influence fully operational and says nothing about when it arrived — which is why Dinis Cruz's confirmation came with a question attached rather than closing the entry.

Block 3 The principle

Block 4 The trace table

1 of 5 row carries no version. The format's own rule is that a trace table without versions is an opinion — these rows name a file the corpus scan reached but not the release it was read at. The generate-or-date rule.

This table on its own, with its sources → · as JSON · as markdown

Three rows implemented at a stated version, from three documents in the same fortnight of the corpus. That density is why Dinis Cruz's confirmation was a formality rather than a discovery.

Block 5 The gaps, as build specs

Patterns from the anchor the estate does not implement yet, written precisely enough that an agent could pick one up as a work item. This is what makes an influence page forward-looking: it is provenance and backlog in the same document.

Block 6 The checklist

What to ask of new work in this influence's light. The checklist is the influence made operational — the part an agent can run without having consumed the anchor work.

• Is it simpler than what it replaces? Not smaller — simpler.
• Would going back to the previous version feel worse? If not, this change is decoration.
• What did this remove? If the answer is nothing, look again.
• Does the internal structure agree with the external experience, or is the surface hiding the shape?
• Start from what the person is trying to do: does this design fall out of that, or was it designed first and justified after?

Block 7 The wider library

The rest of the work, linked and never rehosted, each item with one line on what it adds. The full union of every entry's Block 7 is at /library/.

• The 1996 Wired interview — a different and broader Jobs formulation — design as the fundamental soul of a made thing — and useful beside the anchor rather than instead of it ↗
• Objectified (2009) — Ive and Rams in the same documentary — the clearest available statement of the lineage this entry nests
• Insanely Simple — Ken Segall — the simplicity-as-subtraction argument, from someone who was in the room

The corpus evidence

What the mining run found, by path. These are the files that put this entry in its tier — the claim on this page is checkable against them, which is the whole point of the format.

Paths are as recorded by the mining run behind the commissioning pack (v0.33.62, 25 August 2026). This repository holds the website, not the corpus, so they are cited rather than resolved — R2 in the comms queue.

Where this sits

• Nested here: The wider design canon

The whole graph →