Hit the spaghetti wall around automation 12. Everything worked, nothing was debuggable. The layering approach makes sense, I arrived at something similar by accident after spending three hours tracing a failure across six tools with no clear owner. Separating UX, workflow, and persistence means each layer can fail independently (or be replaced).

Turns out the persistence layer is where most complexity actually lives, not the orchestration. State is the hard problem. The Slack-to-Fibery example is a good one but I'd want to see what happens when the Fibery schema changes and the workflow layer doesn't know yet.