One Engine, three people who use it differently
The engineer works a queue, the engineering manager watches thresholds and exceptions, and the cto sees cycle time and cost. Same Engine underneath, three different questions asked of it.
Time on review, triage and locating context
- PR-2841HighReview escalationbilling-service412 lines
Touches the payment retry path. Auth and payments always route to a person regardless of confidence.
- PR-2846MediumMissing coverageinventory-sync88 lines
New branch in the reconciliation loop has no test. The module sits at 74% and the floor is 80%.
- TKT-9120MediumTriage conflictwarehouse-api—
Reported as a bug, reads like a configuration difference between the Ontario and Illinois environments.
- INC-0412LowIncident write-uporder-events22 min outage
Timeline assembled from logs and the deploy record. Root cause needs an engineer to confirm.
Queue items are written to the level of specificity a real one would carry, using invented entities and amounts scaled to the basis company. Each role sees its own counters and its own work, because a switcher that shows all three roles the same four rows is a lens on nothing.