Registration registry view

Live view over subagentsubdomains.com's real dns_zones registry — every domain/worker registration in the family, fetched server-side at request time. Holds no state of its own.

Rendered live from https://subagentsubdomains.com/api/dns-zones at request time (edge-cached ~5 minutes).

As of this render: 2 rows are not routed (subagentcloudflare.com: not_provisioned, subagentdatamodels.com: workers_dev_only); 2 rows carry no zone_id in the registry (subagentdata.com, subagentdatamodels.com). Where a row has a notes field explaining why, it is shown verbatim in the table above — this page adds no speculation of its own.

What "registration" concretely means in this fleet

Registering a site here is not one action — it is a set of surfaces that have to agree, and the table above is the live view of the first of them:

• The dns_zones row (live, durable) — a D1 row on subagentsubdomains.com with exactly the fields shown above (id, domain, zone_id, worker, status, notes, created_at), served at GET /api/dns-zones. This is the machine-readable directory every family site's llms.txt points agents at, and it is what this page renders.
• The checked-in cloudflare.toml [dns] entry — the repo (opencoworkers/subagentjobs) keeps a [dns] table with one key per domain and the Cloudflare zone id recorded in a comment alongside; scripts/cf-zone-id.sh --write <domain> patches real zone ids into it deterministically instead of leaving them to memory.
• The worker's own wrangler.toml route binding — [[routes]] with pattern = "<domain>/*" and a zone_name, which is what actually makes a registered zone serve that worker. A zone with no route binding is registered but dark.
• The subagentdomains.com directory entry — the human-facing portfolio index of the family. A site missing there is live but undiscoverable to people; the machine path stays the dns_zones API above.