Lesson 3: The seven constraints that shape Northdesk's design
26 min read·
Module 2 · Lesson 3 · About 45 minutes · Needs: Lessons 1 and 2 of this module, and Python dictionaries and functions
The situation
Joel sends his first design for the Q2 2027 target: one hosted model API for every tenant, answers returned whole, Cases replying inside each tenant's staff chat, and the second provider from the 22 September incident as a fallback. Leila replies within the hour. Brennan & Kloss's data must stay in the EU. Halcyon's contract forbids the provider keeping any of its data. Nobody has asked Brennan to approve a second provider.
Helen wants the constraints written down, with numbers and sources, before anyone argues about components, and a check every later design must pass.