Skip to content

Norn v3 launch state ​

Status reviewed 2026-11-16 UTC. The DO staging live online upgrade and pilot retirement are complete. The online upgrade passed on 2026-11-16; exact-scope provider readback at 15:27 UTC confirmed retirement. Management remains available for future Fleet work.

Current evidence ​

ItemVerified stateLimit
Deployed platformLive run 43852466595 upgraded all three controls from signed fa301fa5 to cdf2081e through Fleet executor bdf522cc. Its 19-event receipt ended online-qualified.This qualifies the existing Fleet platform upgrade, not fresh creation, workload resizing or every application.
ContinuityThe accepted window contains 399 management-observer samples and 673 separate public probes with no observed workload outage, API handoff gap or sampling gap. API ownership moved Control 03 to Control 01.Nine later public-probe timeouts occurred outside that window; their cause is unresolved. The last public probe succeeded and management observation remained policy-healthy. Do not describe the entire 45-minute monitor as uninterrupted.
Signed release and admissioncdf2081e passed twelve qualification jobs and publication. Exact-pair qualification 43851271049 and state readback 43851955369 admitted the live operation.Future operations still require fresh source, state, owner and signature bindings.
Recovery and final cleanupPreparation-only recovery and the succeeding upgrade have retained evidence off-Fleet.The controller saved its success receipt and cleared the active journal at 12:25 UTC; all three host-authority retirement receipts are retained. The worker and observer are stopped. PR #1089 repaired directory validation; PR #1090 repaired original-source Git ownership. These repairs are merged; the accepted upgrade was not rerun.
Pilot retirementOwner-authorized exact-ID doctl retirement complete. Nine Fleet Droplets, both application database clusters, dedicated ingress load balancer, Fleet firewalls/VPC and management-to-Fleet peering are absent. Two management Droplets remain active, management database online; runner pinned SSH succeeds and authority is online on Tailscale.The saved-plan retirement controller was not live-qualified. Spaces, state, evidence and credentials were retained; ordinary Fleet apply is disabled to prevent accidental recreation. Authority API health was not established by this readback.
Self-hosted strategyThe recorded direct-host deployment met the signed-V3/API/responding-workload bar on 2026-11-10.Its repair and Git admission follow-ups have an independent lifecycle; Fleet resizing does not apply.

Pilot complete and follow-up boundary ​

The launch-critical online-upgrade and disposable-pilot retirement milestones are complete. GitHub billing/capacity still blocks required CI for retirement controller prerequisite PR #1091, but no longer blocks this retired pilot. The owner explicitly chose direct doctl cleanup. Do not treat that cleanup as saved-plan controller qualification. Future creation requires deliberate state refresh, source review and plan approval before re-enabling ordinary Fleet apply; retained state is historical.

Application nodes and workload sizes were unchanged during the platform upgrade. Fresh-Fleet creation, workload admission, mixed-version resizing and stateful compatibility continue after this pilot milestone.

See release program milestones and the Fleet retirement runbook for the workstream overview and execution boundary.

Historical section links

The dated records below are archived evidence, not current launch gates.