Overview

The Negotiation and Conflict Resolution Framework (T13 in Ora’s territory map) handles active negotiation guidance — interest-mapping, BATNA assessment, integrative-option generation, third-side analysis. It activates when the user is in or about to be in an active negotiation or conflict and wants guidance for it, either as a party (their own preparation) or as a third party (mediating or facilitating). The framework produces actionable guidance: the position-vs-interest descent, BATNA development, options for mutual gain, objective-criteria selection, mediator-role analysis. It does not do descriptive stakeholder mapping without active-negotiation framing (that is T8); it does not do pure interest-power analysis (T2); it does not do strategic-game analysis with formal payoffs (T18).

The framework runs in three modes. Interest-mapping is the lightest — a quick pass that surfaces the position-vs-interest distinction, descends to inferred underlying interests per party (hypothesis-flagged), identifies shared/compatible and genuinely-opposed interests, names candidate integrative moves, and flags unknowns the user could test in the negotiation. Principled-negotiation is the full Fisher-Ury treatment — all four elements (separate people from problem, focus on interests not positions, generate options for mutual gain, insist on objective criteria) plus BATNA for both the user and the inferred counterparty. Third-side is the mediator/facilitator/ombuds/community-member perspective on a multi-party conflict, applying Ury’s ten roles in their three clusters (prevention, resolution, containment).

The framework’s load-bearing intellectual content is the position-vs-interest descent, the BATNA development discipline, the integrative-vs-distributive distinction, and the Voss-warning for adversarial contexts. The position-vs-interest descent is Fisher-Ury’s central move: a position is what a party says it wants; an interest is the underlying need or concern that produces the position. Positions are typically singular and incompatible; interests are typically multiple and overlap substantially with the other party’s, opening room for trades. The test for an interest is whether removing the position would leave the interest intact and seeking other satisfaction. The BATNA discipline says BATNA must be developed concretely and tested for realism — abstract or aspirational BATNAs leave the negotiator vulnerable to accepting agreements worse than their actual best alternative.

The integrative-vs-distributive distinction says the framework surfaces both shared/compatible interests AND genuinely opposed interests rather than defaulting to fully integrative or fully zero-sum. Both defaults are diagnostic failures. The Voss-warning says principled negotiation assumes a counterparty willing to negotiate on the merits; when the counterparty is adversarial, manipulative, or operating in bad faith, Fisher-Ury’s prescriptions can leave the principled negotiator exposed. The framework flags the warning explicitly and offers voss-tactical-empathy as an optional supplementary lens; it does not adjudicate Debate D6 (Fisher-Ury sufficiency for adversarial contexts).

The framework answers questions like: I’m walking into this negotiation tomorrow — help me prepare. What does each side really want underneath their stated positions? As a mediator, how should I structure this conflict? What’s my BATNA, and what would the counterparty’s BATNA be? Is this a Fisher-Ury context or do I need Voss’s tactical-empathy supplements?

Systemic context

Negotiation and Conflict Resolution is the active-negotiation territory of Ora’s territory map (T13, super-cluster D — Position, Stakeholder, and Strategy). It sits adjacent to T2 (Interest and Power Analysis, descriptive interest mapping), T8 (Stakeholder Conflict, descriptive conflict-structure mapping), and T18 (Strategic Interaction, game-theoretic equilibrium analysis). Cross-territory dispatch routes to T2 when the question is really interest mapping rather than active negotiation, to T8 sequentially-first when conflict structure is not yet mapped, and to T18 when formal payoffs and equilibria are the right frame. The three T13 modes also dispatch among themselves — interest-mapping escalates to principled-negotiation when mapped interests reveal substantial integrative possibility; principled-negotiation hands off sideways to third-side when the user’s role is facilitator rather than party.

Ora’s output

Example question: I’m a freelancer about to enter a contract negotiation with a new client. They’ve sent me a proposal: $10,000 fixed-fee for a 3-month engagement, with a clause that they own all IP I produce including pre-existing tools I might adapt. The dollar amount is fine but the IP clause is unacceptable. They’ve said “this is our standard contract, take it or leave it.” Help me prepare.

Ora’s response (running Negotiation and Conflict Resolution in principled-negotiation mode):

The case fits the full Fisher-Ury treatment: the counterparty has stated a position (“standard contract, take it or leave it”); the user has a reaction at the position level (IP clause unacceptable); the integrative possibility-space is plausibly real (the client wants delivered work; the user wants compensation plus IP protection; both can plausibly be honored with restructuring). I’ll work the twelve required sections.

Section 1 — Parties and stated positions. Client position: their standard contract as written, including the all-IP clause. Stated framing: this is non-negotiable. Your position: unwillingness to sign the IP clause as written.

