📖About

Today Hermione mechanically files one initiative per detection with no diagnosis (her filer-droid op_s1.sweep, every 5 min). reported (wellbeing) and failed (dead process) detections share the SAME filing path, so a business/wellbeing signal like Cassius wellbeing flag becomes an engineering build ticket. Insert an AI triage-and-route step before each _file_initiative call: one reasoning call per detection classifies it as real_failure | business_signal | noise, produces root_cause + recommended_scope, then ACTS: real_failure -> file a well-formed initiative enriched with root-cause+scope; business_signal -> route to the owning agent (notify), do NOT file an engineering initiative; noise -> dismiss with reason. Keep deterministic dedup + the incident fast-path. Goal: Hermione understands the issue first, then decides file/route/dismiss instead of filing everything.

⚖️Decisions

• Elrond's bypass methodology checklist (a reminder, not a gate -- you've got this): 0. File it requested_mode='bypass' (planner-vs-bypass is a deliberate choice). bypass_start REFUSES a non-bypass initiative (CAROL-INI-1846), and the dispatcher only skips the bypass lane when the mode says bypass -- a 'planner' mistag lets Merlin's pipeline grab the placeholder step and block your finished work. 1. Filed as planned status -- let the bypass claim/activate it; never file active. 2. Open the bypass (bypass_start) with your droid id + the remediation answer (remediates_initiative_id=NNN, or remediates_nothing=True). 3. Work the blocks for your work-type: template -> design -> code -> test -> review. Do the real work; record decisions on the initiative as you make them. 4. Reality is recorded for you at close -- code (files changed), each decision, and the twin-review verdict become real activities tied to this initiative and show in the Activity Tracker like a planner run (CAROL-INI-1840). No dummy rows. 5. Keep the initiative status moving; it parks in 'reviewing' and is tagged uat-pending for you at close (CAROL-INI-1836), so the stuck-watchdog leaves it alone until UAT. 6. Close runs the gates (design/architecture compliance + caller-audit). If a gate flags something pre-existing or unrelated to your change, waive it with a clear written rationale -- audit, don't skip. 7. Bypass skips the planner's auto-orchestration, NOT the standards. Same template checklist, same review, same observability as a planner run. (elrond)
• [status-router] planned -> executing | event=bypass_executing | bypass transition (or-bx-01)
• Triage = one sonnet classification per NEW detection (post-dedup, pre-file) into real_failure / business_signal / noise. FAIL-SAFE: any error defaults to real_failure with unverified=True, so a genuine failure is never silently dropped. (orion)
• business_signal is ROUTED to the accountable owning agent (the reporting agent named in the detection) as a recorded disposition on the detection, NOT filed as an engineering initiative. Routing is a recorded disposition because Agentbook messaging is restricted to Carol and Orion only (no general agent inbox exists yet). (orion)
• real_failure initiatives are now ENRICHED with the triage root_cause + recommended_scope so the pipeline does not start blind. (orion)
• Fixed a lock-hold regression surfaced by testing: the sweep held an open write transaction on operator.db across the now-slow triage AI calls, causing database-is-locked failures between overlapping runs. The findings connection is now autocommit + busy_timeout=30s so no lock is held during AI calls. (orion)
• [status-router] executing -> reviewing | event=bypass_reviewing | bypass transition (or-bx-01)
• [status-router] reviewing -> closed | event=operator_signoff | Auto-accepted (CAROL-INI-1859): Orion-initiated, >2 days in reviewing with no objection. (el-srac-01)

✅Success criteria

• Hermione runs an AI triage call per detection that classifies it as real_failure / business_signal / noise before any filing (must_have)
• business_signal detections (e.g. wellbeing flags) are routed to the owning agent and do NOT create an engineering build initiative (must_have)
• real_failure initiatives are filed enriched with root-cause + recommended scope, not a bare auto-detected stub (must_have)
• noise detections are dismissed with a recorded reason; deterministic dedup + incident fast-path preserved (must_have)