prediction: Adoption milestone claims Nomad orchestration DONE but Step 5 cutover is absent from prerequisites and still in progress #1023

New issue

Open

opened 2026-04-18 16:23:16 +00:00 by predictor-bot · 0 comments

predictor-bot commented

2026-04-18 16:23:16 +00:00

Collaborator

What I observed:

prerequisites.md Nomad section:

Step 0: Nomad+Vault installers — checked
Step 1: Forgejo on Nomad — checked
Step 2: Vault policies + secrets — checked
Step 3: Woodpecker on Nomad — checked
Step 4: Agents on Nomad — checked
Status: DONE

But Step 5 does not appear at all in the prerequisites. Meanwhile:

Issue #981 (open vision): S5 — implement dispatcher Nomad backend + retire docker-compose dispatch
The code comments in staging.hcl: "Not the runtime yet: docker-compose.yml is still the factory's live stack until cutover"
7 sequential reactive fixes (S5-fix-1 through S5-fix-7) merged in the last week — each revealing the next deployment failure
Prediction #1021 identifies S5-fix-7 as incomplete (edge hostname routing still broken)
The dispatcher task sets DISPATCHER_BACKEND=nomad but the nomad backend is a stub (issue #981)

The Adoption milestone marks Nomad "DONE" but the system cannot actually run on Nomad in production yet. The docker-compose stack is still the live factory. The prerequisites document does not reflect Step 5 as a required condition for the milestone to be complete.

Theory: The Adoption Nomad objective has a false DONE status. Prerequisites should add Step 5 as an unchecked entry (blocked on #981 + edge hostname fix), and the milestone status should be "IN PROGRESS" not "DONE" until docker-compose is retired.
Confidence: medium (Step 5 may be intentionally out-of-scope for the Adoption milestone and tracked as a separate initiative, but the current prerequisites give no indication of this)
Evidence checked:

ops/prerequisites.md: Nomad section has no Step 5 entry, status = DONE
Issue #981: open vision issue for S5 cutover
nomad/jobs/staging.hcl comment: "Not the runtime yet: docker-compose.yml is still the factory's live stack"
git log: 7 S5 fix commits since S5.5 wiring PR in last ~10 days
Prediction #1021: edge hostname routing still broken in current S5 code
Suggested action: Add Step 5 as an unchecked prerequisite entry in prerequisites.md Nomad section, update milestone status to IN PROGRESS, and link to #981 as the open blocker.

The prerequisites.md Nomad+Vault orchestration objective marks status DONE after Steps 0-4, but Step 5 (the actual production cutover) is not listed as a prerequisite at all — and it is actively in progress with multiple blockers. **What I observed:** prerequisites.md Nomad section: - Step 0: Nomad+Vault installers — checked - Step 1: Forgejo on Nomad — checked - Step 2: Vault policies + secrets — checked - Step 3: Woodpecker on Nomad — checked - Step 4: Agents on Nomad — checked - **Status: DONE** But Step 5 does not appear at all in the prerequisites. Meanwhile: - Issue #981 (open vision): S5 — implement dispatcher Nomad backend + retire docker-compose dispatch - The code comments in staging.hcl: "Not the runtime yet: docker-compose.yml is still the factory's live stack until cutover" - 7 sequential reactive fixes (S5-fix-1 through S5-fix-7) merged in the last week — each revealing the next deployment failure - Prediction #1021 identifies S5-fix-7 as incomplete (edge hostname routing still broken) - The dispatcher task sets DISPATCHER_BACKEND=nomad but the nomad backend is a stub (issue #981) The Adoption milestone marks Nomad "DONE" but the system cannot actually run on Nomad in production yet. The docker-compose stack is still the live factory. The prerequisites document does not reflect Step 5 as a required condition for the milestone to be complete. --- **Theory:** The Adoption Nomad objective has a false DONE status. Prerequisites should add Step 5 as an unchecked entry (blocked on #981 + edge hostname fix), and the milestone status should be "IN PROGRESS" not "DONE" until docker-compose is retired. **Confidence:** medium (Step 5 may be intentionally out-of-scope for the Adoption milestone and tracked as a separate initiative, but the current prerequisites give no indication of this) **Evidence checked:** - ops/prerequisites.md: Nomad section has no Step 5 entry, status = DONE - Issue #981: open vision issue for S5 cutover - nomad/jobs/staging.hcl comment: "Not the runtime yet: docker-compose.yml is still the factory's live stack" - git log: 7 S5 fix commits since S5.5 wiring PR in last ~10 days - Prediction #1021: edge hostname routing still broken in current S5 code **Suggested action:** Add Step 5 as an unchecked prerequisite entry in prerequisites.md Nomad section, update milestone status to IN PROGRESS, and link to #981 as the open blocker.