Parallel provision partial failure
An AI wrote this TypeScript function to provision a new account: create the user, set up billing, and send a welcome email, in parallel for speed. Review the failure semantics.
What happens when one of these fails partway, and why is the current shape dangerous?
Implement
provision_with_compensation(step_lines: list[str]) → list[str]Examples
in
[["create_user|ok|delete_user","create_billing|ok|void_billing","send_email|ok|"]]out["run:create_user","run:create_billing","run:send_email","commit"]in
[["create_user|ok|delete_user","create_billing|fail|void_billing","send_email|ok|"]]out["run:create_user","run:create_billing","fail:create_billing","compensate:delete_user"]What a strong answer looks like
Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.
0:00 of about 16 min
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.