What architecture baseline makes external API outages supportable while reducing migration risk, and who should own change control?

External API outages should let resource usage determine whether the proposed production workflow infrastructure boundary holds; separate the concerns explicitly by labeling external API outages as the use case, production workflow infrastructure as the operating condition, change control as the owned task, and resource usage as proof from production agents. Separate the concerns explicitly: external API outages is the use case, production workflow infrastructure is the operating condition, change control is the owned task, and resource usage is the proof expected from production agents. Treat external API outages as an architecture and operations problem rather than a one-time implementation task. The final decision record should explain why the chosen approach is suitable for external API outages. Separate the agent framework from the runtime services needed to queue work, persist progress, authorize tools, and resume safely.