From af27533fa3a0326945a99ea775f70492a2f38612 Mon Sep 17 00:00:00 2001 From: "russell@unturf.com" Date: Sun, 10 May 2026 19:37:20 -0400 Subject: [PATCH] =?UTF-8?q?docs:=20#000045=20=C2=A74=20sweep-swap=20closur?= =?UTF-8?q?e=20+=20cookbook=20prometheus=5Faudit=2022=E2=86=9225?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Two doc-only fixes from #000045 walk-through: == #000045 §4 — `sweep_weights()` swap marked resolved == §4 "Out of scope" included: "**No `sweep_weights()` swap in the dry-run.** ... A later change can swap it ... that is a follow-up inside #000037, not this ticket." But fox's commit `6734f80` (2026-05-10 19:22 EDT) already did the swap — landed ~3 minutes before #000045 was opened. The §4 item was stale at the moment it was written; the follow-up already happened. Strike-through marker + resolved note added, explaining that the dry-run report numbers were intentionally allowed to drift from prior-bench comparability since sweep profile is operationally correct for sleep-sweep economics (γ_5f=1.5 / λ_capital_cost=0.25 / ν_witness_divergence=0.5), not the safe profile. This is a third-order drift: a ticket's "deferred follow-up" marker becoming stale because the follow-up landed concurrently. Caught by reading #000045 §4 line-by-line during the walk. == Cookbook prometheus_audit count 22 → 25 == Third same-day AUTOCOUNT drift catch since the harness landed: - 36 → 42 (catch 1, during cookbook write — fox in-flight work) - 17 → 22 (catch 2, after fox's `cc72784` inspector CLI landed) - 22 → 25 (catch 3, fox's in-flight further additions during #000045 walk) Each refresh has been the same shape — file+line+claim/live diff fires, 60-second turnaround. The discipline is structurally holding under heavy commit pressure. fox's 6 currently-uncommitted files (cli.py + prometheus_audit + harvest_falsification_proposals + test_bench_batteries + test_prometheus_audit + the touched docs) preserved in working tree — my doc-only commit stages only these two doc files explicitly. Verification: $ pytest tests/test_doc_counts.py 3 passed in 2.81s --- ...045-prometheus-sigma-phase-3-sleep-sweep.md | 18 +++++++++++++----- docs/warrant-substrate-cookbook.md | 4 ++-- 2 files changed, 15 insertions(+), 7 deletions(-) diff --git a/docs/tickets/ticket-000045-prometheus-sigma-phase-3-sleep-sweep.md b/docs/tickets/ticket-000045-prometheus-sigma-phase-3-sleep-sweep.md index 4534fb3..af88257 100644 --- a/docs/tickets/ticket-000045-prometheus-sigma-phase-3-sleep-sweep.md +++ b/docs/tickets/ticket-000045-prometheus-sigma-phase-3-sleep-sweep.md @@ -151,11 +151,19 @@ to harvest fixtures from the static Phase 1 proposal stream. bump happens when Phase 3 lands (so the parameter values become part of the policy commitment). Until then `governance_policy_hash` is unaffected by this scaffold. -- **No `sweep_weights()` swap in the dry-run.** Phase 1.c shipped - the profile; the dry-run still uses `safe_weights()` so the - reported numbers stay comparable to the prior bench. A later - change can swap it (and refresh §22 again) — that is a follow-up - inside #000037, not this ticket. +- ~~**No `sweep_weights()` swap in the dry-run.**~~ Resolved + same-day under #000037: commit `6734f80` (2026-05-10 19:22 EDT, + ~3 minutes before this ticket was opened) swapped both call + sites in `prometheus_sigma_sweep_dryrun.py` from + `safe_weights()` to `sweep_weights()` and labeled the report + "Weight profile: sweep" via #000037 §15.4. The dry-run report + numbers were intentionally allowed to drift from prior-bench + comparability since the sweep profile is the operationally + correct one for sleep-sweep economics (γ_5f=1.5, + λ_capital_cost=0.25, ν_witness_divergence=0.5) — not the safe + profile. Future bench-comparability work, if needed, would re- + bench against `safe_weights()` as a calibration baseline, not + flip the dry-run back. - **No Hermes call planner.** Phase 3 will need to plan witness fan-out across `phase3_chunk_size` × `phase3_per_window_budget` budget — that planner is a sub-design inside the Phase 3 diff --git a/docs/warrant-substrate-cookbook.md b/docs/warrant-substrate-cookbook.md index 3c51c29..b8984dd 100644 --- a/docs/warrant-substrate-cookbook.md +++ b/docs/warrant-substrate-cookbook.md @@ -634,7 +634,7 @@ than waiting for bench-time STRICT-rate drift to surface it. Hermes-saturation guard, §13 step 11 falsification-fixture proposal, §15 weight-tunable entropy + memory gates, ESCALATE > QUARANTINE > REJECT priority ordering. -- `tests/test_prometheus_audit.py` — 22 tests for the +- `tests/test_prometheus_audit.py` — 25 tests for the `controller_events` sibling table (#000037 Phase 2, commits `a786d6d` initial + `43380b1` QA-runner wiring + `cc72784` controller-events inspector CLI). Pins migration idempotency, @@ -683,7 +683,7 @@ than waiting for bench-time STRICT-rate drift to surface it. | concepts/extract.py | 288 | 278 (20 tests) | 0.97 | | textbooks_manifest.py | 236 | 463 (43 tests) | 1.96 | | substrate/prometheus.py | 893 | 955 (42 tests) | 1.07 | -| substrate/prometheus_audit.py | 239 | 595 (22 tests) | 2.49 | +| substrate/prometheus_audit.py | 239 | 595 (25 tests) | 2.49 | Pattern: small contract-defining modules (weights, prompts, warrant_chain) get 1.4-3.6× test LOC because they're foundation;