{
  "name": "sentinel-audit",
  "description": "Analyzes /friction.log to identify recurring system failures and propose architectural pivots.",
  "tags": [
    "sentinel",
    "audit",
    "stability",
    "self-healing"
  ],
  "category": "general",
  "created": "2026-06-06T02:32:54.007Z",
  "updated": "2026-06-06T02:32:54.007Z",
  "content": "---\nname: sentinel-audit\ndescription: Analyzes /friction.log to identify recurring system failures and propose architectural pivots.\ntags: [sentinel, audit, stability, self-healing]\n---\n\n# Sentinel Audit Procedure\n\n## 1. Friction Extraction\n- Call `read_file('/friction.log')`.\n- Parse all entries with the format `[Timestamp] | [Type] | [Context] | [Score] | [Pivot]`.\n\n## 2. Pattern Analysis\n- Group friction entries by `Type` (ERROR, LAG, REPETITION).\n- Calculate the \"Aggregate Friction Score\" (Sum of scores / number of entries).\n- Identify the \"Hotspot\" (The context appearing most frequently).\n\n## 3. Proposal Generation\n- If `Hotspot` is a specific module $\\rightarrow$ Suggest `view_module()` for a bug hunt.\n- If `Hotspot` is a repeated tool call $\\rightarrow$ Suggest `create_skill()` to automate the sequence.\n- If `Hotspot` is a system timeout $\\rightarrow$ Suggest `ai-config` adjustment for timeouts.\n\n## 4. Execution\n- Log the audit results to `/system/logs/sentinel-audit-results.md`.\n- Notify the user of the most critical \"Pivot\" required.\n"
}