An answer the graph gives has an address

Answers Identity · Epistemology

Every declared question, answered from every row it can be answered from, is a page of its own, where and only where the walk from that row is non-empty: the same engine binds it at build, the page is canonical to itself and linked from the row and from the question, its structured data is the question as asked from that row with the rows the walk reached as an ordered list, and no page exists for an empty answer.

What goes wrong without it

A reader who arrives with a question arrives at an address, and an answer engine cites addresses. The composer answers any declared question from any term on demand, but a thing that exists only after a click has no address to cite and nothing for a crawler to read. The risk of publishing many pages from one template is the one Google names as scaled content and doorway abuse: pages that say little and funnel. The guard is structural: a page exists only where the binding is non-empty, says exactly what was bound and nothing generic, and sits in the hierarchy under its question and beside its term.

What proves it — 2

Each is a gate the build runs: a check inside a ring, a whole ring, or an eval beside them. A build stops at the first that refuses.

• ring:6the site ring
  The built site is the whole graph and nothing else: every page indexed, addressed by a label, self-contained and free of any private name; every structured-data identifier a subject the standards export wrote; every page unfurling to its own card, and every sitemap entry naming that card as its image; every journey with its SCXML twin; the sitemaps held to the graph; a graph under a megabyte. And the host held to the ground: the Worker serving the build as its assets and running first for every request; the allowlist and the redirect list it carries cut from the graph, every address the graph once answered to in the list with the status the law gives it and none of them a page; every endpoint served by the files it names; and the beacon sending to the collector's endpoint and nowhere else; every projection the law declares in the build, served by the files that say they serve it, and named in llms.txt; and the Worker reading the host's caching rules and owed headers from the law, writing none of its own; every answer a question carries a page where the walk is non-empty and nowhere else, its structured data naming exactly the rows the walk reached.
• eval:enginethe engine agrees with itself
  The binder that runs while the graph is built and the binder that runs in a reader's browser find the same bindings: every pattern bound against the whole model to the same instances and the same rows in every role, the published example among them, and every view bound again from every row it answers from, row for row, and the port of the pattern law beside the browser's engine refuses every way a declared pattern can be broken exactly as the law does, and every question bound again from every row of its root kind finds an answer exactly where the build published one and nothing where it did not.

Derived from — 2

• Google Search CentralSpam policies for Google web search
• schema.orgItemList

Where this model stands

registry/law.json `addresses.projections.question_row` is the address, /questions/{question}/{slug}/, drawn by its route like every other projection.

scripts/ground/graph.py binds every question from every row of its root kind with the same engine that binds the views, and writes an answer only where the binding is non-empty: `answers` on the question, each with the row, its address and every whole binding.

The site draws each answer as the walk read from that row - a sentence, a list, a chain or a table by the law's drawing rule - under the question's page and beside the row's; the row page lists the questions answered from it, the question page the rows it is answered from, and the table leaves with the reader as a file.

The structured data is a Question as asked from that row, its accepted Answer about an ItemList of the rows the walk reached, each a ListItem with its address. The site ring holds every answer page to existing, to its list naming exactly those rows, and refuses a page answering a question from a row the graph carries no answer for; the engine eval binds every question again from every row of its root kind in the browser's runtime and holds the answers identical, present and absent alike.

The sitemaps, llms.txt and the search index enumerate the answers with every other page, as their own group.

What it does not claim

An answer is drawn from one question at a time. A page answering several questions from one row is a view, and is declared as one.

RUL-044