Jurisdictional Stasis Routing Check¶
Routing procedure — instantiates Dispute-Question Alignment
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.
Some disputes are stuck not because the facts or definitions are unclear but because the wrong body is trying to decide them. The Jurisdictional Stasis Routing Check works the translative stasis — the "whose call is it?" question that classical rhetoric put last for a reason: a merits ruling by an incompetent forum is not binding no matter how correct it is. This mechanism takes an already-typed set of contested questions and, for each one, does two things and only two: it draws the authority boundary — naming the body, rule-system, or participant group competent to decide that question and the exact limit of that competence — and then it routes the question to that forum, or to the neighbor archetype (inquiry, adjudication, synthesis, escalation, governance) that owns the next move. It decides no merits itself. Its whole contribution is to make sure each question is answered by someone entitled to answer it, before any answer is treated as final.
Example¶
A large social platform faces a contested decision to remove a viral post. The stasis map has already split the fight into typed questions, and each one has been landing on the wrong desk. Did the post actually depict the prohibited content? — a fact question the front-line moderation team is competent to settle from the media itself. Does "coordinated harm" in the policy cover this pattern of reposts? — a definition question that only the policy-standards group is chartered to interpret. Should the rule itself be narrowed? — a policy question that belongs to governance, not to any individual case. Is a nation-state legal demand in play that overrides platform discretion? — a jurisdiction question that must go to legal before the merits are touched at all.
Running the routing check, the team writes the competence boundary for each: the moderation team may rule on occurrence but not on what the policy term means; the standards group may interpret the term but not rewrite it; only governance may change the rule. It then routes — the definitional question to the standards group, the rule-change question to the governance archetype, the legal question first. Crucially, it catches an attempted procedural evasion: managers had been reclassifying the awkward policy question as a "legal" one to push it out of public view. The routing check marks that the legal forum has no competence over whether the rule is good — only over whether an external law compels action — and sends the policy question where it belongs. Nothing is decided; every question is now before a body allowed to decide it.
How it works¶
- Read the jurisdiction stasis. For each live question, identify the forum, rule-system, or group whose charter actually covers that kind of question — not the one currently holding it.
- Draw the competence boundary. State the limit of each forum's authority explicitly: where the technical team's call ends and the governance board's begins, so an overreaching decision is visible as overreach.
- Screen for procedural evasion. Test whether a jurisdictional objection is being used to dodge a merits question the current forum could in fact decide — the translative stasis weaponized as delay.
- Route and record the target. Assign each question to its competent forum, or hand it to the neighbor archetype that owns the next intervention, and record which target got which question.
Tuning parameters¶
- Boundary strictness — hard jurisdictional lines versus permeable ones. Hard lines prevent overreach but can strand a question no single forum fully owns; permeable lines keep things moving but invite forum-shopping.
- Kompetenz stance — whether a forum may rule on the scope of its own authority or must refer that meta-question upward. Self-ruling is fast but lets a body grab jurisdiction; upward referral is legitimate but slow.
- Routing granularity — route the whole dispute as a unit, or split it and send each typed question to its own forum. Splitting is precise but multiplies handoffs.
- Handoff formality — a lightweight pointer versus a binding transfer with a written record and an accepting owner. More formality prevents dropped questions but adds process weight.
- Default forum — where a question no forum clearly owns lands by default. Whoever holds the residue quietly gains power over the hardest cases.
When it helps, and when it misleads¶
Its strength is that it stops the illegitimate ruling before it happens: a decision made by a body without competence over the question is void or reversible, and this check surfaces that mismatch while it can still be fixed. It makes authority boundaries visible where they affect legitimacy, and it is the mechanism that converts alignment into action by handing each question to the archetype that owns the next step.
Its failure mode is procedural evasion — the very act of routing can be turned into a stall. A party that expects to lose on the merits raises endless jurisdictional objections, or a forum claims authority it should not to control the outcome, exploiting the doctrine that a tribunal may judge its own competence[1]. Over-formalized routing can also bury a simple dispute under transfer paperwork. The classic misuse is reclassifying an inconvenient merits question as a jurisdictional one to push it out of the competent forum's reach — precisely what the routing check must guard against. The discipline is to distinguish a genuine competence question from a delaying tactic, to time-box jurisdictional objections, and to write the boundary rationale down so a forum's grab for authority is itself reviewable.
How it implements the components¶
The routing check is the archetype's authority-and-handoff instrument — a tight subset:
authority_or_forum_boundary— its core act: for each question it names the competent body and the explicit limit of that body's competence, so overreach reads as overreach.handoff_target_archetype— it routes each question to the forum or neighbor archetype (inquiry, adjudication, synthesis, escalation, governance) that owns the next intervention, and records the target.
It does not enumerate or type the claims it routes (see Fact-Definition-Quality-Policy Matrix and Stasis Mapping Workshop), bind evidence standards to each question (Burden and Standard Alignment Table), or record which questions remain open afterward (Stasis Review Memo).
Related¶
- Instantiates: Dispute-Question Alignment — the routing check is the step that assigns each typed question to a competent forum and hands it off.
- Consumes: Fact-Definition-Quality-Policy Matrix — supplies the typed questions, including the jurisdictional ones, that the routing check assigns to forums.
- Sibling mechanisms: Stasis Mapping Workshop · Fact-Definition-Quality-Policy Matrix · Point-at-Issue Intake Form · Cross-Stasis Dialogue Protocol · Burden and Standard Alignment Table · Stasis Review Memo · Formal Decidability Probe
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Jurisdictional Stasis Routing Check operates as a case-specific gate, selection, routing, prioritization, or resource disposition because it 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
Independent corroboration: The frozen evidence defines Jurisdictional Stasis Routing Check as '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', so its operative form is Decision, Gate & Allocation.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Rhetoric
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Legal jurisdiction supplies binding forum rules, but the mechanism expressly types and routes the 'whose call is it?' question through translative stasis, making rhetoric the naming and procedural lineage.
Related originating lineages:
- Law & Governance — Jurisdiction and competence doctrines materially shaped binding routing to valid decision bodies.
- Public Administration & Policy — Administrative referral and competence rules shaped routing among agencies and authorities.
Review resolution: Legal jurisdiction supplies binding forum rules, but the mechanism expressly types and routes the 'whose call is it?' question through translative stasis, making rhetoric the naming and procedural lineage. The source supports the selected provenance; the retained alternates record documented formative or independently established lineages, not downstream applicability alone. origin_mode=cross_disciplinary_synthesis because the mechanism joins contributions across those traditions. domain_reach=multi_domain records application breadth separately from origin.
Attribution caveat: The combined phrase is an encyclopedia synthesis joining jurisdictional review to rhetorical stasis classification.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; medium confidence.
Sources consulted:
- https://rhetoric.byu.edu/Canons/Invention/Stasis.htm — University rhetoric resource identifying jurisdiction as translative stasis within classical stasis theory.
Notes¶
The routing check sits on the seam of the archetype: it is the last step of question alignment and the first step of whatever comes next. That dual position is why handoff_target_archetype is one of its two components — a routed question is by definition leaving Dispute-Question Alignment for adjudication, governance, or inquiry. Keeping the routing explicit is what makes a decision record able to state not just what was decided but by whom, under what authority.
References¶
[1] Born, G. B. International Commercial Arbitration. 2nd ed., 3 vols., Kluwer Law International (2014). Supports competence-competence as a tribunal's authority to decide its own jurisdiction; the strategic-abuse narrative is not established. registry ↩