Process optimization — Operating Strix
Kept separate from the SOP (process-operate-strix.md) per convention — this
document is about improving the process, not defining it.
Current State
Manual triage after every scan; budget ceilings set per-analyst judgment rather than data-driven defaults per scan mode; no automated re-scan-on-fix loop outside of an analyst manually re-running Strix.
Identify Waste
| Waste | Where it shows up |
|---|---|
Re-reading full penetration_test_report.md for scans with zero findings |
Every clean scan still produces a full narrative report to read |
| Manually copying SARIF into a CI dashboard | findings.sarif is CI-ready but wiring it into the pipeline is a one-time setup cost currently repeated per project |
| Budget ceilings picked ad hoc | No shared table of "typical cost per scan mode / target size" to set --max-budget against |
Future State Recommendations
| Recommendation | Expected benefit |
|---|---|
Wire findings.sarif into GitHub code scanning via the documented CI/CD GitHub Actions workflow (ci-security-scanning-with-strix skill / .github/workflows example in the source repo) once, at the org/template level |
Removes per-project manual SARIF handling |
Track run.json's llm_usage.cost across scans in a shared log to build real budget-per-scan-mode baselines |
Fewer budget-stopped scans needing --resume |
Use --scope-mode diff for all PR-triggered scans by default |
Faster, cheaper CI scans scoped to actual changes |
Estimated Impact
Primarily analyst time saved on triage of clean scans and reduced budget-stop
interruptions — no hard numbers yet; recommend measuring llm_usage.cost distribution
and --resume frequency over the next quarter before quantifying further.
Implementation Plan
- Land the CI SARIF wiring as a reusable template (one sprint).
- Start logging
run.jsoncost/status per scan into a shared sheet (immediate, no engineering work — just a triage-runbook addition). - Revisit budget defaults once ~20 scans of cost data exist.
Related: process-operate-strix.md, STRIX — Process and Runbooks.