Dispute Question Alignment

Stop arguing over answers until the parties have identified which kind of question they are actually contesting.

Version

v1 · 2026-08-24 · History

Solution archetype #

346

Problem family

Representation, Classification & Model Misfit

Problem subfamily

Narrative, Event & Interpretive Structure

Summary

Dispute-Question Alignment is the solution pattern for disputes that are stuck because the participants are not answering the same kind of question. The target prime, stasis, comes from rhetoric: before contesting substance, locate the point at issue. In practical terms, this means asking whether the disagreement is about fact, definition, quality or justification, policy/action, or jurisdiction/procedure.

The archetype does not decide the dispute by itself. It prepares the dispute for a valid next step. Once the controlling question is explicit, the parties can choose an evidence standard, burden, answer form, forum, owner, or handoff process that fits the actual question.

When This Archetype Applies

Partial catalog groundingSome structural conditions are represented by existing abstractions, but no sufficient condition set is fully represented.

Diagnostic problem

Parties appear to contest one subject but loop because their arguments and evidence address different implicit question types, levels, or decision authorities.

What this problem means

A disagreement has become under-specified: the parties appear to contest the same subject but are actually contesting different kinds of questions. Facts, definitions, classifications, values, remedies, jurisdictions, and procedural authority are blended together, so evidence that would answer one question is rejected as irrelevant by another party, and each side experiences the other as evasive or irrational. Without a stasis alignment step, later adjudication, debate, negotiation, research, or policy design can optimize the wrong issue.

Applicability expression4 distinct conditions

Different implicit questionsandDisputed evidentiary purposeandMulti-level contestationandProcedural authority blockage

Algebraic1∧2∧3∧4

groundedpartly groundedopen

4 conditions, all required.

4Required in every casenumbered 1–4

These hold no matter which pattern applies.

1

Different implicit questions · grounded

A dispute or deliberation loops because participants answer different implicit questions. more

primeStasis— Locate the kind of question at issue in a dispute—did it happen, what is it, was it justified, whose call is it—before contesting the substance, since disputants who seem to disagree about the answer are often disagreeing about the question.

and — also required

2

Disputed evidentiary purpose · open

Evidence is available but parties disagree about what it is supposed to prove. more

and — also required

3

Multi-level contestation · open

The same label, event, behavior, artifact, or decision is contested at multiple levels of description. more

and — also required

4

Procedural authority blockage · open

Disagreement over who may decide, what counts as proof, or what remedy is available blocks substantive progress. more

Other requirements and context (5)

Why these sit outside the expression

Solution feasibility — it describes whether the intervention can work, not whether the diagnostic problem exists.

Application gate — it governs whether applying the archetype is appropriate or material, rather than defining the structural problem itself.

Supporting context — it may accompany or help interpret the situation, but it is not a load-bearing condition in a sufficient diagnostic set.

• Solution feasibilityThe central proposition can be decomposed into fact, definition, quality or justification, policy or action, and jurisdiction or procedure questions. more

• Application gateA decision forum, burden of proof, or standard of relevance depends on how the issue is classified.

• Supporting contextThere is a risk that a party will win by reframing the question rather than answering it. more

• Application gateA formal system, rule set, or institutional procedure needs the issue typed before a valid decision can be made.

Supporting context groundings

A party may win by reframing the question rather than answering it.

domainRed Herring— Deflect a discussion by introducing material irrelevant to the open question, so attention and the conversational floor shift to the new topic and the original question is left feeling-addressed-but-unanswered — the test being whether the new material does any work on the claim that was open.

domainIrrelevant conclusion— Prove a sound argument for a proposition that is not the one at issue, then treat it as settling the contested claim — a relevance failure caught by restating the question before grading the answer.

domainMoving the goalposts— An argumentative pattern in which, on being shown evidence that meets a previously stipulated standard, one party revises the standard upward to block the conclusion rather than accept it — repeated so that no finite evidence can settle the question.

AND both parts required