Section 2 — People-problem diagnosis. The client’s “standard contract, take it or leave it” framing is a relational signal as much as a substantive one — they are signaling they don’t want to negotiate, possibly because their procurement process is set up around the standard contract, possibly because they’re testing whether you’ll push back. The substantive issue (the IP clause) and the relational issue (their take-it-or-leave-it framing) need to be addressed on separate tracks. Don’t make the conversation about whether they’re being fair to you; make it about the specific IP clause and what alternatives serve both parties.

Section 3 — Inferred underlying interests per party (hypothesis-flagged).

Client interests (inferred): delivered, usable work product they can deploy and modify without licensing complications; predictability of cost and scope (the fixed-fee structure signals cost-control matters); process simplicity — using their standard contract reduces internal procurement and legal friction; protection against you using deliverables in a way that would compete with their business or expose proprietary information. Hypothesis: the all-IP clause is a blunt instrument serving the protection interest; a more precise clause would also serve it.

Your interests: fair compensation (satisfied at $10K); protection of pre-existing tools you’ve built (load-bearing — without protection, every future engagement risks losing tools you depend on); continued ability to use techniques and patterns you develop during the engagement; working relationship that doesn’t poison future negotiations.

Section 4 — Shared and opposed interests.

Shared/compatible: delivered work the client can use; protection of confidentiality and competitive information; preserved working relationship. Genuinely opposed: the all-IP framing vs. your need to retain pre-existing tools. The opposition is real but at the position level — the underlying interests can plausibly be honored without it.

Section 5 — Options for mutual gain.

Option A — Carve-out for pre-existing IP. You retain ownership of pre-existing tools and general patterns; client owns engagement-specific deliverables. Standard professional-services pattern.

Option B — License-back. Client owns deliverables; you retain a non-exclusive license to use patterns and techniques in future work.

Option C — Time-bounded exclusivity. Client owns deliverables and gets 12-month exclusivity on the patterns; after 12 months you can use them in non-competing contexts.

Option D — Confidentiality-and-non-compete instead of all-IP. Strong confidentiality clause plus 12-month non-compete on directly competing engagements; the IP question decoupled from the protection question. Addresses what is plausibly the client’s actual concern without the over-reach.

Section 6 — Objective criteria. Industry-standard professional-services contracts in your space; the fact that virtually no competent freelancer signs an all-IP clause without carve-outs is a third-party-defensible standard. The client’s procurement function will recognize the industry-standard pattern even if their initial proposal didn’t reflect it.

Section 7 — Your BATNA. Decline this engagement; pursue other client work in your pipeline. Concrete description: if you have a comparable engagement candidate, your BATNA is “decline and pursue [named candidate].” If your pipeline is empty, “decline and use the engagement-prep time for prospecting.” Walk through what you’d actually be doing in the next 3 months if you declined; test the BATNA against your last 12 months of engagement-acquisition rate, not against your aspirational rate.

Section 8 — Inferred counterparty BATNA. Hypothesis (medium confidence): the client’s BATNA is to engage a different freelancer or an agency at similar fee. Plausibly weaker than they’re signaling — finding a freelancer who will sign an all-IP clause without carve-outs likely costs them a lower-skilled freelancer, an agency at higher cost, or more time in procurement.

Section 9 — Recommended opening-and-fallback pattern.

Opening: “I’d like to sign this contract; the IP clause needs adjustment to reflect industry-standard professional-services patterns. I propose Option A. What’s the procurement constraint that’s driving the all-IP framing?” The opening combines acceptance, a specific counter-proposal, and a calibrated question that surfaces underlying interest.

Expected counters and fallbacks: if “we can’t customize the contract,” ask whether legal can add exhibits; if “we need the IP for [reason],” address with Option C or D; if “take it or leave it,” activate your BATNA. The BATNA is the decision criterion at the endpoint.

Section 10 — Voss-warning flag. Mild adversarial signals (the take-it-or-leave-it framing tests your willingness to push back), not high-stakes adversarial in the Voss sense. The calibrated-question tactic (“what’s driving the standard-contract framing?”) is worth deploying.

Section 11 — Flagged unknowns to test. Whether procurement has customization discretion; whether the actual concern is confidentiality/non-compete (Option D resolves) or genuinely IP-ownership; whether take-it-or-leave-it reflects internal policy or is a negotiation move; the actual quality of the client’s BATNA.

Section 12 — Confidence per finding. Position-vs-interest descent: high. Options for mutual gain: high. Your BATNA: depends on your pipeline. Counterparty BATNA: medium. Voss-warning: low-grade.

That is what principled-negotiation produces — twelve sections covering parties, people-problem diagnosis, hypothesis-flagged interests, shared and opposed interests, options for mutual gain, objective criteria, both BATNAs concretely, opening-and-fallback pattern, Voss-warning, flagged unknowns, and confidence. The user walks in with the descent already done, four integrative options ready, the opening mapped, and a clear BATNA decision criterion.

