What we have shipped, in order.

Architecture 1: develop → review → gate, proven green

The first member PR ran the whole loop: manifest, install, tests, contract, lint, security, advisory AI review, deterministic gate. Policies took ownership of the contract schema so members can't drift it.

Copier scaffold + automated fleet migration

The "Use this template" button was retired for a Copier template with provenance. A registry bot now opens copier update PRs across the fleet weekly and never auto-merges; version-scoped branches protect human conflict resolution.

• FastAPI /api + MCP /mcp in one deployment
• Zero-config Railway deploys

Public site + RFC 001

agents.turingplanet.ai went live with a 30-second try. RFC 001 set the migration and deploy model: in-place adoption for existing projects, opt-in registration from the manifest, a pull-model hosting allowlist.

Platform hosting under one wildcard domain

A single edge router and deployments.yaml as the allowlist. Merging a line deploys and routes; removing it tears down. Pilot member hello-fleet served from hello-fleet.agents.turingplanet.ai.

Self-service registration, both directions

/register and /deregister: the member consents in their manifest, the platform verifies the App is installed, and opens the registry PR with its own credentials. Two teardown incidents produced the guards that now exist.

Cross-account hosting + /fix-suggestion

First member from outside the org hosted live. On any failing PR check, the platform's model root-causes the failure and posts the smallest concrete fix, advisory.

Fleet gateway: one MCP endpoint for everyone

Every hosted agent aggregated behind mcp.agents.turingplanet.ai/mcp, tools prefixed by slug, stateless proxy, roster maintained by the deploy reconciler.

Fleet status page + admin quota endpoint

A weekly snapshot of scaffold versions, gate results, hosting health and review quota, with a "things for me to do" list that links straight to the PR or run.