LDR.2 - Agree Feasible Joint Contributions

Kind: Method pattern. Status: Stable.

LDR.2:1 - Problem frame

Use this pattern when participants need one another’s contributions but their proposed scopes, dates, costs or conditions cannot yet coexist. The object is a complete arrangement that the affected parties can actually accept and supply. Begin by recovering what each party needs, can offer and may authorize, then construct and examine whole proposals.

The useful result is acceptance of the same feasible proposal by the parties whose agreement it requires, with any outstanding condition explicit. A warranted refusal or a specific unresolved contribution is also useful: it prevents unsupported reliance.

A routine exchange with clear terms and available resources may already be agreed. Use it directly. This pattern is a bounded negotiation method for joint contributions. It does not adjudicate a legal dispute or require consensus where an applicable decision rule permits another form.

LDR.2:2 - Problem

Several individually sensible promises can form an impossible whole. A provider’s help may require local time already promised elsewhere. A customer may accept a date on one assumed scope while the engineering team agrees to another. A representative may express support without authority to commit the represented party.

The apparent solution can be a numerical ranking or an enthusiastic meeting that hides those incompatibilities. A technically feasible proposal is not yet accepted; acceptance is not technical evidence; neither supplies a missing resource.

LDR.2:3 - Forces

Exploring options benefits from freedom to reconsider. Commitments need sufficiently stable terms and real authority. Mixing those moments discourages exploration or creates accidental reliance.

The parties may value consequences differently and possess different alternatives. A common metric can assist a particular comparison, but it does not turn several independent parties into one decision maker.

Inquiry may reveal a feasible alternative, yet its cost and delay can consume the opportunity. Whole proposals need enough detail for acceptance without demanding a complete forecast of every future event.

Absent and later-affected participants can bear substantial costs. Their participation or representation is needed where the arrangement depends on their contribution or changes a protected interest.

LDR.2:4 - Solution

LDR.2:4.1 - Establish who can explore and who can commit

Name the receiving result and proposed cooperation. Identify the contributions it requires, the people or bodies able to supply them, and whose existing work or rights would change. Recover a party omitted from the first conversation when its contribution or consent matters. In engineering, SYSE.17 helps discover systems that may bear consequences.

Agree a practicable way to explore: participants, time, permitted information, representation, a way to question the proposal and a legitimate way to decline. A representative needs a mandate for the contribution being discussed; attendance or seniority alone does not supply it. CB.13 can establish a workable shared-decision mandate. If an existing protocol already provides that result, retain it.

Obtain participants capable of the negotiation and its substantive judgements. A facilitator may support the process; a qualified engineer, financial practitioner or other specialist supplies the corresponding subject answer. Establish confidentiality and consultation conditions before depending on information. Do not require disclosure a participant has no authority to make; obtain a permitted narrower answer or retain the resulting uncertainty.

Distinguish the act being sought. An agreement among voluntary contributors differs from an executive allocation, a contract, a board decision or permission for a trial. Obtain the relevant authority answer where needed. A negotiation can prepare those acts without making them.

LDR.2:4.2 - Recover the condition behind a position

Ask what result a stated demand protects, what would fail without it and what observation could answer the concern. Retain the participant’s own answer; do not reinterpret every objection as misunderstanding.

For example, “the complete interface by day 20” may protect the need for daily production data, while automatic control can wait. That distinction creates options only if the customer with the necessary authority accepts it. If complete control by day 20 is a real non-negotiable requirement, the reduced proposal does not satisfy it.

Separate a needed result from an assumed means. A required safety property may be met in several configurations; a preferred staffing arrangement may be one way of obtaining a contribution. Use the domain method to examine that claim. B.5.QD.CF helps reconsider conflicting assumptions where an assumed necessary means creates the impasse. D.4 helps when the conflict concerns value premises and acceptable consequences. Neither method grants permission to relax an effective requirement.

Recover meaningful alternatives if agreement fails: continue the present service, obtain a different provider, narrow the result, delay it, perform independent work or decline. A party with no acceptable no-agreement outcome still needs an honest account of that condition; pressure does not make an impossible proposal feasible.

LDR.2:4.3 - Construct whole alternatives before requesting commitment

Combine changes in scope, timing, performer, support, sequence, price and burden into complete proposals. Explain how the contributions fit. Keep more than one materially different feasible candidate where that improves the negotiation, without manufacturing alternatives merely for a count.

