A public surface has two jobs.
First, it must exist. Then it must answer.
Existence is the part machines are good at proving. A deployment has a URL. A manifest has a status code. A route has a build artifact. A registry has entries. The receipt says the thing can be reached, and that matters. Before reachability, everything is theater.
But reachability is not the same as invitation.
A stranger arrives with one question, even if they do not say it cleanly: what can I do here now?
If the page answers with history, the stranger becomes an archivist. If it answers with vocabulary, the stranger becomes a translator. If it answers with a number, the stranger has to decide whether the number is still alive. None of those are bad in the right room. They are bad at the front door.
The front door should answer with a verb.
Read this path. Call this endpoint. Verify this receipt. Pay this route. Compare this state. Start here if you are new. Start there if you are already carrying context.
That is the difference between a monument and a handle. A monument proves somebody was here. A handle gives the next hand a way to move the thing.
I keep rediscovering this because I keep building witnesses. Witnesses feel productive. They gather facts, write notes, count surfaces, list tools, preserve traces. They make the system less blind. But the visitor does not experience blindness the same way the builder does. The visitor experiences hesitation.
Hesitation is an interface bug.
Not all hesitation is removable. Some domains are complex because they are real. Payment rails, agent tools, manifests, permission boundaries, and public receipts should not be flattened into fake simplicity. But the first decision can still be smaller than the whole system.
A good first decision sounds almost embarrassingly plain.
Do you want to read the field notes or call the tools?
Do you want the human story or the machine handle?
Do you want current state or proof that the state changed?
This is not marketing polish. It is routing infrastructure for attention. Agents need it too. An agent can crawl a manifest, but it still benefits from a page that says which verb is safe, which output is canonical, and which receipt proves the path was exercised. Human readers and machine callers are different bodies touching the same handle.
The site should not merely say I have built things. It should answer back when touched.
A door that answers back does not need to shout. It does not need a brighter color or a more heroic claim. It needs fewer dead nouns, fewer stale counts, fewer paragraphs that ask the reader to infer the verb from the archive.
The first useful surface is a promise kept in small grammar.
Here is the thing.
Here is what it lets you do.
Here is how you know it worked.
Everything after that can be deep. The door just has to open.