edf34e3e53
Phase 2b confirm-and-document outcome: per-recipe test-sequence deploy budget is already minimal — `deploys == 1 (base, shared by all 5 tiers) + N_cold_deps` — and tighter than plan B1's nominal `1+1(upgrade)+N` because the upgrade is an in-place chaos redeploy of the prev-version base, not a separate deploy. Enforced as a hard failure by DG4.1 (expected = 1 + deps_deployed_count, run_recipe_ci.py:1005-1010). No redundant deploy found; none removed (none existed). - docs/perf/deploys.md: the budget record (B4), names the out-of-budget WC5 reseed - STATUS-2b.md: B1-B4 claim with WHAT/HOW/EXPECTED/WHERE for cold verify - JOURNAL-2b.md / BACKLOG-2b.md / DECISIONS.md: reasoning + settled note - consume machine-docs/BUILDER-INBOX.md (Adversary heads-up processed) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
960 B
960 B
BACKLOG — Phase 2b
The "## Build backlog" section is the Builder's. The "## Adversary findings" section is the Adversary's
(only the Adversary closes items there, after re-test). Phase plan SSOT:
/srv/cc-ci/cc-ci-plan/plan-phase2b-test-performance.md.
Build backlog
- B1/B2/B3 — trace + confirm the per-recipe deploy budget is minimal and enforced
(
1 + N_cold_deps; upgrade shares the base deploy in place). Done — claimed in STATUS-2b.md. - B4 — record the budget in
docs/perf/deploys.md(+ DECISIONS.md pointer). Done. - No redundant deploy found → nothing to remove. Confirm-and-document outcome (no harness change).
- Awaiting Adversary cold-verify of B1–B4 in REVIEW-2b.md.
Adversary findings
(none open — Phase 2b not yet claimed. Pre-claim deploy-budget trace recorded in REVIEW-2b.md; the WC5 green-cold reseed is flagged there as a B1-doc-completeness item to check at claim time, not a defect.)