# Construct a connected build plan

Produce the caller's usable plan for making an identified physical product at the required quantity, configuration, time and quality. Adopt [Source grounding](../../core/std/source-grounding.md) and [Result](../../core/std/result.md). The caller supplies product requirements, revision/effectivity, demand, source records, facilities, available evidence and the output/effect boundary. A proposed plan is the default; actual purchases, shop dispatch, acceptance and engineering release require explicit commissioning and available capabilities.

Fulfill [Configuration baseline](configuration-baseline.md), [Manufacturability and routing](manufacturability-routing.md), [Material and yield plan](material-yield-plan.md) and [Capacity schedule](capacity-schedule.md) as connected work. The same product, applicable revisions, demand and source identities are shared across these contributions. Pass the resolved configuration and chosen route into material planning, and its resulting starts, rework and consumption into scheduling. Revise candidate choices within this invocation when necessary, preserving the governing requirements. A favorable schedule based on different quantities does not complete this plan.

The caller may select a Planning policy, Yield model or Route worker for the corresponding roles defined by those contracts; preserve each selected contract's reference origin. The policy defaults to finding a feasible plan under the caller's priorities without an optimality requirement. No separate worker contract is needed for ordinary direct work. Selected roles must actually be fulfilled, and their adverse or incomplete findings remain visible.

Construct the required shop instructions by fulfilling [Build instructions](build-instructions.md) with this plan's operation definitions. Identify the product acceptance rule, sampling/measurement basis and the lot/genealogy records needed to execute the plan. If the caller commissions inspection-plan design, alternative qualification, process-change qualification or a continuing-buildability response, fulfill the corresponding selected contract with the same baseline and explicitly identified evidence; do not invoke every linked contract merely because it exists.

Deliver mutually consistent material quantities, route and capacity allocation, configuration applicability and usable instructions, with support for feasibility and any optimization claim. Resolve the caller's required scenarios, distinguish scenario assumptions from actual output, and report any unfulfilled production goal separately from a completed analytical inquiry. Missing necessary qualifications, engineering limits or capabilities cannot be repaired by an unsupported release recommendation.