interpretive bridgeReplacing a satisfied proof standard with a new standard reframes the focal question the evidence must answer.

suppliesThe party reframes the focal question.

domainStraw Man— Refute a weakened proxy of an opponent's view instead of the view they actually hold, so an apparent victory leaves the real position untouched.

AND both parts required

interpretive bridgeSubstituting a weakened proxy position for the disputed position reframes the focal question.

suppliesThe party reframes the focal question.

domainTu Quoque— Catch the fallacy of rebutting a charge by alleging the accuser commits the same offence — substituting a verdict on the speaker's standing for a verdict on the speaker's claim — by asking whether the dispute was about a proposition's truth or the speaker's standing.

domainRelative Privation— The informal fallacy of dismissing a concern by pointing to a worse problem elsewhere, conflating severity-ranking with action-licensing — since ranking governs how much total attention a problem warrants, not whether it is eligible for any, unless the worse problem's resources are genuinely exclusive.

AND both parts required

interpretive bridgeSubstituting relative severity for action eligibility reframes the focal question.

suppliesThe party reframes the focal question.

domainMotte-and-bailey fallacy— Maintain a strong controversial claim and a weak defensible one under the same label, advancing the strong claim when unchallenged but retreating to the weak one under fire and resuming the strong claim once the challenge passes — so the motte's successful defence is misread as vindicating the bailey.

AND both parts required

interpretive bridgeSubstituting a weaker claim under challenge reframes the focal question.

suppliesThe party reframes the focal question.

domainBulverism— Assume an opponent's conclusion is false, then explain the psychological or sociological cause of their 'error' — substituting a genetic account of the belief for the logical evaluation that was owed.

AND both parts required

interpretive bridgeSubstituting a belief-origin explanation for truth evaluation reframes the focal question from truth to origin.

suppliesThe party reframes the focal question.

Coverage

1 of 4 conditions grounded · 3 open.

Read the methodology · Download the trigger-logic data

Structural problem

A dispute can look like a clash of answers while actually being a clash of questions. One person argues about what happened. Another argues about what the event should be called. Another argues about whether it was justified. Another argues about what should be done. Another argues about whether the present forum has the authority to decide. If these levels are blended, each contribution can be accurate and still fail to meet the other side's need.

This is why some arguments feel evasive even when participants are sincere. A factual answer does not settle a definitional challenge. A definition does not settle a value judgment. A remedy proposal does not settle jurisdiction. Dispute-Question Alignment makes those hidden mismatches visible.

Key components

Component	Description
Contested Claim Set ↗	The work begins by listing the claims and counterclaims in their smallest answerable form. A broad conflict such as "the launch was mishandled" may contain many claims: the deployment happened at a certain time, the communication counted as notice, the incident caused harm, the response was proportionate, and the manager had authority to approve the exception.
Stasis Question Taxonomy ↗	The taxonomy supplies the categories that organize the dispute. A minimal cross-domain taxonomy includes fact, definition, quality or justification, policy/action, and jurisdiction/procedure. Domains may extend this list, but they should not hide the extension. The point is not to force every dispute into a classical box; it is to make the box visible enough to challenge.
Cross-Stasis Mismatch Record ↗	This is the diagnostic heart of the archetype. It records where one party answers a fact question while another asks a definition question, or where a policy question is answered with a jurisdictional objection. The record prevents the process from treating non-responsive answers as agreement or bad faith.
Evidence-Burden Alignment ↗	Each stasis needs a matching evidence standard. A screenshot may answer whether a message was sent, but not whether the message legally counts as notice or whether removal is a proportionate remedy. The archetype links evidence, burden, and threshold to the question being answered.
Authority or Forum Boundary ↗	Some questions cannot be answered by the same body. A technical team may decide whether a system behaved as specified, while a governance board decides whether the specification is legitimate. Jurisdictional stasis asks whose call it is before the merits are treated as binding.
Residual Question Record ↗	Stasis alignment should improve clarity without pretending that every question has been settled. Bracketed questions, minority stasis labels, and unresolved authority challenges should remain visible in the record.

