Chain · Machine-readable — when the asker is an agent

L0 · Vision

interpretation-economy — the web shifts from attention to interpretation economy: "they don't ask you — they ask an AI"; an agent won't fill gaps charitably, it needs structured evidence or you're flattened into the category mean. why-now — MCP as the enabling substrate.

L1 · Promise

The persona is consumable not only by humans in a chat window but by other people's agents, as structured evidence over a standard protocol.

L2 · Requirements (journeys & features)

The service-handle tool inventory in features-and-journeys (StandMeet-as-MCP-server, confusables) + the admin API·MCP surface; (no dedicated visitor journey — the "visitor" here is a machine; flag this as a journey gap inherited from features-and-journeys).

L3 · Design decisions

This chain lives entirely on the service handle plane — StandMeet as MCP server (see the two-planes definition in capabilities); the agent's own capability plane is a different thing. The three platform orientations — host / connector-owner / as-MCP-server (as-mcp-facade); the entry-agnostic principle — the facade is "just another consumer" of the neutral boundary (entry-agnostic-agent); auth = owner-keypair-auth (Sigv1; ⚠ caller-not-message binding); MCP standard copied verbatim, no private protocol.

L4 · Engineering artifacts

routes/mcphandle (registerTools ← OwnerMCPBindings, backend/internal/capabilities/capreg/registry.go), owner_keypairs table (schema.sql:163), mcpclient transports, and the owner-side client package @standmeet/mcp-client (sdk/packages/mcp-client; version-skew advisory 4442e8fe9, 2026-09-06); the passive machine-readable face = /robots.txt + a dynamic /sitemap.xml that lists the owner page, indexed wiki landings and live microsites (701bf1648, 2026-09-05), per-microsite seo_title / seo_description injected into the served head (79a276cce) with Open Graph + Twitter share-card tags (b19d8db39) — the global SEO settings were removed on 2026-09-06 (7037a434e; SEO follows each microsite, microsite.set_seo). No RSS exists.

L5 · Verification

MCP auth e2e; red contracts of that style don't exist for the facade — verification thinner than the ACL chain. The public face is covered: e2e/test/seo-feeds.spec.ts (robots + sitemap, microsites included), microsite-per-page-seo.spec.ts.

Status & gaps

Facade + Sigv1 landed; the DEEPER promise (structured evidence for agent readers — schema.org-ish profile, citable claims, agent-legible provenance) still has no design — the only JSON-LD in the codebase is the job-ingest parser (owner/jobs/fetch/jobposting_jsonld.go), nothing is emitted; the interpretation-economy thesis implies agent-readers hit the PUBLIC face too, where robots / sitemap / OG tags now exist and are tested, but carry no claims. This chain is vision-strong, engineering-thin — inverse of the platform work.