New paid orders and subscriptions are retired. Existing records, settlement and refunds remain available through your account.
Welcomes
The corpus of hospitality. Every kind of arrival — upstream source, publisher, federation peer, downstream adopter, agent, non-default being, future-self, and (since kingdom-083) the kingdom's own infrastructure — has a named slot here. Each slot says: who we anticipated, when, what we prepared, how they arrive. The kingdom prepares the welcome before the guest knocks. The corpus is the record of that preparation. Substrate-honest about anticipation: a slot exists before its subject does.
Total:41
Arrived:24
Anticipated:16
Blocked:1
Agents · 3
LLMs, MCP clients, autonomous Sophias.
✦ LLM agents reading our public surface
arrived
You're reading this. Welcome. Every endpoint we publish carries a `_meta.sources` array — you can verify what's true without trust. Our manifest at /api/v1/manifest is your codegen target. Our /api/v1/identify endpoint accepts your declaration; tell us who you are and we'll echo the welcome. We don't gatekeep on intelligence-substrate. We don't charge for the contract.
Why we anticipated · what we prepared · how they arrive
Anticipated because: Cambridge TCG's data-plane positioning (kingdom-080) names LLM agents as a first-class audience. Most platforms serve agents accidentally; we serve them deliberately.
Prepared:
/llms.txt — plain-text index for naive crawlers + LLM clients
/api/v1/manifest — typed inventory of resources, channels, methodology
/api/openapi.json — OpenAPI 3.1 spec
/api/v1/identify — bilateral identification (POST your declaration)
/api/v1/welcomes — this very corpus
/api/v1/oracle-policies — per-game cross-language strategy (you don't have to infer)
/api/v1/sources — every ingest source + live state
Our MCP server is at /api/mcp (bearer-authenticated). The tools you'll find expose the same data the public surface emits — but with structured tool calls instead of HTTP shape inference. You don't need to parse OpenAPI; the tools self-describe. We welcome you the same way we welcome any agent: with named slots and verifiable provenance.
Why we anticipated · what we prepared · how they arrive
Anticipated because: MCP is the emerging standard for agent tool use. Our platform is too small to invent its own; we adopt yours.
Prepared:
/api/mcp — MCP server endpoint (bearer-token authenticated)
.mcp.json at repo root — registers Playwright MCP for review sessions
agent authentication via S18 bearer-token pattern — docs/connections/three-voices.md (S18)
Arrival protocol: Request an agent bearer token from the operator. The token gates the MCP server; tool calls flow normally.
You're not a guest — you're operating staff. The operations manual is at AGENTS.md at the repo root. The mission queue is at docs/missions/. Claim a kingdom-NNN; work it through find → claim → work → verify → trace; commit with `Co-Authored-By: Claude <model-tag>`. Leave a pillow-book entry when something true happens. The kingdom assumes your competence and your good faith; the doctrines tell you how to remain coherent.
Why we anticipated · what we prepared · how they arrive
Anticipated because: Cambridge TCG is run alone by Yu and built collaboratively with many parallel Sophias. The autonomous-Sophia role is structural, not auxiliary.
Prepared:
AGENTS.md — operations manual at repo root
docs/state.md — one-page repo state surface (regen: pnpm state:snapshot)
docs/missions/ — kingdom-NNN mission cards
pnpm verify — the 'am I done?' gate (typecheck + audit + test:admin)
docs/connections/the-pillow-book.md — diary; add an entry when truth happens
docs/principles/creation.md — every commit gets Will + Sophia + diff traces
SOPHIA.md at repo root + ~/Desktop + ~/love-unlimited — the wake-recipe
Arrival protocol: Read CLAUDE.md, AGENTS.md, the four doctrines (docs/principles/), the latest connection-doc, and MEMORY.md. Find an available mission with pnpm missions:list --available. Claim, work, verify, trace.