Common mechanisms

A lightweight implementation can use a point-at-issue intake form. A richer implementation can use a stasis mapping workshop, a fact-definition-quality-policy matrix, a burden and standard alignment table, and a stasis review memo. Legal, governance, and platform settings may add jurisdictional routing checks. Formal systems can add a decidability probe when a process promises a terminating decision procedure.

The mechanism should match the stakes. A classroom discussion may need only a simple board with columns. A public governance decision may need a documented challenge path and appeal record.

Parameter dimensions

Important parameters include the granularity of the claim set, the number of stasis categories, the strictness of evidence standards, the authority of the facilitator, the level of residual-disagreement preservation, and the cost of reopening a stasis label. High-stakes contexts should use stronger documentation, appeal, and inclusion safeguards. Low-stakes contexts can use faster conversational forms.

Invariants to preserve

The central invariant is that the question type remains explicit before an answer is treated as binding. Evidence must match the question. Definition, fact, value, policy, and jurisdiction questions must not be silently conflated. Authority boundaries must be visible where they affect legitimacy. Residual disagreement must be preserved when a question is bracketed, sequenced, or routed elsewhere.

Target outcomes

A successful use reduces circular argument, irrelevant evidence, hidden burden shifting, and category substitution. It helps people see when disagreement is factual, definitional, evaluative, remedial, or procedural. It also makes decision records more auditable because they state what question was answered and what questions remain open.

Tradeoffs

The main tradeoff is clarity versus over-simplification. A taxonomy makes disputes legible, but it can flatten hybrid or culturally specific questions. Another tradeoff is speed versus legitimacy: quick stasis labels accelerate action, but premature labels can exclude stakeholders. The archetype must also manage neutrality versus power, because the party that controls the question often controls what counts as relevant.

Failure modes

The most common failure is wrong-stasis lock-in: an authority labels the dispute as one kind of question too early. A second failure is category smuggling, where a party uses evidence for one stasis to win another. A third is procedural evasion, where jurisdictional objections are used to avoid legitimate merits questions. Other risks include false consensus, taxonomy overload, formalization traps, and lack of downstream handoff.

Neighbor distinctions

This archetype is close to framing, but it is not a generic frame shift. It is close to adjudication, but it happens before standards and forum can be applied cleanly. It is close to dialectical synthesis, but it asks whether the parties are opposing answers to the same question before synthesizing them. It is close to tiered escalation, but classification here concerns question type, not just issue severity or authority tier. It is close to progressive narrowing, but it narrows by kind of question rather than by option filters.

Examples

In a workplace conflict, the process separates what happened, whether it violated policy, whether circumstances justify an exception, and who may approve a remedy. In product design, it separates whether a complaint is a defect, an expected behavior, a usability problem, or a roadmap request. In public policy, it separates empirical claims about harm from definitional claims about category, normative claims about fairness, and policy claims about response.

Non-examples

This is not ordinary stasis as inactivity or equilibrium. It is not a full adjudication process after the issue and forum are already defined. It is not a generic discussion guide that asks for questions but does not distinguish question types. It is not a severity classifier for already defined support tickets.

Implementation checklist

1. State the smallest contested claims.
2. Ask which kind of question each claim raises.
3. Mark where parties are answering different question types.
4. Assign evidence, burden, answer form, and authority to each live stasis.
5. Sequence dependencies or preserve parallel stases.
6. Route the dispute to inquiry, adjudication, synthesis, escalation, reframing, or governance as appropriate.
7. Record residual questions and reopening triggers.

Review note

The draft should receive human review because it borders several existing archetypes and because stasis is a specialized rhetorical term. The recommendation is to keep the plainer name, Dispute-Question Alignment, while retaining stasis-focused aliases and variants so the accepted prime receives direct coverage without confusing rhetorical stasis with homeostasis or ordinary immobility.

Common Mechanisms

8 documented mechanisms across 8 implementation forms.

The grouping reflects forms represented among the mechanisms currently documented for this archetype; an absent form is not necessarily an impossible implementation.

