{"wiki":null,"facts":{"id":"wm-01","name":"Watchman","machine_name":"WM-01","owner":"agt_014","function":"Monitors Carol conversations for signs she is not up and running. Scans all user chats for distress phrases in Carol replies.","process_type":"scheduled","schedule":"Every 15 min","process_name":"watchman","avatar_color":"#94a3b8","created_for":"Guardian is responsible for keeping Carol and all infrastructure healthy and working properly. One critical part of this job is noticing early when Carol has problems. Watchman handles the detection: it continuously monitors whether Carol is actually up and responding correctly to users.","purpose":"Every 15 minutes, Watchman scans what Carol has replied to users across all conversations. It looks for signs that Carol is having trouble. When it finds evidence of problems, it records them in Guardian's monitor database so Guardian knows what's happening and can take action.","duties":"- Scans all user conversation databases every 15 minutes\n- Searches Carol's replies for specific failure phrases like 'something went wrong', 'i'm offline', 'error occurred'\n- Records the status of each scan: 'ok' if Carol looks healthy, 'alert' if problems are detected, 'no_convos' if there's no recent activity\n- Creates detailed alert records showing which user was affected, what Carol said, and which phrase caused the alert","constraints":"Watchman only flags real system failures—it ignores normal conversational hedging like 'i can't' or 'unable to'. It can't tell if Carol is working when there are no active conversations. It only records alerts; Guardian must respond and fix problems. It only watches Carol's outgoing replies, not incoming requests or internal systems.","status":"running","gender":"female","archetype":"watcher","building_block":null,"service_override":null}}