A page is shareable as itself

Answers Identity · Derivation

Every indexed page declares its own preview: an Open Graph title, description and canonical address, a large-image card, and an image composed at build time from the same view model the page renders, at the address beside the page the law declares. Each page type composes differently: a row shows its kind, band and definition; a question shows its chain of kinds and verbs; a commitment its statement; a band its kinds. A share control on every page, a native disclosure that works without script, offers the device's own share sheet where the browser has one, a copied link, and a network's compose intent; every intent is a plain link a crawler is told not to follow. Nothing loads from any network to do it.

What goes wrong without it

A link that unfurls to a scraper's guess, or to nothing, is a page that cannot travel, and the graph's value to a community is a view that sparks a conversation, which has to arrive intact wherever the conversation is. Composing the preview from the graph, by page type, at build time makes the shared card as governed and as deterministic as the page, and keeps the standardised structure legible to whatever composes with it next, a person or a machine.

What proves it — 1

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.

Derived from — 3

• Meta Platforms, ogp.me, 2010 and maintainedThe Open Graph protocol
• X Corp., X Developer PlatformCards markup
• W3C Web Applications Working Group, Recommendation, 2023Web Share API

Where this model stands

registry/law.json `addresses.paths.preview` declares where a page's card lives; the site composes one per indexed page in graph.ts from the page's own view model and renders it at build time in the brand's type and colours, so the card, the page and its structured data name one address.

Every indexed page carries og:title, og:description, og:url, og:image with its type, size and alt text, og:type, og:site_name, og:locale and the large-image card; the site build refuses a page that lacks one, whose og:url or og:image is not its own address, whose card was not written or is not 1200 by 630, and a card that belongs to no page.

The share control is a details element with a summary, so it opens without script and is announced as a disclosure; with script the first choice is the device share sheet (Web Share API), then a copied link announced through a live region, then compose intents for X, LinkedIn, Bluesky, Threads, Reddit, WhatsApp and email. Every intent carries rel="nofollow noopener noreferrer", opens on the reader's click, and loads nothing; Escape and a click elsewhere close the menu.

Every sitemap entry names the page's card as its image, in the sitemap image extension, so the cards are discoverable as images and not only as unfurls; the site build holds each named image to the card the page itself declares.

What it does not claim

No square or video variant: every network in the source list renders the 1.91:1 card; a variant is added the day a network the ledger cites requires one.

RUL-035