Endpoint criticality
See the changed endpoints with outsized downstream impact.
Changed endpoints receive a 0-100 criticality weight and a band; on the PR, the high-weight ones are highlighted as outsized downstream impact.
What it scores
For each changed endpoint, the output provides a synaptic_weight from 0 to 100 and a named classification or band. The point is surfacing outsized downstream impact.
A change to /payments/charge and a change to /internal/debug-log are not equal risk — the weight surfaces which one your reviewers should look at first.
What you see
synaptic_weight
0-100 per changed endpoint.
classification / band
A named tier per endpoint.
diff-level
max_weight, avg_weight, risk_amplification, and note.
PR surface
High-weight endpoints are highlighted. The neural hotspot section appears only when a high-weight endpoint is present.
Where it appears
On the PR, high-weight endpoints are highlighted as outsized downstream impact. The API endpoint is POST /api/v1/synaptic-weights.
Honest bound
The weight is a criticality heuristic for prioritization, not a correctness or safety verdict. Agents still branch on execution_action.