Rights-Conflict Scenario Table¶
Scenario analysis — instantiates Rights–Freedoms Obligation Mapping
Runs concrete combinations of actors, conditions, and scarce resources to reveal which rights collisions are real and which dissolve once scope is fixed.
The Rights-Conflict Scenario Table stress-tests a set of already-mapped positions by running them against each other in concrete situations. Its defining move is enumerating combinations — this bearer, exercising this position, under that condition, while another bearer exercises theirs, over a scarce resource — and reading off, per row, whether the positions actually collide or merely appear to. Many apparent conflicts are artifacts of vague scope: once you pin the object, the trigger, the jurisdiction, and the time window, two "clashing rights" turn out to occupy different situations and never meet. The table's value is separating those false conflicts from the genuine ones, so effort concentrates on the collisions that survive scoping. It surfaces and characterizes conflicts; it does not resolve them.
Example¶
A city receives overlapping requests to use a downtown plaza: a protest march claiming a liberty of assembly, a weekend farmers' market with a standing permit, and nearby residents asserting a claim to quiet enjoyment. Stated as nouns — "free assembly versus commerce versus quiet" — it looks like an unsolvable three-way clash. The scenario table breaks it into rows by condition. Row 1 (Saturday, 8am–1pm, full plaza): market and march both want the whole space at once — a real conflict over a scarce resource, flagged for resolution. Row 2 (Saturday afternoon, plaza empty): the market has ended; the march and residents' quiet claim are scoped to different hours, so the "conflict" dissolves once time is fixed. Row 3 (amplified sound after 9pm): residents' quiet claim genuinely bites, independent of the market. The overlay also distinguishes the residents' collective neighborhood claim from any single resident's, so one household's objection is not mistaken for the community's position. Three named rows replace one shouting match: one real resource conflict, one false conflict killed by scoping, one real time-bounded conflict — each now addressable on its own terms.
How it works¶
- List the positions and the situational axes. Actors, conditions, triggers, scarce resources, jurisdictions, exceptions — the variables that make one exercise of a right meet another.
- Enumerate the rows. Each row is a concrete combination: who is doing what, when, where, over what.
- Classify each row's interaction. Direct contradiction, resource contention, cumulative burden, or no actual contact — the last being a false conflict the row has just retired.
- Scope-narrow before escalating. For each apparent collision, tighten object/time/jurisdiction and re-read; only conflicts that survive tightening are marked real.
- Split collective and individual rows. So a group-held position and an individual one are tested as distinct interactions, not merged.
Tuning parameters¶
- Row coverage — a handful of representative scenarios versus a near-exhaustive combinatorial sweep. Broad coverage catches edge collisions but explodes the table.
- Scenario realism — ordinary cases only, or deliberate stress rows with low-power parties and cross-jurisdiction interactions. Stress rows find hidden conflicts but cost analysis.
- Scope-tightening aggressiveness — how hard you narrow before declaring a conflict false. Aggressive tightening dissolves more apparent conflicts but risks engineering loopholes that exclude real cases.
- Interaction taxonomy granularity — how finely rows are typed (contradiction vs. contention vs. cumulative burden). Finer types route conflicts to the right resolver but add bookkeeping.
When it helps, and when it misleads¶
Its strength is deflation: it shows that a large fraction of "irreconcilable rights conflicts" are really scope ambiguities, and it converts the survivors into specific, addressable resource or timing problems rather than clashes of slogans. The distinction it trades on is the false conflict — an apparent collision that disappears once the governing conditions are pinned, versus a true conflict that persists under any scoping.[n1] Its failure mode is the loophole: over-aggressive scope-tightening can manufacture false conflicts, slicing a genuine collision into conditions so narrow that no row ever shows contact, leaving a real clash formally "resolved" and operationally alive. The guarding discipline is to test each dissolved conflict against a realistic edge case — if a plausible situation still puts the positions in contact, the conflict was real and the tightening was evasion.
How it implements the components¶
normative_conflict_and_interaction_matrix— the table is the interaction matrix, enumerating where positions contradict, contend for scarce capacity, or stack into cumulative burden.scope_condition_and_jurisdiction_boundary— each row fixes object, condition, time, and jurisdiction, and scope-narrowing is the operation that separates false conflicts from real ones.collective_individual_relation_overlay— collective and individual positions get separate rows, so a group's interaction is not conflated with an individual's.
The table exposes and characterizes collisions but does not choose among them — picking the narrowest effective response is the Least-Restrictive Alternative Screen's proportionality_and_least_restrictive_screen, and weighing a survivor's burden against its purpose is the Proportionality Balancing Record's constraint_justification_test. It also assigns no owners or capacity to the duties it touches.
Related¶
- Instantiates: Rights–Freedoms Obligation Mapping — the table is the conflict-discovery stage that runs after positions are typed and scoped.
- Consumes: Counterparty Obligation Register supplies the owned positions whose exercises the table plays against each other.
- Sibling mechanisms: Hohfeldian Relation Matrix · Claim–Liberty Classification Tree · Counterparty Obligation Register · Least-Restrictive Alternative Screen · Proportionality Balancing Record · Permission–Entitlement Crosswalk · Remedy Traceability Review
Editorial Notes¶
Form Classification¶
Form family: Analysis, Modeling & Optimization
Rationale: Rights-Conflict Scenario Table operates as an analytical, modeling, inference, comparison, or optimization procedure that derives insight or a solution because it runs concrete combinations of actors, conditions, and scarce resources to reveal which rights collisions are real and which dissolve once scope is fixed.
Independent corroboration: The frozen evidence defines Rights-Conflict Scenario Table as 'Runs concrete combinations of actors, conditions, and scarce resources to reveal which rights collisions are real and which dissolve once scope is fixed', so its operative form is Analysis, Modeling & Optimization.
Nearest alternative: Representation, Specification & Plan — Rights-Conflict Scenario Table includes features of a static representation, map, specification, schema, or prospective plan that externalizes information, but its defining operation is an analytical, modeling, inference, comparison, or optimization procedure that derives insight or a solution.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Testing concrete fact patterns to locate actual rights conflicts is a legal case-analysis practice.
Related originating lineages:
- Philosophy — Rights theory materially distinguishes genuine collisions from scope errors.
- Public Administration & Policy — Public administration, policy implementation, and program oversight supplies a parallel or contributing lineage for the mechanism's defining operation: runs concrete combinations of actors, conditions, and scarce resources to reveal which rights collisions are real and which dissolve once scope is fixed.
Review resolution: Both blind reviewers agree that law_governance is the primary historical origin. Explicit reconciliation of alternate origin disagreement, origin mode disagreement starts from reviewer_a’s mechanism-specific evidence: Testing concrete fact patterns to locate actual rights conflicts is a legal case-analysis practice. Reviewer A proposed alternates=philosophy, origin_mode=cross_disciplinary_synthesis, domain_reach=multi_domain, and encyclopedia_synthesis=true; reviewer B proposed alternates=public_administration_policy, origin_mode=convergent, domain_reach=multi_domain, and encyclopedia_synthesis=true. The final record retains every independently supported alternate from either review (philosophy, public_administration_policy) without an arbitrary cap, selects origin_mode=cross_disciplinary_synthesis to represent the combined lineage evidence, and keeps domain_reach=multi_domain and encyclopedia_synthesis=true from the more mechanism-specific assessment. Present-day transfer is recorded as reach and is not treated as proof of historical origin.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Borrowed from conflict-of-laws, a false conflict is a situation where two rules appear to collide but, once the actual facts and scope are fixed, only one is genuinely engaged — so no real contradiction exists. The table's scope-narrowing step is the practical test for whether a rights collision is false in this sense or survives as a true conflict. ↩