Engineering overview
Start with what changed, what is unhealthy and what still needs confirmation.
orders-api release 7c3d91e entered production
Checkout error rate increased; pipeline verification #8421 failed
CORE linked the incident to retry-policy changes in orders-api
inferredRemediation proposal prepared; production authority remains blocked
readyCheckout errors after orders-api release
Evidence is correlated, not collapsed into a single unqualified answer.
Synthetic evidence links the incident to a release that changed database retry behaviour; the proposed remediation remains unapproved. This remains a hypothesis until a controlled test verifies it.
orders-api/config/retry.yaml
max_attempts changed from 3 → 1
checkout-service → orders-api
dependency mapping confirmed from deployment evidence
Northstar Commerce topology
Confirmed, inferred and unknown relationships remain visually distinct.
Runtime cost moved with the release
Illustrative only—estimated savings are not revenue or cash.
Restore resilient retry behaviour
CORE can prepare evidence and a reviewable change without claiming deployment authority.
Unit test retry exhaustion · integration test transient DB errors · deploy to staging · verify checkout/error metrics · stop before merge or production until authorised.
The public demo never creates a branch, merge request, deployment or external write.