docs(validation): §5.11 — fatal-throw tripwire count exactness (seven→eight, +INV-24 watchdog)#167
Merged
Conversation
…→eight, +INV-24 watchdog)
The §5.11 realtime-chaos tripwire bullet claimed the harness `invariant()` fast-path
grep-matches "all seven real fatal throws" in `portal/portal-realtime.ts` and enumerated
seven. The file actually has EIGHT `throw new Error(...)` fatals — the omitted one is the
INV-24 delivery-progress watchdog fatal ("…delivered ZERO blocks for …ms… Restart to
re-sync from the finalized head."), added in the RT-1 burst (#161).
The tripwire regex (`orchestrate.sh` `invariant()`: `restart to re-sync|deterministic, not
retried|Cannot finalize safely|Cannot reconcile safely`) DOES match the watchdog fatal (it
ends "Restart to re-sync from the finalized head"), so the mechanism was already complete —
this is a doc⟷code enumeration drift introduced by the burst, not a safety gap. Corrects the
count to eight and adds the watchdog fatal to the list, keeping the INV catalog exact.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
What
§5.11's realtime-chaos tripwire bullet claimed the harness
invariant()fast-path grep-matches "all seven real fatal throws" inportal/portal-realtime.tsand enumerated seven. The file actually has eightthrow new Error(...)fatals — the omitted one is the INV-24 delivery-progress watchdog fatal (…finalized head advanced to N, M blocks PAST the highest delivered block … /stream delivered ZERO blocks for …ms … Restart to re-sync from the finalized head.), which was added in the RT-1 burst (#161).Why it's a drift, not a safety gap
The tripwire regex —
invariant()inharness/chaos/realtime/orchestrate.sh:InvariantViolation|restart to re-sync|deterministic, not retried|Cannot finalize safely|Cannot reconcile safely— already matches the watchdog fatal (it ends "Restart to re-sync from the finalized head", caught byrestart to re-sync, case-insensitive). So the tripwire was always complete; only the prose undercounted. All eight throws (lines 403 / 508 / 522 / 553 / 1009 / 1040 / 1054 / 1100) are covered by the regex.Change
VALIDATION.md§5.11, one bullet: "all seven" → "all eight", and add "the delivery-progress watchdog fatal (INV-24)" to the enumeration (placed in file order, after the deterministic-4xx fatal). Doc-only; no code/test change. Keeps the doc⟷code⟷test invariant catalog exact.🤖 Generated with Claude Code