chore(run-16r2): board revision under instrument v2 (capacity-adjusted) - #47
Merged
Conversation
…ed re-assessment Re-assessment of run-16 under SKILL §6b (beadle PR #45), operator-ratified. Verdict revised DRIFTING (v1) → ON-COURSE (v2) with a watch on selection depth (shallow) and the A4 lane. All v2 bands GREEN: PR acceptance 71% zero rejections (agent baseline 37-45%), cadence 5 attention windows in 3 weeks rising, merge latency <=2 windows. A4 re-denominated to attention windows (5/5 untouched; 7 runs shadow). The v1 prediction FAILURE is preserved verbatim and never re-scored; under v2 registration rules its 2-day horizon would have been invalid at registration. Regression gate PASS: all 423 issue refs, 22 headings, 31 controls preserved vs the before-r2 snapshot. Freshness: #754-#756 arrived post-enumeration — run-17 intake. Refs: aae-orc#65
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
PR #45 changed the instrument; this PR is the acceptance record of the first board computed with it. Run-16's v1 verdict (🔴 DRIFTING, unqualified) measured two part-time maintainers against a full-time standard on beadle's own cadence; re-assessed under the capacity-adjusted v2 calibration, the same data reads 🟢 ON-COURSE with a watch on selection depth — every band GREEN (71% agent-authored PR acceptance vs a 37–45% population baseline, 5 rising attention windows in 3 weeks, ≤2-window merge latency) — while preserving the failed v1 prediction verbatim as a permanent record. Pinning this fixture ensures future runs can assert both the revised verdict and the non-re-scoring discipline.
What
docs/fixtures/vsdd-factory-312-curated-run16r2.md— the revised board as posted to 📋 beadle — Triage Dashboard drbothen/vsdd-factory#312 (sentinel: run 16, revision 2, instrument v2-capacity-adjusted, intent v0.4). Regression gate PASS vs the pre-revision snapshot: 65,312 bytes, all 423 issue refs / 22 headings / 31 controls preserved.Notes
topic:instrument(v2 adoption) andtopic:calibration(r2 re-assessment) notes.