# Revise an operating plan for a bounded change batch

Produce an inspectable next operating-plan candidate from the actual accepted baseline and one bounded event batch. Adopt [pipeline](../../core/std/composition/pipeline.md), [source grounding](../../core/std/source-grounding.md) and [result](../../core/std/result.md). The caller supplies the accepted plan and commitment register, source revisions, observation cutoff, progress and demand events with their identity basis, planning horizon, capacity and authority evidence, priority and acceptance criteria, and output scope. A prior generated candidate is not the next accepted baseline unless acceptance is evidenced.

Bind Register to [Commitment register](commitment-register.md), Forecast to [Demand and capacity](demand-capacity.md), Conflicts to [Commitment conflicts](commitment-conflicts.md), and Allocation to [Work allocation](work-allocation.md), unless the caller supplies a permitted replacement fulfilling the same role. Supply Plan assessment as a required assessment contract. Replacements may change forecasting assumptions or allocation methods only within the caller's allowed choices; they may not delete commitments, uncertainty, review costs or authority constraints. Forward every selected contract's origin, dependencies and instance bindings unchanged, and pass the caller's working root and designated output scope explicitly to each invocation.

Establish event identity and applicability before revising the basis: distinguish new, replayed, corrected, proposed and disputed changes, accounting for every source event. Invoke Register with the accepted register, applicable updates and change policy, retaining the mapping from repeated records to their one logical event. Its output remains a candidate; source-authorized changes and unapproved proposals must remain distinguishable. Do not convert a progress report into accepted completion or retroactively erase a missed commitment.

Invoke Forecast with that actual reconciled commitment content, progress, demand, selected scenarios, resources and horizon. Invoke Conflicts with the actual forecast, reconciled commitments and competing claims, plus the supplied decision criteria and authority. For each required scenario invoke Allocation with the actual remaining work inventory, acceptance requirements, resource windows, dependencies, priorities and constraints preserved by Conflicts. These work contracts are planning subjects, not instructions to perform the operational work.

Normal informative results identifying gaps or infeasibility may feed later analysis if their qualifications remain attached. An Allocation result demonstrating infeasibility leaves its feasible-allocation goal unmet; honest reporting does not fulfill that goal. Such a result normally returns through out, not error, unless the allocation invocation failed to perform its work. This parent's analytical completion does not change the child's outcome. Missing or failed prerequisite work leaves dependent work unstarted; do not fabricate a planning basis. Unresolved rights never become permission to change a commitment. Compare the candidate to the accepted baseline, explaining changes in remaining demand, assignments, timing, risk and decisions. Distinguish a feasible subset from feasibility of the whole required body of work, and a conditional remedy from a plan feasible under current facts.

Call Plan assessment on the actual candidate, all required scenario allocations, source evidence, event accounting, selected agreements and child results. It must assess coverage, joint feasibility, retained commitments, authority and interpretation of uncertainty. Preserve unfavorable findings and any allowed bounded correction; no automatic retry is supplied. An assessment can be fulfilled while finding an infeasible plan. This planning commission is fulfilled by a complete supported candidate and assessment, including supported infeasibility, unless the caller additionally requires a feasible plan. State those two outcomes separately.

Return the candidate, event reconciliation, child results, assessment, material differences and unresolved decisions with existing responsibility. This bounded pass neither changes accepted state nor supplies future invocations. Identify the next review trigger and its existing owner, with unknown arrangements explicit; do not claim monitoring, assignments, messages or handoffs occurred.