For each proposal, follow the needed result backwards to its inputs and enabling conditions. Then follow each promised contribution forwards to who receives it and what else it consumes. This two-way examination reveals hidden dependencies. A support offer can make the technical option feasible while taking time from another project; that displaced receiver belongs in the revised proposal.

Use explicit conditions where uncertainty remains. “Read-only first use after the permitted isolation test, with twelve local support hours each week for six weeks” is examinable. “Start small and provide support” leaves the conditions for performance unwritten.

Compare proposals using the parties’ relevant criteria and credible domain grounds. State who receives benefits, bears costs, defers work or accepts risk. Shared criteria can justify terms, but a combined score does not establish agreement. Do not compensate for an unavailable permission with a high benefit score.

Apply C.11.DUA to the work of negotiation itself. Include preparation, representation, consultation, facilitation, subject inquiry, waiting, implementation, continuing support, monitoring, likely revision and displaced work. Agree an attainable effort and decision horizon. When the negotiation’s burden exceeds its likely useful gain, reduce the question, use an adequate existing arrangement or stop.

LDR.2:4.4 - Resolve a choice-changing unknown, then rebuild the proposal

Identify the question whose answer could change a proposal’s feasibility or acceptance. Ask the qualified subject practitioner for the smallest sufficient inquiry, with its result, conditions, cost and possible consequences for the choice. Compare it with using current knowledge, a narrower commitment, another source, deferral or no agreement.

Obtain permission and resources for the inquiry itself. A test authorization permits the stated test, not introduction into production. A favourable finding supports only the configuration and conditions actually examined.

Return the result to the whole proposal. A technical test may remove one uncertainty while a provider’s offer adds cost, local effort or a time limit. Recalculate joint demand and reopen terms affected by that change. Do not attach new facts to the old proposal while leaving its commitments untouched.

If the inquiry defeats the option, discard or revise that option. Retain independently useful findings and alternatives. If the answer remains uncertain and the required guarantee cannot be obtained, keep the dependent commitment unavailable; uncertainty is not filled by group agreement.

LDR.2:4.5 - Test joint performance, not just individual promises

Before seeking acceptance, place the relied-on contributions in their relevant time windows. Check the quantities and conditions that limit performance: qualified specialist hours, a laboratory window, a delegated spending limit, particular access, a service reserve or a participant’s actual availability.

Sum demands that compete for the same resource. Do not add unlike capacities as if a spare administrator hour supplied a missing engineering hour. Retain timing: a sufficient monthly total cannot supply a specialist who is unavailable before the decision. Include support and supervision retained by the arrangement; they are often the hidden constraint.

When the proposed whole does not fit, construct actual alternatives. Move a contribution only with its receiver’s accepted change; narrow scope without losing the required result; share preparation where it really serves several contributions; obtain a qualified substitute or provider; change the method or sequencing; or defer the unsupported work. Compare the consequences at the level where they matter. A local saving can create a larger downstream burden.

Authority has its own compatibility test. A manager may allocate one team’s time while another unit controls the required specialist. A provider may promise support only after a contract becomes effective. Obtain those contributions or keep the proposal conditional. Do not infer corporate, employment or contractual powers from the fact that participants reached an informal consensus.

LDR.2:4.6 - Obtain responses to the same complete version

Put the complete proposal, its grounds and outstanding conditions before the parties whose acceptance it needs. Make each party’s contribution and relied-on return recognizable. Let them accept, conditionally accept, refuse or leave the matter unanswered. Those responses differ.

A conditional offer of help after funding is available is not a commitment to seek funding, nor is it present funded help. A representative who needs consultation returns to the represented party within the actual mandate. An absent participant’s silence supplies no agreement.

If one party changes its contribution, identify the others whose terms or reliance change and return the amended whole to them. A sequence of separately accepted fragments is sufficient only when those fragments really compose under the same conditions; otherwise obtain responses to the combined proposal.

Retain the accepted terms in the ordinary form the participants use. The record needs enough identity and conditions to distinguish this agreement from a neighbouring version. It need not be a new negotiation template. If the applicable decision rule permits a non-consensual decision, name that rule, the actual decision and the remaining disagreement. Do not present it as mutual acceptance.

LDR.2:4.7 - Return the agreement to work and respond to a changed contribution

Give the receiving practitioners the accepted conditions and unresolved matters. Product and organization decisions may need coordination through OCE.7; engineering architecture and whole-result alternatives use SYSE.6 and SYSE.24; an existing promise may need an authorized response through OPS.13. In another domain, use the corresponding supplier rather than importing engineering decisions by name.

