Dispatch confidence
Assignments degrade when readiness and dispatchability context are checked too late.
Outcome: Dispatch decisions are anchored in shared readiness and asset state before assignment.
Dispatch decisions are stabilized when readiness, credentials, and asset state are checked before assignment.
Related power-pair routes
Proof snippets
TMS load lifecycle orchestration includes planning, persistence, and downstream contract surfaces.
verified
docs/products/tms/product.md · Module Catalog > Load Lifecycle and Planning
Code: backend/services/tms/internal/modules/loads
Contract: proto/tms/loads/v1
TMS load lifecycle workflows are implemented in service modules and proto contracts.
verified
docs/products/tms/product.md · Module Catalog > Load Lifecycle and Planning
Code: backend/services/tms/internal/modules/loads
Contract: proto/tms/loads/v1
Crew readiness and eligibility signals are implemented for assignment-gating workflows.
verified
docs/products/crew/product.md · Module Catalog > Readiness & Eligibility
Code: backend/services/crew/internal/readiness
Contract: proto/crew/v1
Crew readiness and eligibility decisions are implemented in dedicated service modules.
verified
docs/products/crew/product.md · Module Catalog > Readiness & Eligibility
Code: backend/services/crew/internal/readiness
Contract: proto/crew/v1