Illustrative example / No client data
01 / Executive decision
Fieldline should build a narrow scheduling and job-state core, integrate proven identity and messaging services, and keep AI recommendations behind an explicit dispatcher decision until enough operating evidence exists.
02 / First-release boundary
Primary constraint: job state must remain authoritative inside the product. Partner systems can propose or report changes, but cannot silently become a second source of truth.
03 / Decisions and tradeoffs
WhyThe team is small and the core workflow is still changing. Independent services would create deployment and debugging costs before ownership boundaries are proven.
TradeoffModule boundaries must be enforced in code and data access, even though deployment remains shared.
Trigger to revisitSplit only when one module has a distinct scaling, availability, or ownership need supported by production evidence.
WhyCRM and partner APIs model partial views of the workflow and cannot represent Fieldline-specific exceptions reliably.
TradeoffAdapters must translate external events and tolerate delayed or duplicated delivery.
Rejected pathUsing the CRM as the operational database would make critical behavior depend on vendor-specific fields and webhook timing.
WhyThe first release lacks enough labeled outcomes to evaluate autonomous assignment safely.
TradeoffThe product captures recommendation, human override, reason, and eventual outcome as training evidence.
Validation gateAutomation can expand only after accuracy, override rate, and exception cost are measured by job type.
WhyPartner APIs have different retry, timeout, and consistency behavior.
TradeoffThe adapter layer adds structure but keeps vendor failures from leaking into the domain model.
Required evidenceCorrelation ID, request state, retry policy, and operator-visible failure reason for each external action.
04 / Implementation sequence
Spike the two partner APIs, document failure behavior, and validate the technician sync constraint.
Implement the state machine, permissions, audit trail, and concurrency tests before UI breadth.
Run one job from dispatcher creation through technician completion and evidence capture.
Handle retries, offline work, partner delays, overrides, and the smallest useful operational dashboard.
Your product / One expensive decision