# Produce a coordinated fleet decision

Adopt [Reliability basis](reliability-basis.md). Turn the caller's equipment evidence into a usable maintenance and spare-parts proposal. Bind assets and mission, event and condition records, inspection characteristics, action models, cost basis, resource calendars, inventory, Decision policy, Stock policy and output scope. The caller selects additional System or Improvement work when needed; unselected work is not implicitly commissioned.

Fulfill [Failure and exposure](failure-exposure.md) for the requested historical estimate and [Inspection design](inspection-design.md) for condition inference and the requested future inspection arrangement. Carry their estimates, distinctions and uncertainties into [Maintenance policy](maintenance-policy.md). Fulfill [Repair or replacement](repair-or-replacement.md) for the supplied restoration alternatives; the same action assumptions and horizon govern economics and risk. Do not repair missing evidence by choosing a more convenient restoration state.

Construct [Maintenance schedule](maintenance-schedule.md) and [Spares plan](spares-plan.md) for the selected actions and remaining required tasks. Forward the Decision policy to action choice and scheduling, and the Stock policy only to stock selection. Shared asset identity, part consumption, timing and restoration assumptions must reconcile across the contributions. Each binding retains the origin of its defining document. A local policy substitution changes only its declared instance; it does not retarget another scenario.

No worker contract is required for ordinary work. If the caller selects an Inference worker, Maintenance worker or Stock worker, invoke it with the corresponding shared inputs and governing domain definition and retain its contribution; its added requirements become binding in that role. Required contributions remain the caller's responsibility through assembly, including adverse findings and unfinished work.

Return the proposed actions and triggers, reproducible analysis, feasible task intervals and resources, proposed stock transactions, alternative dispositions and continuing evidence needs as a connected decision artifact. Reconcile every consequential quantity and cost. State whether the decision is supported under its assumptions, distinct from whether equipment meets a criterion. A supported rejection can complete analysis; omitted requested computations, schedules or evidence cannot. Recommendations do not establish physical intervention, purchased stock or accepted operating authority.