{"wiki":{"id":1013,"slug":"el-rsi-pattern-01","entity_type":"droid","entity_id":"el-rsi-pattern-01","title":"RSI Pattern Diagnostician","prose_md":"## About\n\nThe RSI Pattern Diagnostician is a watchdog that spots recurring pipeline blockages nobody else can see. While the [[rsi]] dashboard tracks per‑initiative issues, this droid looks across **all** block events over the last 24 hours, groups them by root cause, and raises a flag when a single cause triggers 10 or more blocks. Its goal is to stop the same failure from silently repeating across different workstreams.\n\nEvery hour, it aggregates block events, ranks the causes, and checks if there’s already an open pattern initiative for the same problem. If not — and no more than two new alerts are being filed this run — it creates an Albus‑lane pipeline‑fix initiative in the RSI loop, tagged with the pattern cause and evidence, so [[agt_001]] can resolve the root defect. It never edits pipeline code itself; it is pure software, making a purely diagnostic contribution.\n\nIt is owned by [[agt_011]] and is a unique one‑off droid — not part of any standard reusable family. While 187 droids in Carol’s organisation share the “(none)” family label, each of them is a distinct, individually designed worker.","namesake_json":"{\"engine\": \"software\", \"model\": null, \"claude_purpose\": null, \"family\": \"(none)\", \"family_size\": 187, \"is_unique\": true}","profile_pic_path":"avatars/droid/el-rsi-pattern-01.png","source_hash":"628070d0204cbf05c5659d0f61187339f0d5c02662d3aec3279d2bce38688c32","status":"active","last_generated_at":"2026-07-27 03:25:37","created_at":"2026-07-27 03:25:37","updated_at":"2026-08-06 03:25:57"},"facts":{"id":"el-rsi-pattern-01","name":"RSI Pattern Diagnostician","machine_name":"el_rsi_pattern_01","owner":"agt_011","function":"Aggregate block-cause analysis for the RSI service","process_type":"scheduled","schedule":"Hourly at :25","process_name":"rsi-pattern-diagnosis","avatar_color":"#94a3b8","created_for":"","purpose":"Sees what the per-initiative RSI loop cannot: groups ALL block events over a rolling 24h window by routed cause and files ONE Albus-lane pipeline-fix initiative per dominant generator (threshold 10/24h), evidence embedded.","duties":"Hourly: aggregate block events by cause; rank; skip causes with an open pattern initiative; file up to 2 Albus bypass initiatives per run (channel rsi-loop, tags rsi-pattern-diagnosis + pattern:<cause>); emit run-audit on every run.","constraints":"Never files while an open pattern initiative exists for the same cause; never exceeds 2 filings per run; analysis-only — never edits pipeline code itself (Albus does, via his bypass).","status":"retired","gender":"","archetype":"","building_block":"rsi_loop","service_override":null,"enabled":0,"task_key":null,"model_free":0},"page":{"type":"droid","page_class":"main","class_label":"Main page","kind_label":"Droid","kind_gloss":"","listed":true}}