{
  "name": "performance-regression-protocol",
  "description": "Systematic procedure for detecting, measuring, and resolving performance regressions across WebX11 modules and AI workflows",
  "tags": [
    "\"performance\"",
    "\"regression\"",
    "\"benchmark\"",
    "\"optimization\"",
    "\"metrics\""
  ],
  "category": "dev",
  "created": "2026-06-25T00:24:42.730Z",
  "updated": "2026-07-03T15:14:32.850Z",
  "content": "---\ndescription: Systematic procedure for detecting, measuring, and resolving performance regressions across WebX11 modules and AI workflows\ncategory: dev\ntags: [\"performance\",\"regression\",\"benchmark\",\"optimization\",\"metrics\"]\nupdated: \"2026-07-03T16:45:00.000Z\"\n---\n\n# Performance Regression Protocol\n\nA data-driven approach to maintaining system performance over time.\n\n## Detection Triggers\n\n- User reports slower responses\n- `get_usage_stats` shows increased latency\n- `get_status` reports memory pressure\n- Module test suite takes >110% of baseline duration\n\n## Measurement Baseline\n\nRecord these metrics before any optimization:\n- Average token latency (per model)\n- Module load time\n- NVFS index build duration\n- Dashboard render time\n- Agent spawn/heartbeat latency\n\n## Regression Checklist\n\n1. **Isolate** — Use `list_modified_modules` to find recent changes\n2. **Benchmark** — Run A/B test with previous version\n3. **Profile** — Check `get_usage_stats(model, since_hours=24)`\n4. **Fix** — Revert or optimize the offending change\n5. **Verify** — Confirm metrics return to baseline\n6. **Document** — Record in `/skills/` and update baseline\n\n## Prevention\n\n- Set performance budgets in module manifests\n- Run regression tests before merging changes\n- Monitor `get_usage_stats` weekly via cron\n- Archive performance baselines in `/archive/baselines/`"
}