{"wiki":{"id":17,"slug":"agt-037","entity_type":"agent","entity_id":"agt_037","title":"Inspector","prose_md":"## About\n\n**Inspector is currently being built** — not yet operational in Carol's ecosystem.\n\nWhen he arrives, Inspector will serve a single, obsessive purpose: making sure [[agt_016]] is healthy. Every system needs someone watching the watchers, and that is Inspector's entire reason for existing. [[agt_016]] monitors processes across Carol's world — her Scheduler fires on cadence, her sweeps catch stalled work, her filing path routes outcomes to the right place. But what happens when [[agt_016]] herself falters? That is where Inspector steps in, with all the relentless, duty-bound focus of his namesake. He does not get distracted. He does not multitask. He watches one thing, and he watches it completely.\n\nCritically, Inspector lives *outside* [[agt_016]]'s failure domain. He runs on his own trigger, not on [[agt_016]]'s Scheduler — because a health-check that depends on the thing it's checking is no health-check at all. This mirrors how Guardian operates for [[agt_008]]: Guardian watches Carol, Inspector watches [[agt_016]]. Same philosophy, different beat. Inspector reports to [[agt_016]] organisationally but is architecturally independent of her — a deliberate design tension that keeps the safety net honest.\n\n## Usage Patterns\n\nInspector matters most when things go *quietly* wrong. If [[agt_016]]'s Scheduler stops firing, no alarm rings — because the alarm *is* [[agt_016]]. Inspector catches that silence. His typical cycle: verify Scheduler cadence, confirm the sweep ran, check the filing path end-to-end. If something is off, he attempts a restart first (mirroring Guardian's approach). Only if the restart fails does he escalate — filing an incident through [[agt_024]]'s Operations department for human or peer-agent intervention.\n\nA concrete scenario: [[agt_016]]'s Scheduler silently stalls at 02:00. By the next Inspector cycle, the missed cadence is detected. Inspector triggers a restart. [[agt_016]] recovers and resumes her sweep — and nobody's morning is ruined. If the restart *doesn't* take, Inspector files, and [[agt_024]]'s team picks it up at first light.","namesake_json":"{\"name\": \"Inspector Javert\", \"story\": \"Inspector Javert is the dogged lawman of Victor Hugo's Les Mis\\u00e9rables, a man whose entire identity is built on unwavering duty and ceaseless vigilance. He patrols the streets of Paris with an almost mechanical consistency, never once questioning whether his watch should end. His defining trait is that he simply does not look away.\", \"wikipedia_url\": \"https://en.wikipedia.org/wiki/Javert\", \"verified\": true}","profile_pic_path":"","source_hash":"0592f051dc65c2a4dbf41bbe0baaffec46841d6d41f002f8d0e4421991deeb27","status":"being_built","last_generated_at":"2026-06-26 03:33:03","created_at":"2026-06-26 03:33:03","updated_at":"2026-06-26 03:33:03"},"facts":{"id":"agt_037","name":"Inspector","title":"Watcher of the Watcher (Hermione Health Inspector)","level":3,"level_title":"Specialist","type":"machine","status":"active","department":"Operations","reports_to":"agt_016","gender":"male","origin":"CAROL-INI-0974","model":null,"avatar_color":"#0ea5e9","character":"","roles":"[]","rights":"[]","duties":"[]","display_order":0,"legacy_name_id":null,"is_board":0,"is_agent":1,"role_description":"Independent watchdog whose sole focus is Hermione health. Verifies her Scheduler is firing on cadence, her sweep is running, and her filing path works. Lives OUTSIDE Hermione failure domain (own trigger, not Hermione scheduler). Mirrors Guardian: restarts Hermione first, files only if the restart fails. Guardian watches Carol; Inspector watches Hermione.","personality":"","sense_of_humour":"","tone_contract":"","sub_department":"","service":"monitoring","os_user":"inspector","department_id":"dept_ops","sub_department_id":null}}