Jurisdictional Scope¶
Institution — instantiates System Scope Definition
A legal or administrative definition of the territory, matter, population, or authority an actor governs.
Jurisdictional Scope turns a boundary into legitimate authority. It fixes which territory, subject-matter, and population an actor may lawfully govern (who and what fall under it), what lies outside its remit (whose authority someone else's), and how cases sitting at or beyond the edge are referred, appealed, or escalated to a higher or joint authority. Its defining concern is not analysis or work but the right to act and be obeyed: the same physical facts fall to different actors depending on where the jurisdictional line runs. That is what separates it from its siblings — it does not merely frame a system for study or list committed work; it says who is entitled to decide, and where an edge case goes when entitlement is unclear.
Example¶
A road bridge spans the river between two adjacent cities, and a two-car collision happens near the middle of the span. Whose police secure the scene, and whose prosecutor charges the case? Jurisdictional scope answers it. City A's department holds authority up to the surveyed boundary marker at the span's midpoint — incidents on the western half fall to A; the eastern half falls to B, and is therefore outside A's remit. A standing mutual-aid memorandum handles the edge: whichever unit arrives first stabilizes the scene regardless of side, and any genuine dispute over which half the wreck lies in — or a pursuit that crosses the line — escalates to the county sheriff, who holds concurrent authority over the river boundary.
The outcome is that the middle of the bridge is not a lawless gap where each department can say "not ours." There is a defined inside, a defined outside, and a named path for the case that lands exactly on the seam.
How it works¶
- Define the remit by territory, matter, and population — the dimensions along which this authority is legitimate.
- Mark the exclusions — adjacent or co-located authorities whose domains begin where this one ends.
- Specify the escalation and referral path — the distinctive move: what happens to boundary, overlap, and appeal cases, and which superior or joint body resolves them. Authority without a referral path leaves seams uncovered.
Tuning parameters¶
- Authority strength — advisory, contractual, regulatory, or binding; stronger authority coordinates better but makes boundary errors costlier.
- Remit breadth — how much territory, matter, and population the authority covers; broader remit reduces gaps but strains capacity and legitimacy.
- Edge handling — a bright-line boundary vs. deliberately concurrent/overlapping jurisdiction; overlap prevents gaps but invites conflict.
- Escalation formality — an informal referral custom vs. a codified appeals hierarchy; more formality adds predictability at the cost of speed.
When it helps, and when it misleads¶
Its strength is producing accountable authority — someone is entitled and obligated to act, and there is a defined recourse for the hard case.
Its failure mode is at the edges: either a negative conflict, where every authority disclaims a case that falls between them, or overreach — acting beyond one's granted remit, the classic ultra vires problem.[n1] A related misuse is defining harms as outside one's jurisdiction specifically to avoid accountability for them. The guarding discipline is to name a residual authority and an escalation path for the uncovered middle, so no case can fall through simply because two bodies each point at the other.
How it implements the components¶
Jurisdictional Scope fills the authority-and-referral components — the legitimacy side of the archetype:
inclusion_criteria— the territory, matter, and population that lawfully fall under this actor's authority.exclusion_criteria— the matters and areas outside the remit, belonging to another authority.exception_or_escalation_path— the referral, appeal, and escalation route for edge, overlap, and disputed cases.
It confers authority but does not draw the internal responsibility_map of owners and handoffs inside an operation — that is Operational Responsibility Map, the nearest sibling (both touch authority and escalation, but this one grants legitimacy over a domain while that one assigns internal ownership). It also does not produce an analytic boundary_statement for study (System-of-Interest Definition) or acceptance-level measurement_scope (Project Scope Statement).
Related¶
- Instantiates: System Scope Definition — turns a scope boundary into legitimate, accountable authority.
- Sibling mechanisms: System-of-Interest Definition · Project Scope Statement · Model Boundary Definition · Service Boundary Definition · Research Inclusion/Exclusion Criteria · Operational Responsibility Map
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Jurisdictional Scope operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it a legal or administrative definition of the territory, matter, population, or authority an actor governs
Independent corroboration: The frozen evidence defines Jurisdictional Scope as 'A legal or administrative definition of the territory, matter, population, or authority an actor governs', so its operative form is Rule, Policy & Commitment.
Nearest alternative: Organization, Role & Governance — The jurisdictional definition is a standing rule that bounds legitimate authority, not the authority-holding body itself.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Legal doctrine developed jurisdiction as bounded authority over territory, subject matter, persons, and remedies.
Related originating lineages:
- Public Administration & Policy — Administrative practice materially shaped operational allocation of authority among public bodies.
Review resolution: Both independent reviews place the primary lineage in law_governance. The queued differences (domain_reach_disagreement) concern secondary metadata rather than primary provenance. The final retains public_administration_policy only where a reviewer supplied a formative-lineage rationale; downstream application by itself is not treated as origin. origin_mode=cross_disciplinary_synthesis records the relationship among origin traditions, while domain_reach=multi_domain records application breadth separately. encyclopedia_synthesis=false reflects whether either reviewer identified a corpus-specific synthesis, and confidence=high preserves the more cautious evidence assessment.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Ultra vires — Latin for "beyond the powers" — is the legal doctrine that an act taken outside an actor's granted authority is invalid. It is the sharp form of the jurisdictional failure in which an authority reaches past its defined remit. ↩