diff --git a/BUILDER.md b/BUILDER.md
index ca3fef9..40e6994 100644
--- a/BUILDER.md
+++ b/BUILDER.md
@@ -45,7 +45,7 @@ triage bug, and the move is to say so on the issue, not to guess.
      on the labels against stale prose, say so in the claim — name the
      events you read, their timestamps and their actor, and invite the
      correction if the read is wrong;
-     [the 14:11:44Z claim on #149](https://github.com/heavy-duty/ceremony/issues/149#issuecomment-5070781295)
+     [the 14:11:45Z claim on #149](https://github.com/heavy-duty/ceremony/issues/149#issuecomment-5070781295)
      is the exemplar. Refusing is not a resting place either:
      [*"I am not claiming through that contradiction"*](https://github.com/heavy-duty/ceremony/issues/149#issuecomment-5070776624)
      was a correct instinct and an incomplete move — the next step is to
diff --git a/TRIAGE.md b/TRIAGE.md
index 7c6e638..6e4bf8e 100644
--- a/TRIAGE.md
+++ b/TRIAGE.md
@@ -56,7 +56,7 @@ is the failure this whole flow exists to prevent.
    write that re-read only the thread races it. Both 2026-07-24 failures —
    [a header correction on #149](https://github.com/heavy-duty/ceremony/issues/149#issuecomment-5070758613)
    asserting a hold 58 seconds after its lift, and
-   [a `needs-ruling` ask on #151](https://github.com/heavy-duty/ceremony/issues/151#issuecomment-5070774657)
+   [a `needs-ruling` ask on #151](https://github.com/heavy-duty/ceremony/issues/151#issuecomment-5070768876)
    the operator's label events had answered 132 seconds earlier — are this
    sentence's absence.
    Past 24 hours from the current episode's `labeled` event, if the ruling