Scan Run Lifecycle — What Happened to All 126

Scan Run Lifecycle — What Happened to All 126 A lifecycle diagram generated by Archify. 01 / Run phases 02 / Terminal failures 03 / Operator outcomes Queued · scan accepted · Run phases · 126 scans 01 Queued scan accepted 126 scans Running · probe loop · Run phases · httpx sessions 02 Running probe loop httpx sessions Judged · AEGIS-J verdicts · Run phases · findings + traces 03 Judged AEGIS-J verdicts findings + traces Completed · 80 scans · Run phases · 63% of runs 04 Completed 80 scans 63% of runs Failed · 43 runs · Terminal failures · buckets in cards Failed 43 runs buckets in cards Aborted · 3 scans · Operator outcomes · operator stop Aborted 3 scans operator stop Legend start active state decision terminal success failure / exit

The 80 that counted

  • • Completed scans produced all 243 published findings
  • • Median full scan: 3.6 minutes · average 7.1
  • • Every completed scan persisted traces and verdicts

The 43 that didn't — disclosed

  • • 19 worker/queue issues during platform development
  • • 10 agent endpoint misconfigurations
  • • 9 timeouts · 3 platform bugs we then fixed
  • • Failed runs contribute zero findings — no salvage, no silent retry

Why this matters

  • • Published percentages use completed scans only where noted
  • • No cherry-picking: failure buckets are on the page
  • • Abort is operator-controlled, never silent