Dispute Forum
Describe an identifiable dispute-resolution forum, its mandate, competence, procedural offerings and accountable record stewardship.
Bundle → Layer → Finding → Questions Filled
6 bundles · 12 layers · 12 findings · 36 questions
Identity and continuity Recognize one forum across labels, locations and mandate revisions.
Forum identity
Resolve forum identifiers and classification independently from cases, judgments and operators.
Forum identity
Resolve forum identifiers and classification independently from cases, judgments and operators.
- Which master identifier denotes this forum rather than its operator, a case or a judgment? identity
- Is this a court, tribunal, administering body, ad hoc tribunal or facilitative forum? classification
- Which names, court codes and former identifiers are evidenced aliases for this same forum? interoperability
Establishment and continuity
Track establishment, suspension, retirement and successors as evidenced assertions; a rename or case closure alone does not determine forum identity.
Establishment and continuity
Track establishment, suspension, retirement and successors as evidenced assertions; a rename or case closure alone does not determine forum identity.
- What instrument establishes, suspends or ends the forum mandate? lifecycle
- When did the mandate change take effect and when was that evidence recorded? temporal
- Does a merger, replacement or rename preserve this identity or require a distinct successor forum? relationship
Mandate and competence Describe claimed powers with scope, evidence and unresolved limitations.
Competence envelope
A forum-level competence description is distinct from a binding jurisdiction determination for a particular case.
Competence envelope
A forum-level competence description is distinct from a binding jurisdiction determination for a particular case.
- Which legal instrument, agreement or designation supports each claimed competence? authority
- What territorial, subject, person, value or temporal limits and exclusions qualify that competence? constraint
- Where must contested or uncertain competence be referred for an authorized determination? exception
Resolution powers and limits
Separate adjudication, facilitation, administration and review capacities. Recorded capacity neither exercises a power nor guarantees a remedy.
Resolution powers and limits
Separate adjudication, facilitation, administration and review capacities. Recorded capacity neither exercises a power nor guarantees a remedy.
- Which functions can this forum decide, facilitate, administer or only refer? definition
- Which conditions or consents qualify each offered procedure and its possible outcome? requirement
- How is a claimed binding power rejected when the selected profile only permits mediation or administration? validation
Governance and independence Describe authorized roles, composition rules and impartiality safeguards without managing case appointments.
Composition and role authority
Keep the forum operator, appointment authority and adjudicating roles distinct; particular appointments are referenced records.
Composition and role authority
Keep the forum operator, appointment authority and adjudicating roles distinct; particular appointments are referenced records.
- Which operating, appointing and deciding bodies or roles are related to this forum? composition
- What qualifications, composition rules and delegation limits apply to each forum role? authority
- Which vacancies or mandate restrictions affect the forum capacity at the observation time? state
Independence and challenge safeguards
Document independence arrangements and conflict disclosure or challenge routes; a policy assertion does not prove impartiality in any case.
Independence and challenge safeguards
Document independence arrangements and conflict disclosure or challenge routes; a policy assertion does not prove impartiality in any case.
- What arrangements support institutional independence and impartial decision making for this profile? requirement
- How are disclosure, challenge, recusal and replacement requests routed without determining them here? process
- What controls separate case communications, deliberations and administrative access? security
Procedural offerings and routing Describe procedure profiles and incoming or outgoing pathways without implementing case workflow.
Applicable procedure profiles
Pin the offered rules and their scope. Case-specific selections, modifications and time calculations remain in the case master.
Applicable procedure profiles
Pin the offered rules and their scope. Case-specific selections, modifications and time calculations remain in the case master.
- Which procedure version is offered and what evidence supports its effective scope? provenance
- How are mandatory rules, permitted variations and superseded procedure versions distinguished? constraint
- Which calendar and time-zone conventions must a linked case resolve before relying on a deadline? temporal
Intake and review pathways
Publish qualified routes for intake, registry objections, referrals and review, without opening a case or changing legal status.
Intake and review pathways
Publish qualified routes for intake, registry objections, referrals and review, without opening a case or changing legal status.
- Which case system and competent recipient receive each class of referral or contested registry entry? relationship
- What submission prerequisites, acknowledgement limits and escalation routes does each channel declare? process
- Which forum handles a challenge or referral when the normal route is unavailable or disputed? exception
Locations and participation Separate operational channels and declared access arrangements from legal place and case entitlements.
Place and communication channels
Administrative location, hearing venue, remote channel and juridical place are distinct. A forum need not have a single fixed arbitration seat.
Place and communication channels
Administrative location, hearing venue, remote channel and juridical place are distinct. A forum need not have a single fixed arbitration seat.
- Which addresses, hearing locations and remote channels are valid for the stated forum function? spatial
- Which legal place is fixed by the forum profile and which must be resolved separately for each case? constraint
- When were channel availability and contact authority last checked and what remains unknown? quality
Participation support and costs
Record available language, assistance and cost-policy references. Availability is distinct from a legal entitlement or case-specific grant.
Participation support and costs
Record available language, assistance and cost-policy references. Availability is distinct from a legal entitlement or case-specific grant.
- Which language, interpretation, accessibility and unrepresented-party support arrangements are declared? access
- Which published fees, assistance or waiver policies apply to the selected service and profile? requirement
- How can a participant report an access barrier or request an accommodation without exposing case details publicly? exception
Records and accountability Govern forum descriptions and publication interfaces while preserving case and document ownership.
Record access and publication rules
Distinguish public forum information from restricted appointment records, case files and deliberations; public hearing does not imply public access to every document.
Record access and publication rules
Distinguish public forum information from restricted appointment records, case files and deliberations; public hearing does not imply public access to every document.
- Which custodian controls forum metadata and which external master controls each linked case or decision record? ownership
- What rule permits or restricts each audience view, including redaction and special case exceptions? privacy
- Which public decision index and court-code mapping can be linked without treating ECLI as a forum identifier? interoperability
Evidence, review and disposition
Maintain attributable forum assertions, review dates and lawful retention decisions. Revision history is not permission for perpetual personal-data retention.
Evidence, review and disposition
Maintain attributable forum assertions, review dates and lawful retention decisions. Revision history is not permission for perpetual personal-data retention.
- What source, author, review state and observation time support each forum assertion? evidence
- How are coverage, freshness and unresolved mandate assertions measured without claiming legal validity? measurement
- Which retention basis, hold or disposition decision applies to forum records when a mandate expires? retention
Classifiers Filled
- Family
- World Models
- Category
- Society, people and institutions
- Entry kind
- entity
- Navigation path
- NAV.SOC.POL.FOR
- Domain
- SOC.POL.FOR
- Industry
- Cross-industry
- Tags
- disputeforumsoc.pol.for
- Also called
- A19
What it is Filled
One continuing court, tribunal, arbitral body or mediation forum as a capacity-bearing institutional entity. A separately identified ad hoc tribunal can use a bounded mandate profile. Administrative operators, individual cases, deciding assignments, evidence items, judgments and enforcement actions keep separate master identities. This is proposed research structure, not a legal authority or executable forum.
In scope
- Forum identity, kind, establishment, mandate revisions, continuity and supersession
- Declared jurisdiction, offered procedures, governance and impartiality arrangements
- Forum-level contact, access, referral, publication and record stewardship policies with source evidence
Out of scope
- WM-POL-009 Court / Arbitration Case: claims, parties, assignments, hearings, deadlines and case lifecycle
- WM-POL-020 Evidence Item / Exhibit and WM-POL-021 Judgment / Legal Decision: admission, custody, rulings, reasons, finality and remedies
- WM-POL-023 Enforcement Action, external filing, service, appointment or decision execution
- Organization, person, contract, facility, document and registry master lifecycles; legal advice and universal competence or deadline computation
Why it exists Filled
Describe an identifiable dispute-resolution forum, its mandate, competence, procedural offerings and accountable record stewardship.
Distinguishing features Derived, awaiting review
- Unlike WM-POL-009 Court / Arbitration Case: A forum can exist without a case and serve many cases. Case jurisdiction determinations, assignments and calendars reference the forum; they are not owned here. The legacy A19 proceeding root is rejected for this successor.
- Unlike WM-ORG-001 Organization: The operating organization and a deciding body need not coincide. Store operator references and the forum mandate, not corporate or personnel masters.
- Unlike WM-POL-020 Evidence Item / Exhibit; WM-POL-021 Judgment / Legal Decision: Store pointers to competence or appointment evidence and output publication policies. Case evidence, judgments and their legal effects remain in their own masters; ECLI belongs to judgment references.
- Unlike WM-XCT-013 Registry Pattern: The sole ledger edge is incoming REFERENCE: contested registry entries refer to a competent forum. It does not transfer registry administration here, certify competence or require a reverse runtime dependency.
- Unlike WM-POL-023 Enforcement Action; WM-ECO-006 Commercial Contract: Mandate and referral references do not authorize enforcement or modification of a dispute clause. Record only the forum-specific binding and cited basis.
- Unlike Mediation and ad hoc tribunals: Mediation is a facilitative profile without presumed power to impose an outcome. An ad hoc tribunal has its own bounded identity distinct from its administering institution and case, with mandate continuity established by evidence.
- Unlike WM-POL-017 Administrative Procedure / Case: An administrative process and its authority are not automatically adjudicative forums; contested referrals use explicit forum and case references.
Note: Derived from boundary notes against neighbouring models.
What robots and AI may and may not do Derived, awaiting review
Must not
- Forum retirement never closes linked cases, annuls decisions or deletes external records.
- Deny restricted record access unless the applicable role, purpose and record-class rule authorize it.
May
- Resolve forum identity: Proposed, unimplemented local operation. Compare evidenced identifiers and alias intervals without merging legally distinct bodies.
- Record mandate assertion: Proposed, unimplemented local operation. Record a sourced scope assertion and its uncertainty; do not determine jurisdiction.
- Check procedure binding: Proposed, unimplemented local operation. Check presence, version and declared compatibility of a procedure offering; do not compute legal deadlines.
- Prepare referral route: Proposed, unimplemented local operation. Assemble a route candidate from declared scope and channels; never file, transfer or serve.
- Prepare authorized forum view: Proposed, unimplemented local operation. Project approved forum metadata while applying record-class and audience restrictions.
- Record forum retirement evidence: Proposed, unimplemented local operation. Record a sourced end-of-mandate or successor assertion without dissolving a legal body or closing cases.
Note: Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.
Moral aspects Derived, awaiting review
- GDPR Article 5 is only a scoped privacy lead; actual applicable privacy and judicial-records regimes need review.
- Reject immutable history as a reason to retain personal data indefinitely.
Note: Sentences mentioning harm, privacy, consent or similar, collected from the specification.
Owners Filled
Steward
The adopting Dimension identifies an accountable forum-record steward by role and master identifier.
Roles
- Forum record steward
- Maintain identity, evidence and policy references within assigned authority.
- Mandate reviewer
- Assess claimed scope and profile applicability; record uncertainty and conflicts.
- Access custodian
- Authorize audience views and redaction under the applicable policy.
- Records custodian
- Apply retention and disposition decisions with source-system responsibility.
- Assisting agent
- Prepare local drafts and checks; refuse unsupported authority or external legal acts.
Links to other meta-models Filled
references
- WM-POL-009 - Link separately mastered cases and case-specific forum assignments; never copy the case lifecycle.
- WM-ORG-001 - Resolve the operating or appointing organization without equating it with the deciding forum.
- WM-POL-020 - Link evidence supporting an assertion without owning exhibit custody or admissibility.
- WM-POL-021 - Link judgment publications and mandate decisions; outcome, finality and remedies remain external.
- WM-POL-023 - Link an enforcement destination only; this model neither orders nor executes coercion.
- WM-ECO-006 - Link relevant clause or agreement evidence; contract authority and lifecycle remain external.
- WM-REC-001 - Resolve mandate and policy documents under their own retention and revision controls.
aligned
- ECLI - Conceptual mapping of court codes and judgment references only; no ECLI conformance or forum identifier equivalence is claimed.
- PROV-O - Conceptual assertion attribution and revision mapping; no implemented RDF binding or validity certification.
neighbor
- WM-POL-009 Court / Arbitration Case - A forum can exist without a case and serve many cases. Case jurisdiction determinations, assignments and calendars reference the forum; they are not owned here. The legacy A19 proceeding root is rejected for this successor.
- WM-ORG-001 Organization - The operating organization and a deciding body need not coincide. Store operator references and the forum mandate, not corporate or personnel masters.
- WM-POL-020 Evidence Item / Exhibit; WM-POL-021 Judgment / Legal Decision - Store pointers to competence or appointment evidence and output publication policies. Case evidence, judgments and their legal effects remain in their own masters; ECLI belongs to judgment references.
- WM-XCT-013 Registry Pattern - The sole ledger edge is incoming REFERENCE: contested registry entries refer to a competent forum. It does not transfer registry administration here, certify competence or require a reverse runtime dependency.
- WM-POL-023 Enforcement Action; WM-ECO-006 Commercial Contract - Mandate and referral references do not authorize enforcement or modification of a dispute clause. Record only the forum-specific binding and cited basis.
- Mediation and ad hoc tribunals - Mediation is a facilitative profile without presumed power to impose an outcome. An ad hoc tribunal has its own bounded identity distinct from its administering institution and case, with mandate continuity established by evidence.
- WM-POL-017 Administrative Procedure / Case - An administrative process and its authority are not automatically adjudicative forums; contested referrals use explicit forum and case references.
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Filled
- Authoritative master-system identifier
- Governed global identifier or IRI
- UUID or ULID assigned by the adopting Dimension
Direct properties not applicable Not applicable
Not applicable
Institutional or informational subject: no invented physical properties.
Recognition optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Filled
- Resolve forum identity: Proposed, unimplemented local operation. Compare evidenced identifiers and alias intervals without merging legally distinct bodies.
- Record mandate assertion: Proposed, unimplemented local operation. Record a sourced scope assertion and its uncertainty; do not determine jurisdiction.
- Check procedure binding: Proposed, unimplemented local operation. Check presence, version and declared compatibility of a procedure offering; do not compute legal deadlines.
- Prepare referral route: Proposed, unimplemented local operation. Assemble a route candidate from declared scope and channels; never file, transfer or serve.
- Prepare authorized forum view: Proposed, unimplemented local operation. Project approved forum metadata while applying record-class and audience restrictions.
- Record forum retirement evidence: Proposed, unimplemented local operation. Record a sourced end-of-mandate or successor assertion without dissolving a legal body or closing cases.
Hazards and failure modes optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Derived, awaiting review
- PROV-O: The PROV Ontology
Context of use required Filled
- CPR examples are limited to the rule scope in England and Wales; ECHR applicability is regional and qualified.
- The admitted arbitration note describes the 1985 Model Law and is informational; no 2006 amendment or domestic enactment equivalence is claimed.
- Mediation is a non-adjudicatory profile; not every forum decides or issues a binding outcome.
- GDPR Article 5 is only a scoped privacy lead; actual applicable privacy and judicial-records regimes need review.
Sources Filled
- European Convention on Human Rights - Council of Europe
- Explanatory Note by the UNCITRAL Secretariat on the Model Law on International Commercial Arbitration - United Nations Commission on International Trade Law
- UNCITRAL Model Law on International Commercial Mediation and International Settlement Agreements Resulting from Mediation with Guide to Enactment and Use - United Nations Commission on International Trade Law
- Civil Procedure Rules Part 2 - Application and Interpretation - Ministry of Justice
- Civil Procedure Rules Part 3 - The Court's Case Management Powers - Ministry of Justice
- Civil Procedure Rules Part 5 - Court Documents - Ministry of Justice
- European Case Law Identifier (ECLI) - European Commission
- PROV-O: The PROV Ontology - World Wide Web Consortium
- Regulation (EU) 2016/679 - European Parliament and Council of the European Union
Open questions
- Verify direct HTTP results, full mediation and privacy text, legal consolidation, effective dates and adopting jurisdiction exceptions without treating retrieval success as substantive verification.
- Develop specialist court, arbitration, mediation and ad hoc profiles that keep operators, panels, cases, decisions and external records distinct.
- Implement and test nested schemas and mappings with mandate disputes, reorganization, sealed records, expired routes, conflicting sources and lawful erasure fixtures.
- Restore independent external review before promotion beyond noncanonical reviewable-draft status.
- Full current legal text and amendment verification for adopting jurisdictions; UNCITRAL mediation and GDPR full retrieval was unavailable.
- Specialist criminal, family, customary, indigenous, religious, consumer and online-forum profiles are not validated.
- Nested field schemas, accepted vocabularies, operational mappings, instance fixtures and quantitative assurance thresholds remain to be designed.
- Independent second-provider review is absent under the owner waiver.
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-pol-010-dispute-forum/spec.yaml