logix-perf-observability-loop

Map performance requirements to CI artifacts and runtime owners by converting requirements into specific runtime owner paths, pressure knobs, expected counter movement, and a CI evidence plan before making optimization claims.

Triage performance regressions by analyzing CI outputs to determine artifact comparability, missing counters, timeouts, and stability warnings, enforcing strict claim boundaries and artifact comparability checks before attributing regressions.

Handle missing counters or timeouts during convergence gating by applying counter three-state handling to evaluate missing, zero, or greater-than-zero states, triggering evidence fixes or re-collection before proceeding with runtime optimizations.

Plan performance optimizations with pressure knobs by structuring implementation into one pressure knob and one owner cost claim per step, pairing local verification with the next required snapshot, trend, or convergence gates.

Artifact comparability checks for performance trend analysis are needed to prevent jumping to conclusions, ensuring same-branch trend analysis and soak evaluations rely on structurally comparable CI artifacts before enforcing convergence gates.

Do not claim a performance improvement from CI artifacts when required counters are missing, timeouts occur, stability warnings appear, or artifact comparability checks fail, triggering safe next-step decisions like re-collection instead.