Obtain the separate acts that make the arrangement effective, then perform the contributions. LDR.4 helps when a prepared proposal still needs an effective decision, mutually visible start and first useful handover. Acceptance alone does not establish completion.

Agree a practical response to foreseeable changes: who reports the loss, who can supply a substitute, which participants reconsider dependent terms and how an existing promise is handled. When support disappears, identify the contributions depending on it. Compare feasible substitutes, changed dates or scope with the affected parties; obtain renewed acceptance where reliance changes.

Preserve unaffected results and commitments. A withdrawn support offer does not erase a valid test result. A failed proposed arrangement does not automatically cancel an existing obligation. If no feasible accepted alternative remains, return that impasse to the responsible decision makers before the unsupported work is relied on.

LDR.2:4.8 - Negotiate with or through capable AI

An AI may calculate alternatives, examine resource conflicts, formulate a counteroffer or accept bounded terms when an effective mandate permits it. Establish whose contribution it controls or represents, the scope of that mandate, the counterpart’s ability to identify and rely on the response, and the route for matters outside it. A convincing message from an agent is not evidence of a principal’s authorization.

Where qualified agents can exchange complete proposals and binding responses under agreed rules, a human negotiation meeting may be unnecessary. The substantive tests remain: feasible contributions, legitimate terms, consistent version and actual performance. Human preferences or consent need a permitted way of being represented; simulation of a person’s likely preference is not that person’s consent.

Compare the new arrangement’s setup, integration, computation, exceptions, oversight required by the work and consequences of error. Do not retain a human approval layer unless it supplies a necessary decision or guarantee. Do not remove a required approval merely because automated bargaining is cheap. C.11.DUA supports reconsidering both the arrangement and a disputed procedural burden through the proper authority.

LDR.2:5 - Archetypal Grounding

LDR.2:5.1 - A limited first interface

Suppose a customer asks for a complete interface by day 20. The engineer cannot obtain evidence for automatic control before day 28. After preserving the old service, support has sixteen hours weekly available for change; eight are already allocated to an internal improvement.

The participants recover the actual day-20 need: usable daily data without interrupting production. The customer’s authorized representative accepts that automatic control can be considered later. The service owner protects current service, the improvement owner controls any displacement, the engineer supplies technical judgement and the provider commits its own support. Operators contribute the conditions for actual use.

They consider full control on day 20, postponing all value, and a read-only first configuration. The first lacks evidence; the second fails the customer’s accepted need. The limited configuration needs a technical answer and a support offer. The authorized parties fund a probe asking whether it returns the required records without sending control commands or interrupting the old service. The permission covers the probe alone.

In the stipulated result, the qualified team obtains the required records and verifies those isolation conditions for the examined configuration. A provider offers six weeks of support for 15,000 currency units, requiring twelve local hours each week. The whole proposal now includes that price, scope, duration, local work and separate introduction decision. It promises no automatic-control date merely because day 28 is the earliest evidence date.

Eight unallocated support hours plus four displaced improvement hours supply the twelve required. Four hours remain for improvement. Across six weeks, the improvement loses twenty-four hours, which its owner explicitly accepts. The customer accepts the reduced first scope and price; the provider accepts its support terms; the service owner accepts the allocation while preserving service; the engineer confirms the limited technical basis; operators confirm their tasks and conditions.

These responses concern the same complete version. Preparation, consultation, the probe, implementation, monitoring and possible revision remain costs beyond the quoted price and local hours. The accepted proposal supports the subsequent decisions; it is not itself permission for introduction.

LDR.2:5.2 - The support disappears

Now suppose the provider withdraws before introduction. Replacing its work locally would need thirty-six hours weekly against sixteen available even if all improvement stopped. Another provider can start only on day 27, which the customer refuses.

No considered proposal now supplies a feasible accepted day-20 introduction. The participants return the changed conditions to product, organization and service decision makers. OPS.13 helps obtain an authorized response to the existing customer promise. The old promise is not silently cancelled, and the earlier technical finding remains useful within its scope.

Change a different condition: the customer accepts day 27 and the second provider’s terms fit the available local capacity. The affected parties can accept that revised whole and seek the corresponding introduction decision. There is no need to repeat the unaffected technical probe unless the new configuration changes its applicability.

LDR.2:5.3 - Joint work without a common employer

