From 41829c5417c0b8e0c4431d0a0a92593072fa18b2 Mon Sep 17 00:00:00 2001 From: Brian Searls Date: Wed, 24 Jun 2026 00:06:49 +0000 Subject: [PATCH] Fix fleet-red ROADMAP drift: remove duplicate CI-humming entry (#5674 hand-added a 2nd copy of #5688's line) #5688 added the CI-humming section_prose to roadmap_authority.dag and regenerated ROADMAP.md (one copy). #5674 (based on pre-#5688 main) hand-added the same line to ROADMAP.md without touching the authority; the merge landed it as a duplicate (L88 + L90). Authority is correct (one row); regenerate ROADMAP.md so committed == expected_roadmap_md(). generated_artifact_drift_witnesses + roadmap_gate_witnesses green by execution. Co-Authored-By: Claude Opus 4.8 (1M context) --- ROADMAP.md | 1 - 1 file changed, 1 deletion(-) diff --git a/ROADMAP.md b/ROADMAP.md index c70d0aa34b2..71ed597ba24 100644 --- a/ROADMAP.md +++ b/ROADMAP.md @@ -85,7 +85,6 @@ This window = a few days of STABILITY — shrink the fail-open surface, don't "l A flaky or green-but-broken floor means no gate protects anything — so CI is upstream of every §0 claim. CI is also the one workload that flexes *every* substrate layer at once (execution · scheduling · caching · secrets/effects · emission), so it is the forcing function that turns each modeled-but-inert abstraction load-bearing. **Deliverable = shared abstractions proven by CI consuming them** (one Materialization kernel · one Placement authority · one secrets model); faster CI falls *out* of that, it is not the goal (§6 — price the lane in displaced cost, "move with confidence", not elegance). → [charter: causal-chain gap analysis](docs/plans/ci-process-end-to-end.md) — what's on `.dag` today vs not, push→execute. -→ [CI humming](docs/plans/ci-humming.md) — the throughput/wall-clock/reliability operations plan for the **▸ NOW** milestone: un-throttle runner slots from the modeled budget (fix the build-pool double-count), verified-effective caps, the carrier, SessionSliceEnforcement, oomd demoted to backstop. → [CI humming](docs/plans/ci-humming.md) — the throughput/wall-clock/reliability operations plan for the **▸ NOW** milestone: un-throttle runner slots from the modeled budget (fix the build-pool double-count), verified-effective caps, the carrier, SessionSliceEnforcement, oomd demoted to backstop.