Commercial AI comparison

Comparison content auto-populates when the comparison-refresh framework runs against this question. Drafters do not author this section.

Brief comparison commentary

Auto-populates with the comparison content above.

How to use this framework

You can run the Negotiation and Conflict Resolution pattern with any AI of your choice. The composition is single-pass for any of the three modes.

The prompt:

[Paste the framework specification]

Run Negotiation and Conflict Resolution on this case.

Mode (optional): [Interest-mapping / principled-negotiation / third-side. If not specified, the framework infers from depth requested.]

Negotiation or conflict description: [Plain prose — parties, stated positions, what’s at stake, your role.]

Your role: [Party / third-side mediator.]

Your BATNA (optional): [If you’ve already developed your BATNA, state it; otherwise the framework will help develop it.]

The AI runs the within-territory disambiguation first if the mode wasn’t specified — Q1 (depth) for “quick interest-mapping” / “full structured walk,” Q2 (specificity) for “I’m a party” / “third side / mediator.” The output is mode-shaped: a seven-section interest-mapping; a twelve-section principled-negotiation; a ten-section third-side mediation analysis with the ten Ury roles surveyed across three clusters.

For best results: maintain the position-vs-interest distinction (if the framework restates positions in interest-language, descend further); develop BATNA concretely (a named alternative with projected revenue, not “I have other options”); surface both shared and opposed interests rather than defaulting to one; take the Voss-warning seriously when it fires (supplement with tactical empathy in adversarial contexts). The framework is deliberately tool-agnostic — the Fisher-Ury four elements, the BATNA discipline, the Ury ten-role third-side framework, and the Voss tactical-empathy supplements survive the lift to any environment.

Other examples

  • interest-mapping Tier-1 on a quick read. A user has 5 minutes before a phone call and wants the position-vs-interest descent fast. The framework runs the seven-section interest-mapping; the user enters the call with three calibrated questions to test the interest hypotheses. Demonstrates the lighter mode’s value when full Fisher-Ury treatment is overpowered.
  • third-side mediation on a community conflict. A neighborhood association asks for help with a conflict between two factions over a shared resource. The framework runs the ten-role survey across prevention (provider, teacher, bridge-builder), resolution (mediator, arbiter, equalizer, healer), and containment (witness, referee, peacekeeper); identifies active, needed-but-unfilled, and not-yet-relevant roles with named bearers. Demonstrates the framework’s defence against the “let’s just mediate” reflex — many conflicts need prevention or containment work first.
  • principled-negotiation with the Voss-warning fully active. A user is preparing for a high-stakes commercial negotiation with a counterparty known for adversarial tactics. The framework runs the twelve sections but flags Voss-warning prominently, recommends voss-tactical-empathy as supplementary lens, and adjusts the opening-and-fallback to include calibrated questions, accusation audit, and Voss’s “no” that opens engagement. Demonstrates the defence against integrative-overreach.

Citations

The framework draws on the principled-negotiation tradition primarily, with supplements from the tactical-empathy and conflict-transformation literatures. Fisher, Ury, and Patton’s Getting to Yes (1981/2011) is the foundational text for interest-mapping and principled-negotiation; the four elements plus BATNA constitute the most-tested integrative framework available. The position-vs-interest descent is the load-bearing operation across all modes. Ury’s The Third Side (2000) is the operational basis for the ten-role mode spanning prevention, resolution, and containment; surveying all ten roles rather than collapsing into generic mediator is the defence against the mediation-reflex failure. Lederach’s The Little Book of Conflict Transformation (2003) and Kriesberg and Dayton’s Constructive Conflicts (2017) supplement the third-side mode for identity-based or community-rooted conflicts.

Voss and Raz’s Never Split the Difference (2016) is the substrate for the Voss-warning and the optional tactical-empathy lens — calibrated questions, mirroring, labeling, the “no” that opens engagement, and accusation audit. Debate D6 (Fisher-Ury sufficiency for adversarial contexts) is carried explicitly: the framework uses Fisher-Ury as primary and flags adversarial-context limitations when warranted, rather than adjudicating the debate. Lewicki et al.’s Negotiation, Lax and Sebenius’s The Manager as Negotiator (1986), Raiffa’s The Art and Science of Negotiation (1982), and Thompson’s The Mind and Heart of the Negotiator provide the distributive/integrative continuum substrate, ZOPA/reservation-price modeling, and cross-cultural dimensions. The framework was compiled 2026-05-01 from the territory map’s T13 entry; v1.0 with PFF-conforming structure throughout.

Downloads

  • Framework specification (PDF) — link to ora-ai.org canonical artifact when published
  • Framework specification (plain text) — link to ora-ai.org canonical artifact when published
  • Full white paper (PDF) — link when published