Skip to content

V3 release program milestones ​

Status reviewed 2026-11-16 UTC. The DO online-upgrade and pilot-retirement milestones are complete. Upgrade and terminal cleanup succeeded on 2026-11-16; provider readback at 15:27 UTC confirmed exact Fleet absence with management retained. The self-hosted deployment met its recorded acceptance bar on 2026-11-10 and has an independent lifecycle.

Launch milestones ​

MilestoneStateExit evidence
Publish the qualified candidateCompleteSigned cdf2081e passed twelve qualification jobs and immutable publication.
Qualify and admit the exact pairComplete for the live executorCompatibility 43851271049, protected owner-private state readback 43851955369, fresh active-owner evidence and a signed intent admitted the actual upgrade on Fleet executor bdf522cc.
Recover the earlier preparation holdCompleteThe controller fenced the held attempt before member invocation, proved all controls still on the old signed release, retained evidence and retired its runner. The succeeding upgrade used a fresh intent. This recovery was not itself upgrade qualification.
Accept the DO online upgradeComplete, 2026-11-16Live run 43852466595 ended online-qualified. All three controls were verified on cdf2081e, passive controls first and the API owner last. API ownership moved Control 03 to Control 01. The accepted window recorded 399 observer samples and 673 separate public probes without observed workload outage, API handoff gap or sampling gap.
Finish terminal controller cleanupComplete, 2026-11-16Fleet PR #1089 repaired handoff-directory validation and installed a separately pinned adapter. PR #1090 repaired Git trust for the verified original and repair checkouts. Both are merged. The controller saved terminal-and-runner-retired success at 12:25 UTC, cleared its active journal, and retained all three host-authority retirement receipts. Worker and observer are stopped. The accepted upgrade was not rerun.
Retire disposable stagingComplete, 2026-11-16Owner-authorized exact-ID doctl deletion followed by provider readback: nine Fleet Droplets, two application databases, dedicated ingress load balancer, Fleet firewalls/VPC and Fleet-to-management peering absent. Two management Droplets active, management database online, runner reachable over pinned SSH, authority online on Tailscale. Spaces, state/evidence and credentials retained; ordinary Fleet apply disabled. This is direct retirement evidence, not live qualification of the saved-plan retirement controller.

The longer 45-minute public monitor recorded nine timed-out probes after the accepted upgrade window, among 2,679 probes. Its last probe and a fresh public check succeeded; management observation remained policy-healthy. Their cause is unresolved. Retain them separately from the zero-failure upgrade window.

The owner chose direct doctl retirement while GitHub billing/capacity blocks required CI for Fleet PR #1091. That prerequisite and live qualification of saved-plan retirement remain follow-ups; they do not reopen this completed pilot. Authority API health and billing settlement were not established by the final infrastructure readback.

Parallel workstreams ​

WorkstreamCurrent evidenceNext proof
Existing DO platformLive online upgrade 43852466595 accepted on 2026-11-16; all three controls verified on signed cdf2081e with workload continuity.Pilot retired with management retained. Future recreation needs deliberate refresh and reviewed plan before ordinary apply is re-enabled.
Self-hosted directRecorded deployment acceptance bar met on 2026-11-10. Self-hosted operation is independent of the Fleet.Separate repair and Git-driven workload admission follow-ups. No Fleet resizing.
V3 workload admissionNegative admission, durable replay, and offline input/provenance checks exist. Current source and tests do not establish a live controller-admitted canary receipt.Verify protected inputs and credential provenance, then bind a responding workload to durable same-intent admission receipts. This follows the platform launch.
Fresh-Fleet creationGeneral and Stateful roles, topology checks, authority models, and default-off API work exist. The published candidate includes the new source. No fresh provider creation is qualified.Connect one-use grants to the provider executor and protected workflow. Qualify partial inventory, ambiguous effects, recovery, and bootstrap. Creation may stay undeployed until needed.
Workload resizingDisposable real-Nomad and etcd-backed recovery checks and mixed-version capacity models exist. No live DO resize is qualified.Complete real executor, health, ingress, and old-cohort-stop proof, then qualify a stateless DO resize. Keep stateful compatibility separate.
Controller recoveryThe earlier preparation hold was recovered before any member invocation. The succeeding live upgrade has retained signed intent, authenticated artifact, journal and observation evidence.Terminal handoff and worker/observer cleanup are complete. Keep offline crash models distinct from live fault-injection proof.
V2-only retirementCleanup follows successful V3 adoption.Remove unused V2 code and tests while preserving versioned contracts still used by V3.

Evidence and operating detail ​

Launch state is the current status reference. The Fleet readiness record tracks implementation evidence. Execution milestones retain the broader feature program. The release runbook contains procedures. Launch history and the archive below preserve dated results and failed attempts. Use the executor qualification rubric when reviewing controller evidence. It distinguishes model, component, disposable, recovery, and live proof without changing these milestone states.

The complete program still requires verified input contracts, offline failure coverage, live readiness checks, controller receipts, postflight, and recovery for every supported lane. Completing the narrower online platform launch does not complete those follow-on workstreams.

Historical section links

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