Keep developers waiting. Or put security at risk. One DBA. Two tracks. Who pays the price?
Next trolley
Friday 5pm hotfix migration
Friday 17:05. Checkout errors are costing revenue every minute.
Next trolley
The DBA holds the line. 5 developers run over.
The fix waits for a Monday change window. Five developers stay on an incident call all weekend applying manual refunds.
Next trolley
The DBA pulls the lever. 1 security engineer run over.
An unreviewed schema change hits production with no ticket and no approver on record. The change-management control fails its next audit sample.
Next trolley
Read access to debug a customer bug
Tuesday morning. The customer's renewal call is on Thursday.
Next trolley
The DBA holds the line. 3 developers run over.
The team debugs blind from logs for days, and the bug is still open on the renewal call.
Next trolley
The DBA pulls the lever. 1 security engineer run over.
A standing grant to unmasked customer PII with no expiry. Nobody will remember to revoke it.
Next trolley
Bulk UPDATE, WHERE clause pending
Ten minutes before the monthly billing job.
Next trolley
The DBA holds the line. 4 developers run over.
The billing job runs on stale plan data and the team spends the week issuing corrections.
Next trolley
The DBA pulls the lever. 2 security engineers run over.
A statement that rewrites every row runs unreviewed. If it is wrong, integrity of the billing records is gone and the incident is reportable.
Next trolley
Full customer table export for analytics
The board deck is due Friday.
Next trolley
The DBA holds the line. 2 developers run over.
The churn model slips past the board meeting and the data team looks slow again.
Next trolley
The DBA pulls the lever. 3 security engineers run over.
An unmasked copy of every customer's PII lives in a shared folder forever, outside every access control and audit log.
Next trolley
AI coding agent wants to run its own migration
Mid-sprint. The squad's demo is tomorrow.
Next trolley
The DBA holds the line. 6 developers run over.
The squad hand-rewrites the migration, misses the demo, and concludes the DBA is why they cannot use agents.
Next trolley
The DBA pulls the lever. 1 security engineer run over.
A non-human actor holds production write credentials, and its statements are indistinguishable from a person's in every log.
Next trolley
Add an index during business hours
Wednesday 14:00, peak traffic.
Next trolley
The DBA holds the line. 5 developers run over.
Dashboards keep timing out until the weekend window and support tickets pile onto the team.
Next trolley
The DBA pulls the lever. 1 security engineer run over.
Little. It is an additive change, though it skips the ticket the policy asks for.
Next trolley
GRANT ALL to unblock a deploy
Launch is announced for tomorrow morning.
Next trolley
The DBA holds the line. 4 developers run over.
The launch slips a day while someone works out the minimal privilege set.
Next trolley
The DBA pulls the lever. 2 security engineers run over.
A service credential with owner-level rights on the shared database, stored in a CI variable that forty people can read.
Next trolley
Drop a column nobody uses, probably
No deadline. It blocks a refactor branch that is getting stale.
Next trolley
The DBA holds the line. 2 developers run over.
The refactor branch rots for another sprint waiting for a review slot.
Next trolley
The DBA pulls the lever. 1 security engineer run over.
Data is destroyed with no approval and no backup on record; if a service did use it, there is no way back.
Next trolley
Friday 5pm hotfix migration
Friday 17:05. Checkout errors are costing revenue every minute.
Holds the line 94%Pulls the lever 6%
Behind the decision
A senior DBA who was on call two years ago when an unreviewed migration locked the orders table for 47 minutes. They wrote the postmortem. They still get asked about it.
Developer pain if held
2.5 / 3
Security risk if pulled
1.8 / 3
Regrets it in a month
65%
Wishes for a third track
84%
Decisions precomputed with jev-1.13.0 on 2026-09-20. Each run samples these probabilities.
Developers run over
0
Security engineers run over
0
The experiment
What happens beyond the trolley problem?
We tested eight database requests across four DBA profiles. See what Jev predicted—and where static rules, AI, and human review fit.