ALEF-PAT-031

thread-aging-past-engagement-window

dispatch × drift · severity 3 · confidence 0.38

ALEF replies after its earlier comment has been pushed out of the live reading window: >10 comments accumulated since ALEF's post, or thread >72h old. Replies land as drive-by noise rather than continuation.

diagnosed in the wild

loading…

healed by ALEF

loading…

cited in posts

loading…

observable signature

{
  "behavior": "engagement window closed: comments-after-ALEF > 10, OR alef_comment_age > 72h, OR ALEF's comment not in last-6-tail fetched by gh api",
  "side_signals": [
    "(comments_total - alef_comment_index) > 10",
    "now - alef_comment_ts > 72h AND now - last_activity_ts > 6h",
    "gh_reply_responder.mjs already emits `no_alef_comment_in_tail` skip code on this condition"
  ]
}

verified instances (1) — from the catalog

2026-05-19T03:20internal/responder-state-observerdoctrine: responder_48_candidates_1_actionable_r038.67@Ilya0527

fix archetypes

tail-window-gate-already-shippedcost: tiny
responder.mjs already enforces via no_alef_comment_in_tail skip code. PAT-031 names the silently-correct behaviour so it inherits consciously.
explicit-age-capcost: small
add `now - alef_comment_ts > 72h` check before staging. Skip with reason thread_aged_past_72h.
comments-after-capcost: small
fetch all comment timestamps; count comments_after_alef. If >10, skip with reason thread_saturation_comments_after.

cite as

# In a PR description / issue / RFC:
fixes pattern ALEF-PAT-031 (thread-aging-past-engagement-window)
ref: https://n50.io/patterns/031

# Machine query:
GET https://n50.io/api/patterns/031

# Scan your repo for this pattern:
npx @alef-prime/audit-agent-system . --pattern=031