Alder Service Desk has asked you to deliver a reviewable Python workflow. Support routing requests with explicit authority and resource boundaries. All records and observations are fictional. Keep one company and the common STAGES fixture through the notebook. Add each named function without replacing earlier work. Done means the last function calls the earlier functions and returns the complete checked delivery report.
Support routing requests with explicit authority and resource boundaries. Read the function contract before you write and inspect the visible fixture to understand its boundaries. The reply can be wrong on purpose. Your code must preserve the requested output shape while handling empty, hostile or changed inputs. Work from stable identities instead of array positions or copied values. The local client and vectors are deterministic teaching fixtures, so passing these tasks proves the implemented contract on the supplied cases, not a production model quality claim. Each stage adds a distinct function to one company's common notebook. The last stage calls earlier functions to produce a checked accumulated report.
The final artifact keeps its authority, identity and verification boundaries.