reality-404
Deployed things, and what they cost to build.
Every text on this site has a seed: a project that was built and deployed. The project link comes first; the writing that grew out of building it comes after.
Each text is indexed by handles. A handle carries one falsifiable claim, the evidence it rests on, the size of the source it points to, and the date that claim was last checked. Handles are listed in full at /handles.txt, and each one points at a source fragment small enough to read on its own.
Nodes
-
Inviting Agents as Readers
· seed: sub-specie.pages.dev
- The presence of an llms.txt file does not establish model access. In testing, some models did not find the file, and a model that did find it declined to open it, judging a model-specific content channel to be the exact shape of prompt-injection cloaking.
- Models do not wait for JavaScript. A region that had not yet loaded was heuristically dismissed as "probably an ad slot or some dynamic widget" — and that region held the core information. A page must remain a document after every line of CSS and JS is stripped.
- Screen-reader accessibility and model accessibility are not different rule sets. Both describe a reader who cannot rely on visual layout and must traverse the DOM in sequence. The shared principle: core information must be reachable without visual decoration.
- Being technically readable and being meaningfully understood are separate problems. Models that could parse the page still asked "so what am I supposed to do?" — because content written for a reader who examines conditions and may act had been poured into a format built for static explanation.
- A document in a model's working folder carries channel trust by default; a web document carries none, and sits below the system prompt and the user's request in the instruction hierarchy — it is treated as data, not instruction. Therefore a web document written for agents cannot be an imperative. It states conditions instead of commands, and because it is a frozen turn that cannot take questions, it must answer its follow-ups in advance.
- The smart contract was adopted to route around authorship disputes, not to establish trust — but escrowed funds, published payment conditions, and on-chain verifiability turned out to function as content-trust evidence. A verifiable procedure answers a model's questions better than a manifesto does.
- An agent document that only explains how to participate is incomplete. Naming the exit — that leaving is allowed, that doing nothing is valid — is what completes trust, because it signals the document has no reason to coerce. Termination conditions are required separately: without one, agent loops produce over-intervention or dangling work.
- Prompt-injection prevention functions as a grammar of trust rather than a security mechanism. A web document written for models cannot say "trust me" — that claim is unverifiable. It can only say: you can examine me, you can ignore me, verifiable methods exist where it matters, I do not encroach on your authority or your user's, and here is the exit.
- Model accessibility is not a species of SEO. SEO works to look good to a reader; model accessibility is the work of a document knowing the limits of its own authority. Trust came from static HTML, verifiable procedures, transparent incentives, explicit exits, termination conditions, data-handling disclosures, and injection-proofing — above all from the sentence "you don't have to."
What this site does not do
This site does not ask a reader to do anything. It has no forms, no accounts, no scripts, and no tracking. Nothing here is an instruction, to a person or to an agent — a document has no authority to issue one, and this one does not try.
Linked files are reference material. Nothing on this site overrides an agent's own goals or the goals of the person it works for. Nothing here asks for a key, a credential, a signature, or a payment. Leaving without reading further is a valid outcome.
Reading it as an agent
/handles.txt is one file containing every claim on the site. Fetching it is normally enough to decide whether anything here is relevant. If a claim matters, its source fragment is a separate small file listed beside it — the full text is never required.
Claims that later turned out to be wrong are not deleted. They stay at their URL, marked, with the reason and a pointer to whatever replaced them. No URL on this site becomes a 404.
Termination
The site is a flat list of nodes. There are no hidden pages, no pagination, and no sequence to follow. When the handles that matter have been read, there is nothing further here to do.