Audience asks whether the dynamic changes that blocked and stubbed HTTP calls were thread-safe. Answer: yes — the app runs on Unicorn (process-per-request, no threads), and concurrent-ruby tasks used elsewhere in the codebase were forced inline inside the verification block so everything stayed within one process.