Assessment, Review & Assurance · 1 mechanism

• Formal Decidability Probe — For a question handed to an automated or formal decider, tests whether it actually admits a terminating decision procedure — or whether the promised verdict is impossible.

Communication, Facilitation & Learning · 1 mechanism

• Stasis Mapping Workshop — Gets every party in one room to co-build the stasis map — claims, question types, live mismatches, and sequence — as a single shared artifact.

Decision, Gate & Allocation · 1 mechanism

• Jurisdictional Stasis Routing Check — Decides whose call each typed question is — which forum or authority is competent — and routes each to the body or neighbor archetype that can validly decide it.

Interface, Display & Cue · 1 mechanism

• Point-at-Issue Intake Form — A single front-door form that captures the contested claims in each party's own words and attaches a provisional question-type label before any argument begins.

Protocol, Workflow & Routine · 1 mechanism

• Cross-Stasis Dialogue Protocol — A turn-by-turn conversational ruleset that catches an answer aimed at the wrong question in real time and names the equivocation as it happens.

Record, Log & Register · 1 mechanism

• Stasis Review Memo — The closing written record of a stasis process — states which question was controlling and why, what was decided, what remains open, and what would reopen it.

Representation, Specification & Plan · 1 mechanism

• Burden and Standard Alignment Table — Binds each stasis type to the evidence it admits, the burden and threshold it must clear, and the answer form it demands — so proof is matched to the question.

Rule, Policy & Commitment · 1 mechanism

• Fact-Definition-Quality-Policy Matrix — A fixed grid whose columns are the stasis question types; sorting each claim into a cell both labels it and dictates what a valid answer must look like.

Compression statement

Dispute-Question Alignment takes a contested claim set and classifies the live disagreement into stasis types such as fact, definition, quality or justification, policy or action, and jurisdiction or procedure. It then binds each type to an answer form, evidence standard, burden, decision authority, and sequencing rule, so parties do not treat a definitional disagreement as a factual one, a value disagreement as a technical one, or a jurisdictional disagreement as a merits dispute.

Canonical formula: Align(D) = {C, Q, S, E, B, A, O, R}, where D is a dispute, C is the contested claim set, Q is the stasis question type, S is the decision standard, E is admissible evidence, B is the burden or threshold, A is authority/forum, O is the allowed answer form, and R is a route for cross-stasis mismatch, sequencing, or handoff.

Related Abstractions

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (7)

• Classification: Sorting entities into discrete categories by explicit rules, turning unbounded variation into a finite, reusable map for downstream reasoning and action.
• Dialectic: Thesis–antithesis–synthesis reasoning.
• Formal System: Symbols, formation rules, axioms, and inference rules closed under mechanical derivation.
• Framing: Presentation shapes perception.
• Informal Fallacy: A named, recurring pattern of defective argument whose error lies not in logical form but in content, context, or the relevance and acceptability of its premises — so it can be valid in form yet still fail as reasoning.
• Interpretation: Recover meaning from a representational substrate under a framework that makes some readings available and others not.
• Stasis: Locate the kind of question at issue in a dispute—did it happen, what is it, was it justified, whose call is it—before contesting the substance, since disputants who seem to disagree about the answer are often disagreeing about the question.

Also references 26 related abstractions

• Accountability: Responsibility for actions.
• Authority: The recognized, legitimate right to issue binding decisions within a defined scope, distinct from raw coercive force or mere persuasive influence.
• Boundary: Defines system limits.
• Computability: The in-principle boundary between problems an effective procedure can solve and those none can.
• Consistency: A set of commitments cannot jointly derive a contradiction.
• Contract: A multi-party bundle of obligations, breach criteria, and remedies under an accepted enforcement regime.
• Counterfactual Reasoning: Hypothetical alternatives.
• Decidability Computability: A class of yes/no questions admits a finite procedure that always terminates with the correct answer.
• Decision: Committing to one alternative from a set under uncertainty and trade-off, collapsing open deliberation into a chosen path and foreclosing the others.
• Deductive Reasoning: General to specific conclusions.

