SAC Reverse-Engineering Run

SAC Reverse-Engineering Run A workflow diagram generated by Archify. 01 / Sources 02 / Deterministic scanners 03 / Agents and health 04 / OKF graph Collect facts Interpret Use the graph Repository roots · monorepo or multi-repo · Sources › Collect facts Repository roots monorepo or multi-repo Wiki and tickets · exported by host skills · Sources › Interpret Wiki and tickets exported by host skills sac_scan.py · packages, IaC, K8s, CI/CD · Deterministic scanners › Collect facts sac_scan.py packages, IaC, K8s, CI/CD Eight RE agents · code, IaC, network, CI/CD, identity · Agents and health › Interpret · orchestrated Eight RE agents code, IaC, network, CI/CD, identity orchestrated sac_doctor.py · orphans, thin nodes, drift · Agents and health › Use the graph sac_doctor.py orphans, thin nodes, drift sac_capture.py · findings to concepts · OKF graph › Interpret sac_capture.py findings to concepts sac_link.py · typed edges + ownership · OKF graph › Use the graph sac_link.py typed edges + ownership sac_pack.py · design pack + blast radius · OKF graph › Use the graph · 2 hops sac_pack.py design pack + blast radius 2 hops ADR and ticket context drafted concepts deterministic facts resolve references health sweep walk the topology walk build files Legend User UI Agent logic Policy External system

Facts before interpretation

  • • Scanners read build files and IaC with no model in the loop
  • • Agents interpret those facts, they do not replace them

C4 maps onto SAC types

  • • SoftwareContainer is the C4 container, not a Docker image
  • • Component, Module, Class, and Method carry the code levels

Then design against it

  • • Ask what exists and who owns it
  • • Ask what the blast radius is before you commit