Runs / run
ChurchOS Build 50 / FSB-IST synthetic tailnet dogfood
The Windows Build 50 custody candidate is serving a synthetic, tailnet-only dogfood surface for FSB-IST with health, login, source identity, and peer reachability checks recorded.
URL [private tailnet endpoint] Candidate HEAD 200175e13def53d39ef41ef103db39c19738d62b and tree 5ab837cea078349d704f5019ba968b6b5ccd0c88 are source-verified. Profile is synthetic_private_church with an isolated synthetic database; fsbist tailnet ping, /readyz, and /login pass. The baked source marker remains churchos-1.4-build48-public-release-r2 and is recorded as a mismatch. No public funnel, signing, upload, deployment, production data, or release approval is involved.
Catalog snapshot: . States and claims below belong to this record; current availability is unverified.
Recorded catalog state
LIVE
2026-09-18 · TCO Tailnet Dogfood
SERVING_SYNTHETIC_DOGFOOD / TAILNET_ONLY / NO_RELEASE_APPROVAL
3 evidence pointers are preserved in the local Lab. Their paths and review controls remain private.
Return to the catalog →Public claim surface
What this object says
- 01FSB-IST tailnet ping passes.
- 02The dogfood /readyz and /login endpoints return HTTP 200.
- 03The runtime uses a synthetic private profile and isolated synthetic database.
- 04The serving candidate source commit and tree match the Windows custody identity.
- 05The baked source marker remains the older churchos-1.4-build48-public-release-r2 and must not be hidden.
- 06Tailnet dogfood is not a shipped release or production proof.