shakedown: wave 9: store checklist, one-command verdict, calibrated baselines (production-QA foundation)#6
Merged
Merged
Conversation
…rated baselines (production-QA foundation) Store Day Checklist: a single in-store flow centered on one command (./run --store) and the verdict. ./run now ends with a clear SHAKEDOWN VERDICT: PASS/FAIL banner (performance-focused, last thing on screen). Calibrated baselines: make-baseline.sh builds baselines/<preset>.json (golden + 3-sigma or tolerance control limits) from known-good reports; ./run bins against it when present, escalating a below-limit metric to FAIL via the new baseline_check field (calibrated verdict), advisory when absent (schema 1.4). Verification/Production QA.md: honest gap analysis toward a factory-grade screen (calibrated limits, golden binning, MSA, gated preconditions, coverage/escape-rate, SPC). baselines/ ships empty (README only).
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.
Store-day usability plus the first leg of production-grade QA.
One-command experience
./runends with a clearSHAKEDOWN VERDICT: PASS/FAIL(green/red on a TTY), performance-focused, the last thing on screen.Verification/Store Day Checklist.md): a single in-store flow centered on the one command (./run --store) and the verdict, no cosmetic clutter.Calibrated baselines (production-QA foundation)
make-baseline.shturns N known-good reports intobaselines/<preset>.json(per-metric golden value + a 3-sigma control limit, or a tolerance band below 8 samples)../runauto-bins againstbaselines/<preset>.jsonwhen it exists for the--target: a metric outside its golden limit escalates the result to FAIL, turning the verdict from within-unit advisory into a calibrated pass/fail, recorded in the new optionalbaseline_checkfield. Absent a baseline, behavior is unchanged. Schema 1.4.Verification/Production QA.md: an honest engineering gap analysis between Shakedown today and a factory production-QA station (calibrated limits, golden binning, Measurement System Analysis, gated preconditions, defect coverage / escape rate, SPC) and the architecture to close it. The baseline mechanism is the first leg.baselines/ships empty (README only): a baseline is only as good as the known-good corpus, which is still being gathered.Verification
Validated on an Intel MacBook Pro 16 (2019): the advisory -> calibrated transition, golden binning, and below-limit FAIL escalation all behave;
make-baselinemath and the verdict banner verified live. shellcheck clean, heredocs parse, JSON valid, links resolve, zero em dashes. Passed dad review (correctness, simplicity, consistency).Note: this builds the mechanism, not a finished production station. Calibrated limits still need a corpus of known-good units; MSA, gated preconditions, and SPC remain (see Production QA.md).