Skip to content

Ratify pipeline-fidelity gate new-data basis, fire sequence, #340 footprint sizing - #344

Merged
WilfordGrimley merged 1 commit into
masterfrom
docs-2026-07-23-pipeline-fidelity-followup
Jul 23, 2026
Merged

Ratify pipeline-fidelity gate new-data basis, fire sequence, #340 footprint sizing#344
WilfordGrimley merged 1 commit into
masterfrom
docs-2026-07-23-pipeline-fidelity-followup

Conversation

@WilfordGrimley

Copy link
Copy Markdown

Summary

  • Records owner-ratified rulings from 2026-07-23: the legacy-pilot comparison (Artifact 1) is closed history; the upcoming full-pool Stage D dry-run becomes the pilot/measurement of record going forward. No vote retraction — legacy/deduction votes stay in the DB and in consensus.
  • Adds the full gated fire sequence to docs/pipeline-fidelity-gate.md (§9): deploy master → scoped re-extraction (Bug-B whole-DB reparse + Bug-A sample) → full-pool Stage D dry-run (the pilot) + owner sample audit + write → consensus_recompute --apply.
  • Adds the Fix OCR short-circuit over-skip and glued language-marker set code #340 root-cause catalog-wide footprint sizing (§10, measured 2026-07-23T00:16–00:24Z, live read-only): Bug A 17,531 cards (91% eligible, ~0.2% expected conversion), Bug B 284 rows (212 eligible, 33 staged-run votes all conservative no-match).
  • Adds the Stage C run-identity note (§11): Stage C runs aren't tracked in PilotRunLedger; evidence rows are fully persisted regardless; a ledger fix is a separate in-flight PR.
  • docs/theory.md §7c: one in-register paragraph on the new measurement basis, provenance log line bumped per the file's own convention.
  • docs/troubleshooting.md: two new symptom-first entries — docker exec ... ps has no ps binary (use docker compose top instead), and admin/moderation session drops after a backend deploy (mechanism unconfirmed, marked as such rather than asserted).
  • Refreshed now-stale one-liners in CLAUDE.md/docs/README.md/docs/MANIFEST.md describing the gate page: the "still-open owner decision on two of three constants" language was inaccurate — that fix already merged as PR Stage D: apply the two must-fix resolution-floor / resolved-tag constants #343 (visible at current master HEAD) and is only awaiting deploy.

Test plan

  • python3 .github/scripts/docs_lint.py — clean (link/path lint)
  • python3 .github/scripts/tests/test_publish_wiki_link_rewrite.py — 4/4 pass (link-rewrite parity)
  • python3 .github/scripts/publish_readme.py . regenerated readme.md and diffed clean against the committed file (no README-REGION markers touched by this change)
  • Pre-commit prettier hook ran clean on the final commit

Co-Authored-By: Claude Fable 5 noreply@anthropic.com

…26-07-23)

Record owner rulings: legacy-pilot comparison closed as history, the
full-pool Stage D dry-run becomes the pilot of record; the gated fire
sequence; #340 root-cause catalog-wide sizing; Stage C/PilotRunLedger
tracking gap; two troubleshooting entries (docker exec ps, admin
logout-after-deploy).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@WilfordGrimley
WilfordGrimley merged commit 813a0d6 into master Jul 23, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant