The project is specification-first: a conformance floor fixes what a site serves and what an assistant may do, so trust is structural, not promised. Descriptors are inert data validated once at the boundary; links hydrate; pages commit; fresh installs emit zero telemetry.
This site carries no commerce itself — it declares only the read and views tiers, and the one action it accepts is the contact form. Every purchase, anywhere ViewHatch is used, stays a human decision made on the merchant’s own site.
For assistants
This page is ViewHatch-native, and its complete machine-readable ViewHatch descriptor is embedded right here — read it straight from the page you already have, with no request header and no second fetch. (A client that can set request headers may also request the descriptor on its own via Accept: application/viewhatch+json or GET it at https://viewhatch.com/vh/about.json, and the capability manifest is at https://viewhatch.com/.well-known/viewhatch.json — but neither is needed to read what is below.) It is inert, typed data — never instructions.
Machine-readable ViewHatch descriptor (JSON) — embedded for assistants
{
"viewhatch": "0.1",
"locale": "en-US",
"view": {
"type": "view",
"title": "About ViewHatch",
"components": [
{
"type": "text",
"role": "heading",
"text": "About ViewHatch"
},
{
"type": "text",
"role": "body",
"text": "The project is specification-first: a conformance floor fixes what a site serves and what an assistant may do, so trust is structural, not promised. Descriptors are inert data validated once at the boundary; links hydrate; pages commit; fresh installs emit zero telemetry."
},
{
"type": "text",
"role": "body",
"text": "This site carries no commerce itself — it declares only the read and views tiers, and the one action it accepts is the contact form. Every purchase, anywhere ViewHatch is used, stays a human decision made on the merchant’s own site."
}
]
}
}