Distributed Planning and Reconciliation Session¶

A recurring working session — instantiates Distributed Coordination Architecture

A working session where independently-planning actors reconcile competing claims on scarce shared resources into a jointly feasible set of commitments.

Distributed Planning and Reconciliation Session is the forum where actors who plan independently bring their local plans together, expose their constraints and dependencies, and reconcile competing claims on the same scarce resources — people, space, funding, a route, compute, a time window — into a plan that is actually jointly feasible. Its defining move is resolving the clash the archetype warns about: plans that are each internally sound but collectively impossible because they silently assume the same limited resource. It exists to change plans and to surface unresolved authority — not to report status. When it produces feasible, published commitments against a reconciled resource picture, it has done its job; when it just goes around the table sharing updates, it has failed at the one thing it is for.

Example¶

A city holds a quarterly street-works reconciliation session. Four independent plans converge on one block of Main Street in June: the water utility wants to open a deep trench to replace a main; the transit agency has scheduled bus-lane repaving; a fiber contractor has booked the same block for conduit; and the July 4 parade needs Main clear and repaved by the 1^st. Every plan is "feasible" on its own; together they are impossible — one street, one window.

The session exposes each plan's demand, constraints, and timing, then reconciles against the shared resource. Water goes first because its excavation is deepest; the fiber contractor piggybacks the open trench rather than digging its own (a substitute that removes a whole conflict); transit shifts its repaving to July; the parade route is protected as a hard constraint. The output is a sequenced, jointly feasible plan with published commitments and a pre-agreed shortfall rule — if water slips, fiber slips with it. The session did not merely "align" four calendars; it changed three agencies' plans against a real constraint.

How it works¶

Actors arrive with prepared local plans, not blank pages — the reconciliation works on concrete demands, dependencies, and constraints.
The scarce shared resource is made explicit, and each plan's claim on it is put on the table where the contention is visible.
Reconciliation uses real levers — priorities, reservations, substitutes, sequencing, and pre-agreed shortfall rules — to turn an infeasible overlap into an executable plan.
It changes plans or surfaces authority gaps. The test of a real session is that a plan moved or an unresolved "who decides" got named; anything less is a status meeting.
It publishes feasible commitments — which then flow to the register that tracks them.

Tuning parameters¶

Cadence — rolling weekly reconciliation versus a quarterly big-room session. More frequent stays fresh against change; less frequent costs less but lets conflicts age.
Reconciliation authority — advisory versus binding. If the session cannot actually reallocate the scarce resource, it can expose the clash but not resolve it.
Resource scope — which scarce resources are in play (only the genuinely contended ones belong in the room).
Pre-work rigor — how complete local plans must be on arrival; thin plans make reconciliation guesswork.
Shortfall-rule strictness — pre-agreed priority rules versus renegotiating every conflict live, trading speed against flexibility.

When it helps, and when it misleads¶

Its strength is catching joint infeasibility before execution — the shared-resource collision that each party's own plan cannot see — and converting it into an explicit, negotiated trade with published, feasible commitments. It is where independent plans are made to add up.

Its dominant failure mode is the one the archetype names: degrading into a status meeting that changes no plan and reconciles nothing. Two others recur — domination by the loudest or most senior actor rather than resolution by the actual constraint, and over-planning that freezes a detailed joint plan just as reality shifts under it. Its classic misuse is convening the session to ratify a plan already decided elsewhere, giving reconciliation theater the appearance of a real negotiation.^[1] The discipline that keeps it honest is the rule that it must change a plan or surface unresolved authority, with decisions tied to the constraint rather than to status or seniority.

How it implements the components¶

resource_and_capacity_reconciliation — this is its core function: it exposes demand, reservations, priorities, substitutes, and shortfall rules against the scarce shared resources, turning logically-compatible-but-jointly-infeasible plans into an executable collective plan.

It does not author the shared outcome the plans serve — that is bound in the Joint Operating Agreement; it does not chart the dependencies it reconciles against — that is the Dependency and Interaction Map, which it consumes; it does not store the commitments it publishes — those go to the Commitment and Dependency Register; and it does not verify readiness at execution — that is the Synchronization Checkpoint.

Instantiates: Distributed Coordination Architecture — the reconciliation forum that makes independently-made plans jointly feasible.
Consumes: Dependency and Interaction Map (the dependencies and shared resources it reconciles against) and the Joint Operating Agreement (the shared outcome and constraints the plans must serve).
Sibling mechanisms: Dependency and Interaction Map · Commitment and Dependency Register · After-Action Coordination Review · Coordination Decision Rights and Autonomy Matrix · Coordination Health Review · Event-Driven Coordination Channel · Exception and Escalation Protocol · Interface Control Document or Service Contract · Joint Operating Agreement · Liaison and Integrator Role · Shared Coordination Board · Synchronization Checkpoint

Notes¶

The session produces commitments but does not store them — that is the Commitment and Dependency Register. Keeping the reconciling forum separate from the durable ledger is deliberate: it lets the parties renegotiate a plan without disturbing the record of what was promised, and lets the record persist after the session ends.

References¶

[1] Big-room planning — the practice, used in lean construction and scaled-agile programs, of putting all interdependent parties in one room to build and reconcile their plans against shared constraints live, rather than integrating separately-made plans after the fact. It is the disciplined form of this session, and its whole point is that plans change in the room. ↩