Topic
System design and integration
Where do the components, records, and boundaries belong?
The application needs somewhere to keep unfinished work, a controlled way to change records, and evidence that a change happened. A model call does not provide those parts of the design.
Start with a system sketch that names people, sources, decisions, and failure paths. The extraction example checks which records arrived and which revision is safe to use. Persistent state and customer isolation need their own design and tests.
Notes in this topic
Where does unfinished work live?
A request can outlive the chat, the worker, and an approval. Save what was requested, what happened, and who must follow up so another person can continue safely.
Read the noteHow do you keep customers apart?
A service can check the right customer at sign-in and still return another customer's cached answer or let queued work outlive permission.
Read the noteWhich parts should become shared capability?
Repeated work may justify shared code. First separate the reusable job from each team's data, policy, and responsibilities.
Read the noteWhat should a tool check before changing a record?
An approval can be valid when it is given and unusable when the change arrives. The receiving service has to check again.
Read the noteDoes this need an agent or a fixed workflow?
A workflow can contain a model without handing it the choice of what happens next. Start by writing down which decisions really need that freedom.
Read the noteYou changed one rule. What else changed?
A lower threshold sends more cases to review. Check what happens to the queue before calling the change an improvement.
Read the noteBuild, buy, adapt, or leave it alone?
Your current software may do enough already. Check the difficult case before deciding what to buy or build.
Read the noteWhen the job needs a solver
A schedule can read well and still put one person in two places. When the rules are explicit, use code to find and check the possible assignments.
Read the noteHow much data repair does this decision need?
Find the records needed for the job before starting a company-wide cleanup. A missing budget can block a finance draft; duplicate mailing addresses might not matter.
Read the noteWhich revenue definition should the agent use?
Two reports can both say revenue and mean different things. Settle the definition, scope, and unresolved facts before letting an agent answer.
Read the noteThe API returned 200. Did all the data arrive?
A successful request can leave out the order that would change your decision. Check which records should have arrived before using the extract.
Read the noteDraw the system before choosing an agent
Follow one request through its records, decisions, approval, and confirmation. Then decide where a model belongs.
Read the note