# Public launch boundary

Recorded: 28 August 2026

Deployment state: public production active; truth and 404 correction included in this release; first scheduled run, notification receipt, two-way mail test and 48-hour observation pending

## Source and release

The approved release at source revision `42b799799049b8448968128e7f0018bbcbfe218a` became the public production release. GitHub production-build run `32971136878` passed for that release source. The default branch contains the source through merge commit `fe9446b7773c3bb9799278bd176d535b7e37e381`, and post-merge default-branch CI run `33183738202` passed.

The shared root Caddy configuration was backed up, changed by exactly one semantic import from the Kingsbury preview fragment to the production fragment, validated and reloaded. The initial cutover release used the same checksum-bound installer and guarded rollback mechanism rehearsed on the earlier release recorded on 26 August; this does not claim that rollback from the exact cutover release was executed.

At the post-cutover checkpoint, the operator ledger reconciled the exact cutover state against the retained off-server package:

- initial cutover release: `20260826T125711Z-42b799799049` at `/srv/kingsbury/releases/20260826T125711Z-42b799799049`;
- archive SHA-256: `e9c2c5414f90c795065ee26a76e6b0943c7919832675e9c52dea7255978f3b74`;
- release-contract SHA-256: `258fc94da4628016b0937b3e3daedd664e2be55bd517abf89561338703a7199e`;
- retained rollback candidate: `20260826T124242Z-2a9d966ccb9e`.

All 43 recorded file checksums matched the retained package. This proves the recorded cutover artefact and then-retained rollback candidate; it does not turn the earlier rollback rehearsal into a rehearsal of that exact release or identify whichever release is active later.

## Domain and network boundary

The apex `A` record moved to `72.62.212.215` with TTL 600, and `www` became a CNAME to `kingsbury.io` with TTL 3600. No `AAAA` record was introduced. The other 12 protected and recorded DNS records, including the Microsoft 365 boundary, were unchanged.

The Hostinger firewall allows SSH, HTTP and HTTPS, drops unmatched traffic, and leaves the private preview port closed publicly. A second SSH connection succeeded after activation. The six applications already sharing Caddy matched their recorded cutover status codes at the post-change check.

## External verification

Caddy obtained trusted certificates for the apex and `www`. The initial production verifier passed from the operator machine, including the expected apex address and absence of IPv6, trusted HTTPS, path-and-query-preserving redirects, required routes, the RSS feed, a real 404 status, homepage cache and security headers, and the protected mail-record baseline. That verifier did not inspect the error response body or its headers; a later check found that Caddy returned an empty 404 response outside the intended header boundary.

The release containing this record corrects that gap: the Caddy error route serves the branded page with the normal security headers and an explicit `noindex` boundary, while the monitor now checks the exact release source, release contract, `www` CNAME, both sitemap layers, every sitemap page and its canonical, the updated Proof, launch evidence, and the complete 404 response. A passing run against that strengthened public boundary had not yet occurred when this record was authored and remains a post-release check. HSTS was deliberately absent during the observation window and is not claimed as a passing header.

GitHub **Public uptime** [run `33184013603`](https://github.com/Kingsbury-io/Kingsbury/actions/runs/33184013603) then passed from outside the VPS using verifier code from merge commit `fe9446b7773c3bb9799278bd176d535b7e37e381`, triggered by repository actor `Kingsbury-io`; Kevin Ingrey is the accountable operator. That verifier did not compare the served release with its checked-out source, so this run does not prove the active static release was built from `fe9446b`. Artifact `9690900298` retains the result until 11 September 2026, subject to private repository access. Repository variable `KINGSBURY_MONITOR_ENABLED` is enabled for the three-hour schedule. The first strengthened and non-skipped scheduled runs, and confirmation that the accountable operator receives failure notifications, had not yet occurred when this record was written.

## Limit

This record supports the claim that Kingsbury's versioned release is served from its production domain, passed an external boundary check, and coincided with the co-hosted applications matching their recorded cutover status codes at the post-change check. It does not establish inbox delivery, receipt of monitor-failure notifications, completion of the 48-hour observation window, a live DNS rollback rehearsal, sustained co-hosted-application health, readership, repeated use or downstream effect. Vercel remains available as a temporary rollback boundary while those launch checks remain open.