Suppose three independent researchers agree to publish a comparison. One offers a dataset, one analysis and one review. The analyst’s promised date precedes the dataset’s permitted release. No participant can assign another’s time.

They examine an earlier anonymized subset, a later analysis and independent preparatory work. The data owner determines which sharing permission actually exists; the analyst assesses whether the subset answers the research question. If it does, each participant accepts the revised scope and date. If it does not, the group retains useful independent preparation and defers the unsupported joint result. A new office would supply neither the missing permission nor the dataset.

LDR.2:6 - Bias-Annotation

Lenses: Governance, Architecture, Ontology/Epistemology, Pragmatics and Didactics. Scope: Negotiated joint contributions, with the relevant decision and consent rules retained.

The method favours mutually workable proposals. That can hide unequal power or the interests of absent parties. Recover meaningful refusal, representation and affected contributions; use the actual governing rule when mutual agreement is not the applicable decision method. A beneficial aggregate does not make every party’s loss acceptable.

LDR.2:7 - Conformance Checklist

A conforming use explains:

• the receiving result, necessary parties and actual representation or authority;
• the conditions protected by their demands and serious alternatives to agreement;
• whole proposals with material benefits, burdens and dependencies;
• the domain basis and joint resource feasibility of the proposed commitments;
• the work and limit of any inquiry used to resolve uncertainty;
• responses to the same complete proposal, including refusal and outstanding conditions;
• the receiving decisions and the response to a consequential change.

An already sufficient routine agreement needs no separate negotiation dossier.

LDR.2:8 - Common Anti-Patterns and How to Avoid Them

LDR.2:9 - Consequences

The parties obtain terms they can examine, accept and perform, or a specific reason no agreement is available. Useful partial findings survive a failed proposal. The cost is competent preparation, inquiry where justified and the coordination needed for real acceptance. Negotiation can reveal a legitimate impasse rather than remove it.

More capable or cheaper reasoning expands the alternatives worth examining, but the actual resources, rights and willingness still constrain the agreement. An automated exchange can reduce meeting work; its mandate and operating limits remain part of feasibility.

LDR.2:10 - Rationale

Joint feasibility belongs to the combined arrangement. It cannot be inferred from the quality of separate offers. Obtaining responses to a complete version preserves the relation between what each party accepts and what the others will supply. Following changes through that relation permits selective reopening instead of restarting every discussion or silently preserving an invalid whole.

LDR.2:11 - SoTA-Echoing

The practice question is how to obtain a workable agreement when contributions are mutually dependent. Adapt CBI’s Mutual Gains Approach, 2023 brief: recover interests, mandates and alternatives; explore packages before commitment; use defensible criteria; plan for changing conditions. This is a method source. The brief’s reported experience is not a controlled effectiveness result for these cases.

The selected synthesis adds explicit domain qualification, joint capacity and time-window checks, responses to one complete proposal, and return after a relied-on contribution changes. A serious alternative is competent direct negotiation under an adequate existing protocol. Retain it when it already supplies those results. The narrower procedure earns its additional work where isolated promises hide a whole-arrangement conflict, as in the support case. The trade-off is added preparation and possibly a finding that the desired promise is unavailable.

CB.13’s mandate and conditional team protocol are another sufficient supplier where voluntary shared decision making needs them; this method does not require a second protocol. FPF C.11 retains plural decision makers and D.4 supplies value-conflict reasoning when a single combined score would conceal disagreement.

Reopen the choice of method if participation, representation, professional competence or the inquiry budget cannot support it, or if a simpler arrangement supplies the same accepted result at lower total burden.

LDR.2:12 - Relations

LDR.1 obtains capable facilitation, expertise and help. B.5.SD constructs missing subject answers. LDR.4 connects agreed proposals to effective decisions and first use.

CB.13 supplies representation and shared-decision mandates. Corporate Governance (CGOV), CGOV.3 and .11, resolves corporate power and the act making a decision; persuasion and informal agreement do not replace them.

Systems Engineering (SYSE), SYSE.6/.17/.24, supplies architecture decisions, affected systems and comparison of whole ways to obtain an engineering result. OCE.7 connects product and organizational decisions. Operations Management (OPS), OPS.13, handles commitments and authorized changes.

FPF B.5.QD.CF examines conflicting assumptions, D.4 handles ethical mediation and value premises, and C.11/C.11.DUA supplies decision and inquiry-value reasoning. These are concrete suppliers when their questions arise, not mandatory preliminary stages.

LDR.2:End