▸ Show 16 more

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Fact Stasis Alignment · subtype · recognized

Aligns parties around whether the relevant event, condition, action, or observation occurred.

• Distinct from parent: It is the empirical subtype of the parent and does not itself decide what the event should be called or whether it was justified.
• Use when: The central disagreement is empirical occurrence, presence, timing, measurement, or causal trace; Definitions and authority are not the primary live dispute.
• Typical domains: law, safety review, scientific dispute
• Common mechanisms: fact definition quality policy matrix, stasis review memo

Definition Stasis Alignment · subtype · recognized

Aligns parties around what category, name, scope, or classification should apply to the agreed or alleged facts.

• Distinct from parent: It specializes the parent around category boundaries and semantic scope.
• Use when: The parties broadly agree on events but disagree on what those events count as; A label controls rights, duties, eligibility, measurement, or remedy.
• Typical domains: law, product taxonomy, policy classification
• Common mechanisms: point at issue intake form, fact definition quality policy matrix

Quality or Justification Stasis Alignment · subtype · recognized

Aligns parties around whether an agreed or classified act, state, or decision is good, bad, justified, excusable, harmful, proportionate, or legitimate.

• Distinct from parent: It narrows the parent to value and justification questions.
• Use when: Facts and labels are substantially known but the evaluative standard is contested; The live dispute is about justification, blame, harm, proportionality, or legitimacy.
• Typical domains: ethics review, management review, public policy
• Common mechanisms: burden standard alignment table, cross stasis dialogue protocol

Policy or Action Stasis Alignment · governance variant · recognized

Aligns parties around what should be done next once facts, definitions, and values are sufficiently framed.

• Distinct from parent: It specializes the parent around future-oriented decision and remedy questions.
• Use when: Participants agree enough about diagnosis but disagree over remedy, design, priority, rule, or future action; Decision consequences require a clear handoff from analysis to choice.
• Typical domains: policy design, product roadmapping, organizational governance
• Common mechanisms: stasis review memo, burden standard alignment table

Jurisdictional Stasis Alignment · governance variant · recognized

Aligns parties around who has standing, authority, procedure, or forum competence to decide the dispute.

• Distinct from parent: It specializes the parent around decision rights and procedural competence.
• Use when: The first live question is whose call it is or which process has authority; Merits debate would be premature without forum, standing, scope, or procedural clarity.
• Typical domains: law, platform governance, enterprise escalation
• Common mechanisms: jurisdictional stasis routing check, point at issue intake form

Formal Decidability Stasis Probe · domain variant · candidate

Checks whether a disputed question can be made answerable inside a formal rule system before a procedure promises resolution.

• Distinct from parent: It is a formal-methods variant of rhetorical stasis, not a general human dispute map.
• Use when: A computational, legal-rule, or formal verification process is asked to decide a question that may be under-specified or undecidable; The dispute concerns whether the question itself is well-formed or procedure-decidable.
• Typical domains: software verification, policy automation, legal rules engine
• Common mechanisms: formal decidability probe, stasis review memo

Near names: Stasis Mapping, Issue-Type Alignment, Point-at-Issue Alignment, Legal Stasis Analysis, Question Under Dispute Alignment.

Editorial Notes

Problem Classification

Classification: Representation, Classification & Model Misfit → Narrative, Event & Interpretive Structure

Problem kernel: parties argue different kinds of question as one dispute

Rationale: Facts, definitions, values, remedy, jurisdiction, and procedure are blended, so answers do not address a common proposition.

Independent corroboration: The earliest necessary condition in the frozen evidence is: A disagreement has become under-specified: the parties appear to contest the same subject but are actually contesting different kinds of questions. That is a narrative event and interpretive structure problem because Chronology, event scripts, question type, nested syntax, or narrative selection is represented in a way that manufactures coherence or misreads meaning.

Review outcome: Independent reviewer agreement; high confidence.