incidents: severity-scaled quiet timer, reopen-on-link, thin calls do not fill the cap #176

Merged
logan merged 1 commits from feat/provisional-close into main 2026-09-26 19:14:38 -04:00
Owner

#170

🤖 Generated with Claude Code

#170 🤖 Generated with [Claude Code](https://claude.com/claude-code)
logan added 1 commit 2026-09-26 19:14:37 -04:00
Hand-labelling the 09-22 10:00-12:00 ET replay window (server-26#170,
answer key replay_groundtruth_0922.json) found ~25 real incidents, of which
only ~5 had an audible clear — most jobs clear by MDT, so the quiet timer is
the close for most incidents and a flat 90 minutes left a lockout or a plate
check "active" on the portal an hour after it ended.

- summarizer: timer close after 30 min quiet for routine/minor, 60 moderate,
  90 major/unknown. A timer close is provisional: reopenable=True.
- correlator: reopenable incidents inside incident_reopen_window_minutes
  (90, since last substantive call) stay candidates; linking a call to one
  reopens it (status active, reopened_count++). The sweep expires the flag
  so the reopenable pool stays bounded. Real clears (units_cleared,
  llm_closure) are never reopenable.
- cap: incident_max_calls counts substantive calls only
  (substantive_call_count). The bridge MVA hit 40 in 32 min with ~40% thin
  replies, split in half, and the second half took another job's title.

c2-core: 467 pass.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
logan merged commit e972cace4a into main 2026-09-26 19:14:38 -04:00
Sign in to join this conversation.