# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T17:02:11Z", "synthesisSha256": "5161873a60108dd5fbe064dd3a81b8205413452f261b785e388268be9d8aa3d0", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-POL-010", "registryId": "vr.wm-pol-010", "name": "Dispute Forum", "version": "0.1.0", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Society, people and institutions", "industry": [ "Cross-industry" ], "domain": [ "SOC.POL.FOR" ], "tags": [ "dispute", "forum", "soc.pol.for" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-pol-010-dispute-forum/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-pol-010", "model": { "registry_id": "vr.wm-pol-010", "model_id": "WM-POL-010", "name": "Dispute Forum", "entry_kind": "entity", "purpose": "Describe an identifiable dispute-resolution forum, its mandate, competence, procedural offerings and accountable record stewardship.", "scope_statement": "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" ], "boundary_notes": [ { "neighbor": "WM-POL-009 Court / Arbitration Case", "distinction": "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.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ] }, { "neighbor": "WM-ORG-001 Organization", "distinction": "The operating organization and a deciding body need not coincide. Store operator references and the forum mandate, not corporate or personnel masters.", "source_refs": [ "SRC-002", "SRC-004" ] }, { "neighbor": "WM-POL-020 Evidence Item / Exhibit; WM-POL-021 Judgment / Legal Decision", "distinction": "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.", "source_refs": [ "SRC-006", "SRC-007", "SRC-008" ] }, { "neighbor": "WM-XCT-013 Registry Pattern", "distinction": "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.", "source_refs": [ "SRC-002", "SRC-008" ] }, { "neighbor": "WM-POL-023 Enforcement Action; WM-ECO-006 Commercial Contract", "distinction": "Mandate and referral references do not authorize enforcement or modification of a dispute clause. Record only the forum-specific binding and cited basis.", "source_refs": [ "SRC-002" ] }, { "neighbor": "Mediation and ad hoc tribunals", "distinction": "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.", "source_refs": [ "SRC-002", "SRC-003" ] }, { "neighbor": "WM-POL-017 Administrative Procedure / Case", "distinction": "An administrative process and its authority are not automatically adjudicative forums; contested referrals use explicit forum and case references.", "source_refs": [ "SRC-001", "SRC-004" ] } ] }, "sources": [ { "id": "SRC-001", "title": "European Convention on Human Rights", "organization": "Council of Europe", "url": "https://www.echr.coe.int/documents/d/echr/convention_ENG", "version_or_date": "Convention of 1950; retrieved English compilation, consolidation currency unverified", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T17:00:40Z", "relevance": "Article 6: qualified fair-hearing, independence and publicity baseline; Article 8: privacy. These are regional obligations, not a universal forum ontology." }, { "id": "SRC-002", "title": "Explanatory Note by the UNCITRAL Secretariat on the Model Law on International Commercial Arbitration", "organization": "United Nations Commission on International Trade Law", "url": "https://sice.oas.org/DISPUTE/comarb/uncitral/icomarbe3.asp", "version_or_date": "1985 Model Law explanatory note, reproduced by the Organization of American States; not the amended 2006 text", "source_type": "public-authority", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-06T17:00:40Z", "relevance": "Paragraphs 12-16, 22-32 and 40-44: mandate, appointment, challenge, procedure and supervision distinctions. Informational Secretariat note, not an official commentary or enacted law." }, { "id": "SRC-003", "title": "UNCITRAL Model Law on International Commercial Mediation and International Settlement Agreements Resulting from Mediation with Guide to Enactment and Use", "organization": "United Nations Commission on International Trade Law", "url": "https://uncitral.un.org/sites/default/files/media-documents/uncitral/en/22-01363_mediation_guide_e_ebook_rev.pdf", "version_or_date": "2018 Model Law and guide publication 2022; indexed excerpt only", "source_type": "public-authority", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-06T17:00:40Z", "relevance": "Guide paragraphs 10-12 support the non-adjudicatory mediator boundary and party control of outcome. Full PDF retrieval failed; only this narrow indexed passage is admitted." }, { "id": "SRC-004", "title": "Civil Procedure Rules Part 2 - Application and Interpretation", "organization": "Ministry of Justice", "url": "https://www.justice.gov.uk/courts/procedure-rules/civil/rules/part02", "version_or_date": "Online text accessed 2026-10-06; amendment and commencement pin pending", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T17:00:40Z", "relevance": "Rules 2.1 and 2.4-2.9 distinguish court scope, authorized actors, place and time conventions in England and Wales." }, { "id": "SRC-005", "title": "Civil Procedure Rules Part 3 - The Court's Case Management Powers", "organization": "Ministry of Justice", "url": "https://www.justice.gov.uk/courts/procedure-rules/civil/rules/part03-", "version_or_date": "Online text accessed 2026-10-06; amendment and commencement pin pending", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T17:00:40Z", "relevance": "Rules 3.1 and 3.1A illustrate court powers, stays, consolidation, procedural adaptation and unrepresented participants. Powers are not agent permissions." }, { "id": "SRC-006", "title": "Civil Procedure Rules Part 5 - Court Documents", "organization": "Ministry of Justice", "url": "https://www.justice.gov.uk/courts/procedure-rules/civil/rules/part05", "version_or_date": "Online text accessed 2026-10-06; amendment and commencement pin pending", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T17:00:40Z", "relevance": "Rules 5.4B-5.5 distinguish party and non-party access, permission, restrictions and filing channels; no universal complete party view is implied." }, { "id": "SRC-007", "title": "European Case Law Identifier (ECLI)", "organization": "European Commission", "url": "https://e-justice.europa.eu/topics/legislation-and-case-law/european-case-law-identifier-ecli_en", "version_or_date": "Page last updated 2021-11-17; accessed 2026-10-06", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-06T17:00:40Z", "relevance": "Court codes occur within judgment identifiers and are governed by national coordination. ECLI identifies judgments, not the forum itself or a case." }, { "id": "SRC-008", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/2013/REC-prov-o-20130430/", "version_or_date": "W3C Recommendation 2013-04-30", "source_type": "ontology", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-06T17:00:40Z", "relevance": "Entity, agent, attribution and revision relationships support provenance of forum descriptions. Provenance does not certify legal authority or truth." }, { "id": "SRC-009", "title": "Regulation (EU) 2016/679", "organization": "European Parliament and Council of the European Union", "url": "https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng/", "version_or_date": "2016-04-27 original act; Article 5 indexed excerpt; full retrieval challenged", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T17:00:40Z", "relevance": "Article 5 storage limitation is a scoped privacy lead for forum records. Applicable regime, exceptions and current text remain unverified; it does not prescribe one retention period." } ], "structure": { "bundles": [ { "id": "forum-identity-bundle", "name": "Identity and continuity", "description": "Recognize one forum across labels, locations and mandate revisions.", "rationale": "Groups forum-owned context; linked case execution and external master lifecycles remain outside this model.", "source_refs": [ "SRC-004", "SRC-007", "SRC-008" ], "layers": [ { "id": "forum-identity-layer", "name": "Forum identity", "description": "Resolve forum identifiers and classification independently from cases, judgments and operators.", "source_refs": [ "SRC-004", "SRC-007", "SRC-008" ], "findings": [ { "id": "forum-identity-finding", "name": "Forum identity", "description": "Resolve forum identifiers and classification independently from cases, judgments and operators.", "source_refs": [ "SRC-004", "SRC-007", "SRC-008" ], "questions": [ { "id": "forum-identity-question-1", "text": "Which master identifier denotes this forum rather than its operator, a case or a judgment?", "kind": "identity", "answer_data": [ "forum_id", "identifier_authority", "operator_ref" ] }, { "id": "forum-identity-question-2", "text": "Is this a court, tribunal, administering body, ad hoc tribunal or facilitative forum?", "kind": "classification", "answer_data": [ "forum_kind", "profile_ref", "classification_basis" ] }, { "id": "forum-identity-question-3", "text": "Which names, court codes and former identifiers are evidenced aliases for this same forum?", "kind": "interoperability", "answer_data": [ "alias", "issuer", "valid_interval", "mapping_evidence" ] } ], "data_elements": [ { "id": "forum-identity-data-forum-id", "name": "forum-id", "description": "Candidate forum-id for forum identity. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-007", "SRC-008" ] }, { "id": "forum-identity-data-forum-kind", "name": "forum-kind", "description": "Candidate forum-kind for forum identity. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-007", "SRC-008" ] }, { "id": "forum-identity-data-aliases", "name": "aliases", "description": "Candidate aliases for forum identity. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "forum-identity-artifact", "name": "Identity profile", "description": "Versioned forum-level evidence view for forum identity. Referenced case and document payloads stay in their master systems.", "media_or_form": [ "structured record", "governed document reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; Dimension-assigned UUID or ULID last. Artifact identity and revision identity are separate; retain evidence and effective interval.", "source_refs": [ "SRC-004", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "forum-continuity-layer", "name": "Establishment and continuity", "description": "Track establishment, suspension, retirement and successors as evidenced assertions; a rename or case closure alone does not determine forum identity.", "source_refs": [ "SRC-004", "SRC-008" ], "findings": [ { "id": "forum-continuity-finding", "name": "Establishment and continuity", "description": "Track establishment, suspension, retirement and successors as evidenced assertions; a rename or case closure alone does not determine forum identity.", "source_refs": [ "SRC-004", "SRC-008" ], "questions": [ { "id": "forum-continuity-question-1", "text": "What instrument establishes, suspends or ends the forum mandate?", "kind": "lifecycle", "answer_data": [ "instrument_ref", "asserted_state", "effective_interval", "verification_state" ] }, { "id": "forum-continuity-question-2", "text": "When did the mandate change take effect and when was that evidence recorded?", "kind": "temporal", "answer_data": [ "effective_time", "recorded_time", "precision", "source_ref" ] }, { "id": "forum-continuity-question-3", "text": "Does a merger, replacement or rename preserve this identity or require a distinct successor forum?", "kind": "relationship", "answer_data": [ "change_kind", "successor_ref", "continuity_decision_ref" ] } ], "data_elements": [ { "id": "forum-continuity-data-mandate-history", "name": "mandate-history", "description": "Candidate mandate-history for establishment and continuity. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-004", "SRC-008" ] }, { "id": "forum-continuity-data-successor-refs", "name": "successor-refs", "description": "Candidate successor-refs for establishment and continuity. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "forum-continuity-artifact", "name": "Continuity register", "description": "Versioned forum-level evidence view for establishment and continuity. Referenced case and document payloads stay in their master systems.", "media_or_form": [ "structured record", "governed document reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; Dimension-assigned UUID or ULID last. Artifact identity and revision identity are separate; retain evidence and effective interval.", "source_refs": [ "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "forum-mandate-bundle", "name": "Mandate and competence", "description": "Describe claimed powers with scope, evidence and unresolved limitations.", "rationale": "Groups forum-owned context; linked case execution and external master lifecycles remain outside this model.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005" ], "layers": [ { "id": "forum-competence-layer", "name": "Competence envelope", "description": "A forum-level competence description is distinct from a binding jurisdiction determination for a particular case.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "findings": [ { "id": "forum-competence-finding", "name": "Competence envelope", "description": "A forum-level competence description is distinct from a binding jurisdiction determination for a particular case.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "questions": [ { "id": "forum-competence-question-1", "text": "Which legal instrument, agreement or designation supports each claimed competence?", "kind": "authority", "answer_data": [ "competence_ref", "basis_ref", "issuing_authority_ref", "verification_state" ] }, { "id": "forum-competence-question-2", "text": "What territorial, subject, person, value or temporal limits and exclusions qualify that competence?", "kind": "constraint", "answer_data": [ "scope_dimensions", "exclusions", "effective_interval", "unknown_dimensions" ] }, { "id": "forum-competence-question-3", "text": "Where must contested or uncertain competence be referred for an authorized determination?", "kind": "exception", "answer_data": [ "question_scope", "review_route_ref", "determining_body_ref" ] } ], "data_elements": [ { "id": "forum-competence-data-competence-claims", "name": "competence-claims", "description": "Candidate competence-claims for competence envelope. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "forum-competence-data-competence-review-route", "name": "competence-review-route", "description": "Candidate competence-review-route for competence envelope. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "artifacts": [ { "id": "forum-competence-artifact", "name": "Competence statement", "description": "Versioned forum-level evidence view for competence envelope. Referenced case and document payloads stay in their master systems.", "media_or_form": [ "structured record", "governed document reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; Dimension-assigned UUID or ULID last. Artifact identity and revision identity are separate; retain evidence and effective interval.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "forum-capability-layer", "name": "Resolution powers and limits", "description": "Separate adjudication, facilitation, administration and review capacities. Recorded capacity neither exercises a power nor guarantees a remedy.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ], "findings": [ { "id": "forum-capability-finding", "name": "Resolution powers and limits", "description": "Separate adjudication, facilitation, administration and review capacities. Recorded capacity neither exercises a power nor guarantees a remedy.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ], "questions": [ { "id": "forum-capability-question-1", "text": "Which functions can this forum decide, facilitate, administer or only refer?", "kind": "definition", "answer_data": [ "function_kind", "capacity_scope", "authority_ref" ] }, { "id": "forum-capability-question-2", "text": "Which conditions or consents qualify each offered procedure and its possible outcome?", "kind": "requirement", "answer_data": [ "procedure_ref", "conditions", "consent_basis_ref", "outcome_class" ] }, { "id": "forum-capability-question-3", "text": "How is a claimed binding power rejected when the selected profile only permits mediation or administration?", "kind": "validation", "answer_data": [ "power_claim", "profile_rule", "reviewer_ref", "validation_result" ] } ], "data_elements": [ { "id": "forum-capability-data-offered-capacities", "name": "offered-capacities", "description": "Candidate offered-capacities for resolution powers and limits. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] }, { "id": "forum-capability-data-authority-limitations", "name": "authority-limitations", "description": "Candidate authority-limitations for resolution powers and limits. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "forum-capability-artifact", "name": "Capability profile", "description": "Versioned forum-level evidence view for resolution powers and limits. Referenced case and document payloads stay in their master systems.", "media_or_form": [ "structured record", "governed document reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; Dimension-assigned UUID or ULID last. Artifact identity and revision identity are separate; retain evidence and effective interval.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "forum-governance-bundle", "name": "Governance and independence", "description": "Describe authorized roles, composition rules and impartiality safeguards without managing case appointments.", "rationale": "Groups forum-owned context; linked case execution and external master lifecycles remain outside this model.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "layers": [ { "id": "forum-composition-layer", "name": "Composition and role authority", "description": "Keep the forum operator, appointment authority and adjudicating roles distinct; particular appointments are referenced records.", "source_refs": [ "SRC-002", "SRC-004" ], "findings": [ { "id": "forum-composition-finding", "name": "Composition and role authority", "description": "Keep the forum operator, appointment authority and adjudicating roles distinct; particular appointments are referenced records.", "source_refs": [ "SRC-002", "SRC-004" ], "questions": [ { "id": "forum-composition-question-1", "text": "Which operating, appointing and deciding bodies or roles are related to this forum?", "kind": "composition", "answer_data": [ "operator_ref", "appointing_authority_ref", "role_definition_ref" ] }, { "id": "forum-composition-question-2", "text": "What qualifications, composition rules and delegation limits apply to each forum role?", "kind": "authority", "answer_data": [ "role_ref", "qualification_policy_ref", "composition_rule_ref", "delegation_limit" ] }, { "id": "forum-composition-question-3", "text": "Which vacancies or mandate restrictions affect the forum capacity at the observation time?", "kind": "state", "answer_data": [ "capacity_state", "restriction_ref", "observed_at", "unknown_state" ] } ], "data_elements": [ { "id": "forum-composition-data-role-bindings", "name": "role-bindings", "description": "Candidate role-bindings for composition and role authority. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-002", "SRC-004" ] }, { "id": "forum-composition-data-capacity-restrictions", "name": "capacity-restrictions", "description": "Candidate capacity-restrictions for composition and role authority. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004" ] } ], "artifacts": [ { "id": "forum-composition-artifact", "name": "Role and composition policy", "description": "Versioned forum-level evidence view for composition and role authority. Referenced case and document payloads stay in their master systems.", "media_or_form": [ "structured record", "governed document reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; Dimension-assigned UUID or ULID last. Artifact identity and revision identity are separate; retain evidence and effective interval.", "source_refs": [ "SRC-002", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "forum-independence-layer", "name": "Independence and challenge safeguards", "description": "Document independence arrangements and conflict disclosure or challenge routes; a policy assertion does not prove impartiality in any case.", "source_refs": [ "SRC-001", "SRC-002" ], "findings": [ { "id": "forum-independence-finding", "name": "Independence and challenge safeguards", "description": "Document independence arrangements and conflict disclosure or challenge routes; a policy assertion does not prove impartiality in any case.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "forum-independence-question-1", "text": "What arrangements support institutional independence and impartial decision making for this profile?", "kind": "requirement", "answer_data": [ "safeguard_ref", "applicable_profile", "assessment_ref" ] }, { "id": "forum-independence-question-2", "text": "How are disclosure, challenge, recusal and replacement requests routed without determining them here?", "kind": "process", "answer_data": [ "route_ref", "authorized_recipient_role", "governing_rule_ref" ] }, { "id": "forum-independence-question-3", "text": "What controls separate case communications, deliberations and administrative access?", "kind": "security", "answer_data": [ "communication_policy_ref", "separation_rule", "exception_authority_ref" ] } ], "data_elements": [ { "id": "forum-independence-data-safeguard-refs", "name": "safeguard-refs", "description": "Candidate safeguard-refs for independence and challenge safeguards. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "reference", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "forum-independence-data-challenge-routes", "name": "challenge-routes", "description": "Candidate challenge-routes for independence and challenge safeguards. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "forum-independence-artifact", "name": "Independence safeguards record", "description": "Versioned forum-level evidence view for independence and challenge safeguards. Referenced case and document payloads stay in their master systems.", "media_or_form": [ "structured record", "governed document reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; Dimension-assigned UUID or ULID last. Artifact identity and revision identity are separate; retain evidence and effective interval.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "forum-procedure-bundle", "name": "Procedural offerings and routing", "description": "Describe procedure profiles and incoming or outgoing pathways without implementing case workflow.", "rationale": "Groups forum-owned context; linked case execution and external master lifecycles remain outside this model.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-006" ], "layers": [ { "id": "forum-rules-layer", "name": "Applicable procedure profiles", "description": "Pin the offered rules and their scope. Case-specific selections, modifications and time calculations remain in the case master.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ], "findings": [ { "id": "forum-rules-finding", "name": "Applicable procedure profiles", "description": "Pin the offered rules and their scope. Case-specific selections, modifications and time calculations remain in the case master.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ], "questions": [ { "id": "forum-rules-question-1", "text": "Which procedure version is offered and what evidence supports its effective scope?", "kind": "provenance", "answer_data": [ "rule_set_ref", "version", "effective_interval", "source_ref" ] }, { "id": "forum-rules-question-2", "text": "How are mandatory rules, permitted variations and superseded procedure versions distinguished?", "kind": "constraint", "answer_data": [ "precedence_policy_ref", "variation_scope", "superseded_ref" ] }, { "id": "forum-rules-question-3", "text": "Which calendar and time-zone conventions must a linked case resolve before relying on a deadline?", "kind": "temporal", "answer_data": [ "calendar_binding_ref", "zone", "cutoff_policy_ref", "case_responsibility" ] } ], "data_elements": [ { "id": "forum-rules-data-procedure-offerings", "name": "procedure-offerings", "description": "Candidate procedure-offerings for applicable procedure profiles. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ] }, { "id": "forum-rules-data-calendar-policy-ref", "name": "calendar-policy-ref", "description": "Candidate calendar-policy-ref for applicable procedure profiles. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "forum-rules-artifact", "name": "Procedure offering register", "description": "Versioned forum-level evidence view for applicable procedure profiles. Referenced case and document payloads stay in their master systems.", "media_or_form": [ "structured record", "governed document reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; Dimension-assigned UUID or ULID last. Artifact identity and revision identity are separate; retain evidence and effective interval.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "forum-routing-layer", "name": "Intake and review pathways", "description": "Publish qualified routes for intake, registry objections, referrals and review, without opening a case or changing legal status.", "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ], "findings": [ { "id": "forum-routing-finding", "name": "Intake and review pathways", "description": "Publish qualified routes for intake, registry objections, referrals and review, without opening a case or changing legal status.", "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ], "questions": [ { "id": "forum-routing-question-1", "text": "Which case system and competent recipient receive each class of referral or contested registry entry?", "kind": "relationship", "answer_data": [ "referral_class", "recipient_ref", "case_system_ref", "basis_ref" ] }, { "id": "forum-routing-question-2", "text": "What submission prerequisites, acknowledgement limits and escalation routes does each channel declare?", "kind": "process", "answer_data": [ "channel_ref", "prerequisites", "acknowledgement_meaning", "escalation_ref" ] }, { "id": "forum-routing-question-3", "text": "Which forum handles a challenge or referral when the normal route is unavailable or disputed?", "kind": "exception", "answer_data": [ "route_scope", "alternative_forum_ref", "authorizing_basis_ref", "unresolved_status" ] } ], "data_elements": [ { "id": "forum-routing-data-routing-bindings", "name": "routing-bindings", "description": "Candidate routing-bindings for intake and review pathways. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ] }, { "id": "forum-routing-data-intake-policy-ref", "name": "intake-policy-ref", "description": "Candidate intake-policy-ref for intake and review pathways. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "forum-routing-artifact", "name": "Routing directory", "description": "Versioned forum-level evidence view for intake and review pathways. Referenced case and document payloads stay in their master systems.", "media_or_form": [ "structured record", "governed document reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; Dimension-assigned UUID or ULID last. Artifact identity and revision identity are separate; retain evidence and effective interval.", "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "forum-accessibility-bundle", "name": "Locations and participation", "description": "Separate operational channels and declared access arrangements from legal place and case entitlements.", "rationale": "Groups forum-owned context; linked case execution and external master lifecycles remain outside this model.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006" ], "layers": [ { "id": "forum-location-layer", "name": "Place and communication channels", "description": "Administrative location, hearing venue, remote channel and juridical place are distinct. A forum need not have a single fixed arbitration seat.", "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ], "findings": [ { "id": "forum-location-finding", "name": "Place and communication channels", "description": "Administrative location, hearing venue, remote channel and juridical place are distinct. A forum need not have a single fixed arbitration seat.", "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ], "questions": [ { "id": "forum-location-question-1", "text": "Which addresses, hearing locations and remote channels are valid for the stated forum function?", "kind": "spatial", "answer_data": [ "location_ref", "channel_ref", "purpose", "valid_interval" ] }, { "id": "forum-location-question-2", "text": "Which legal place is fixed by the forum profile and which must be resolved separately for each case?", "kind": "constraint", "answer_data": [ "place_kind", "profile_place_ref", "case_place_ref", "basis_ref" ] }, { "id": "forum-location-question-3", "text": "When were channel availability and contact authority last checked and what remains unknown?", "kind": "quality", "answer_data": [ "checked_at", "checker_role", "evidence_ref", "availability_state" ] } ], "data_elements": [ { "id": "forum-location-data-location-bindings", "name": "location-bindings", "description": "Candidate location-bindings for place and communication channels. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] }, { "id": "forum-location-data-channel-bindings", "name": "channel-bindings", "description": "Candidate channel-bindings for place and communication channels. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "forum-location-artifact", "name": "Location and channel directory", "description": "Versioned forum-level evidence view for place and communication channels. Referenced case and document payloads stay in their master systems.", "media_or_form": [ "structured record", "governed document reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; Dimension-assigned UUID or ULID last. Artifact identity and revision identity are separate; retain evidence and effective interval.", "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "forum-participation-layer", "name": "Participation support and costs", "description": "Record available language, assistance and cost-policy references. Availability is distinct from a legal entitlement or case-specific grant.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006" ], "findings": [ { "id": "forum-participation-finding", "name": "Participation support and costs", "description": "Record available language, assistance and cost-policy references. Availability is distinct from a legal entitlement or case-specific grant.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006" ], "questions": [ { "id": "forum-participation-question-1", "text": "Which language, interpretation, accessibility and unrepresented-party support arrangements are declared?", "kind": "access", "answer_data": [ "support_type", "policy_ref", "eligibility_ref", "service_contact_ref" ] }, { "id": "forum-participation-question-2", "text": "Which published fees, assistance or waiver policies apply to the selected service and profile?", "kind": "requirement", "answer_data": [ "service_ref", "fee_schedule_ref", "waiver_policy_ref", "effective_interval" ] }, { "id": "forum-participation-question-3", "text": "How can a participant report an access barrier or request an accommodation without exposing case details publicly?", "kind": "exception", "answer_data": [ "request_channel_ref", "recipient_role", "privacy_rule_ref", "escalation_ref" ] } ], "data_elements": [ { "id": "forum-participation-data-support-policy-refs", "name": "support-policy-refs", "description": "Candidate support-policy-refs for participation support and costs. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006" ] }, { "id": "forum-participation-data-cost-policy-refs", "name": "cost-policy-refs", "description": "Candidate cost-policy-refs for participation support and costs. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "forum-participation-artifact", "name": "Participation policy index", "description": "Versioned forum-level evidence view for participation support and costs. Referenced case and document payloads stay in their master systems.", "media_or_form": [ "structured record", "governed document reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; Dimension-assigned UUID or ULID last. Artifact identity and revision identity are separate; retain evidence and effective interval.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "forum-stewardship-bundle", "name": "Records and accountability", "description": "Govern forum descriptions and publication interfaces while preserving case and document ownership.", "rationale": "Groups forum-owned context; linked case execution and external master lifecycles remain outside this model.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-008", "SRC-009" ], "layers": [ { "id": "forum-publication-layer", "name": "Record access and publication rules", "description": "Distinguish public forum information from restricted appointment records, case files and deliberations; public hearing does not imply public access to every document.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-009" ], "findings": [ { "id": "forum-publication-finding", "name": "Record access and publication rules", "description": "Distinguish public forum information from restricted appointment records, case files and deliberations; public hearing does not imply public access to every document.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-009" ], "questions": [ { "id": "forum-publication-question-1", "text": "Which custodian controls forum metadata and which external master controls each linked case or decision record?", "kind": "ownership", "answer_data": [ "record_class", "custodian_role", "master_ref", "responsibility_basis" ] }, { "id": "forum-publication-question-2", "text": "What rule permits or restricts each audience view, including redaction and special case exceptions?", "kind": "privacy", "answer_data": [ "audience", "record_class", "rule_ref", "redaction_policy_ref", "exception_ref" ] }, { "id": "forum-publication-question-3", "text": "Which public decision index and court-code mapping can be linked without treating ECLI as a forum identifier?", "kind": "interoperability", "answer_data": [ "index_ref", "court_code", "code_authority_ref", "mapping_scope" ] } ], "data_elements": [ { "id": "forum-publication-data-custody-bindings", "name": "custody-bindings", "description": "Candidate custody-bindings for record access and publication rules. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-009" ] }, { "id": "forum-publication-data-view-policy-refs", "name": "view-policy-refs", "description": "Candidate view-policy-refs for record access and publication rules. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "reference", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-009" ] } ], "artifacts": [ { "id": "forum-publication-artifact", "name": "Access and publication policy", "description": "Versioned forum-level evidence view for record access and publication rules. Referenced case and document payloads stay in their master systems.", "media_or_form": [ "structured record", "governed document reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; Dimension-assigned UUID or ULID last. Artifact identity and revision identity are separate; retain evidence and effective interval.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "forum-assurance-layer", "name": "Evidence, review and disposition", "description": "Maintain attributable forum assertions, review dates and lawful retention decisions. Revision history is not permission for perpetual personal-data retention.", "source_refs": [ "SRC-008", "SRC-009" ], "findings": [ { "id": "forum-assurance-finding", "name": "Evidence, review and disposition", "description": "Maintain attributable forum assertions, review dates and lawful retention decisions. Revision history is not permission for perpetual personal-data retention.", "source_refs": [ "SRC-008", "SRC-009" ], "questions": [ { "id": "forum-assurance-question-1", "text": "What source, author, review state and observation time support each forum assertion?", "kind": "evidence", "answer_data": [ "assertion_id", "source_ref", "author_role", "review_state", "observed_at" ] }, { "id": "forum-assurance-question-2", "text": "How are coverage, freshness and unresolved mandate assertions measured without claiming legal validity?", "kind": "measurement", "answer_data": [ "metric_definition", "population", "as_of", "unknown_count", "review_result" ] }, { "id": "forum-assurance-question-3", "text": "Which retention basis, hold or disposition decision applies to forum records when a mandate expires?", "kind": "retention", "answer_data": [ "record_class", "retention_policy_ref", "hold_ref", "decision_ref", "successor_custodian_ref" ] } ], "data_elements": [ { "id": "forum-assurance-data-assertion-evidence", "name": "assertion-evidence", "description": "Candidate assertion-evidence for evidence, review and disposition. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-008", "SRC-009" ] }, { "id": "forum-assurance-data-disposition-policy-ref", "name": "disposition-policy-ref", "description": "Candidate disposition-policy-ref for evidence, review and disposition. Values require an adopting profile, source attribution and an explicit unknown state; nested schema remains a conformance hold.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-008", "SRC-009" ] } ], "artifacts": [ { "id": "forum-assurance-artifact", "name": "Forum assurance register", "description": "Versioned forum-level evidence view for evidence, review and disposition. Referenced case and document payloads stay in their master systems.", "media_or_form": [ "structured record", "governed document reference" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; Dimension-assigned UUID or ULID last. Artifact identity and revision identity are separate; retain evidence and effective interval.", "source_refs": [ "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "forum-function-resolve", "name": "Resolve forum identity", "description": "Proposed, unimplemented local operation. Compare evidenced identifiers and alias intervals without merging legally distinct bodies.", "inputs": [ "forum identifiers", "alias evidence", "operator and case references" ], "outputs": [ "Identity candidate or unresolved conflict" ], "preconditions": [ "Authorized adopting-Dimension role and purpose are verified.", "Evidence, applicable policy and expected record revision are supplied; unknown authority or concurrent revision causes refusal." ], "effects": [ "Produce an attributable local identity assessment.", "No local operation grants legal power or performs an external action." ], "source_refs": [ "SRC-007", "SRC-008" ] }, { "id": "forum-function-mandate", "name": "Record mandate assertion", "description": "Proposed, unimplemented local operation. Record a sourced scope assertion and its uncertainty; do not determine jurisdiction.", "inputs": [ "mandate reference", "scope and exclusions", "effective interval" ], "outputs": [ "Versioned mandate assertion or refusal" ], "preconditions": [ "Authorized adopting-Dimension role and purpose are verified.", "Evidence, applicable policy and expected record revision are supplied; unknown authority or concurrent revision causes refusal." ], "effects": [ "Create a local proposed record revision with provenance.", "No local operation grants legal power or performs an external action." ], "source_refs": [ "SRC-002", "SRC-004", "SRC-008" ] }, { "id": "forum-function-profile", "name": "Check procedure binding", "description": "Proposed, unimplemented local operation. Check presence, version and declared compatibility of a procedure offering; do not compute legal deadlines.", "inputs": [ "procedure version", "forum mandate revision", "adopting profile" ], "outputs": [ "Binding report with unresolved checks" ], "preconditions": [ "Authorized adopting-Dimension role and purpose are verified.", "Evidence, applicable policy and expected record revision are supplied; unknown authority or concurrent revision causes refusal." ], "effects": [ "Return a read-only structural assessment; no case workflow is changed.", "No local operation grants legal power or performs an external action." ], "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ] }, { "id": "forum-function-route", "name": "Prepare referral route", "description": "Proposed, unimplemented local operation. Assemble a route candidate from declared scope and channels; never file, transfer or serve.", "inputs": [ "referral class", "channel evidence", "forum scope" ], "outputs": [ "Route preview or unresolved destination" ], "preconditions": [ "Authorized adopting-Dimension role and purpose are verified.", "Evidence, applicable policy and expected record revision are supplied; unknown authority or concurrent revision causes refusal." ], "effects": [ "Create a local preview requiring authorized review before any external action.", "No local operation grants legal power or performs an external action." ], "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ] }, { "id": "forum-function-view", "name": "Prepare authorized forum view", "description": "Proposed, unimplemented local operation. Project approved forum metadata while applying record-class and audience restrictions.", "inputs": [ "requester role", "purpose", "policy revision", "forum record revision" ], "outputs": [ "Filtered local view or refusal" ], "preconditions": [ "Authorized adopting-Dimension role and purpose are verified.", "Evidence, applicable policy and expected record revision are supplied; unknown authority or concurrent revision causes refusal." ], "effects": [ "Return only policy-authorized forum data; linked case access is evaluated by its own master.", "No local operation grants legal power or performs an external action." ], "source_refs": [ "SRC-006", "SRC-009" ] }, { "id": "forum-function-retire", "name": "Record forum retirement evidence", "description": "Proposed, unimplemented local operation. Record a sourced end-of-mandate or successor assertion without dissolving a legal body or closing cases.", "inputs": [ "retirement instrument", "successor reference", "retention decision" ], "outputs": [ "Retirement proposal or refusal" ], "preconditions": [ "Authorized adopting-Dimension role and purpose are verified.", "Evidence, applicable policy and expected record revision are supplied; unknown authority or concurrent revision causes refusal." ], "effects": [ "Preserve identifiers and lawful references; external case and disposition actions remain delegated.", "No local operation grants legal power or performs an external action." ], "source_refs": [ "SRC-004", "SRC-008", "SRC-009" ] } ], "composition": [ { "target": "WM-POL-009", "relation": "REFERENCE", "purpose": "Link separately mastered cases and case-specific forum assignments; never copy the case lifecycle.", "required": false, "source_refs": [ "SRC-002", "SRC-005" ] }, { "target": "WM-ORG-001", "relation": "REFERENCE", "purpose": "Resolve the operating or appointing organization without equating it with the deciding forum.", "required": false, "source_refs": [ "SRC-002", "SRC-004" ] }, { "target": "WM-POL-020", "relation": "REFERENCE", "purpose": "Link evidence supporting an assertion without owning exhibit custody or admissibility.", "required": false, "source_refs": [ "SRC-008" ] }, { "target": "WM-POL-021", "relation": "REFERENCE", "purpose": "Link judgment publications and mandate decisions; outcome, finality and remedies remain external.", "required": false, "source_refs": [ "SRC-007" ] }, { "target": "WM-POL-023", "relation": "REFERENCE", "purpose": "Link an enforcement destination only; this model neither orders nor executes coercion.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "WM-ECO-006", "relation": "REFERENCE", "purpose": "Link relevant clause or agreement evidence; contract authority and lifecycle remain external.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "WM-REC-001", "relation": "REFERENCE", "purpose": "Resolve mandate and policy documents under their own retention and revision controls.", "required": false, "source_refs": [ "SRC-006", "SRC-008" ] }, { "target": "ECLI", "relation": "ALIGN", "purpose": "Conceptual mapping of court codes and judgment references only; no ECLI conformance or forum identifier equivalence is claimed.", "required": false, "source_refs": [ "SRC-007" ] }, { "target": "PROV-O", "relation": "ALIGN", "purpose": "Conceptual assertion attribution and revision mapping; no implemented RDF binding or validity certification.", "required": false, "source_refs": [ "SRC-008" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "The adopting Dimension identifies an accountable forum-record steward by role and master identifier.", "Declare jurisdiction/profile, evidence reviewers, access policy and lawful disposition authority.", "Publish versioned schema and binding choices with unresolved dependencies and review holds." ], "namespace_guidance": "Use a stable adopting-Dimension namespace for forum and artifact identifiers. Labels, dates, court codes and operator names alone are not identity.", "registry_links": [ "vr.wm-pol-010", "WM-POL-009 case reference", "WM-XCT-013 incoming competent-forum reference" ] }, "canon_and_patch": { "canonicalization_rules": [ "Normalize syntax only; preserve original labels, evidence, effective intervals and uncertainty. Never convert a claimed mandate into verified competence.", "The research package remains a noncanonical reviewable draft while any hold is open." ], "patch_rules": [ "Require role, purpose, base revision, rationale and source reference for each patch; reject stale writes and retain review state.", "Changing forum identity, role authority, procedure scope or access requires an explicit reviewed revision." ], "compatibility_rules": [ "Keep historical references resolvable subject to lawful retention; distinguish a correction from a successor forum.", "Pin external schema/model bindings before instance use; incompatible changes need explicit migration and review." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier", "Governed global identifier or IRI", "UUID or ULID assigned by the adopting Dimension" ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and an explicit offset or Z. Keep event/effective time distinct from observation/ingestion time; retain time-zone, precision and unknown values. Do not invent a timestamp for a date-only legal instrument.", "serial_naming_rule": "Use stable artifact identifiers plus separate revision identifiers and media suffixes. A date or content digest alone is not identity.", "integrity_rule": "Preserve source master references, revision and content digest where available; verify signatures with a specified trust profile. A digest proves neither authority nor legal effect." }, "policies": [ "Keep operator, forum, panel assignment, case, judgment and enforcement identities distinct.", "Default to the narrowest evidenced authority and explicit unknowns; no autonomous adjudication, filing, service, appointment or ex parte case contact.", "Treat dangerous or coercive subject matter only as policy categories and external references.", "No brand or company is designated as an owner; owner roles and adopting-Dimension authority are configurable.", "Independent external review, source/version verification, jurisdiction profile and executable conformance remain holds." ], "crud": { "read": [ "Read only permitted forum records for the declared audience and purpose; a public forum directory does not open linked case files." ], "create": [ "Require master identity, classification, mandate evidence or explicit pending verification, custodian and access policy; create a proposed record without legal establishment." ], "update": [ "Version mandate assertions, routes and policies using concurrency checks; preserve contradictions and source timestamps without backdating." ], "delete": [ "Apply the adopting-Dimension retention schedule, legal holds and data minimization before deletion of forum record payloads. Disposition execution belongs to the authorized records master.", "Retire identifiers or retain minimal lawful tombstones where permitted; erase protected payloads when lawfully required, including unnecessary history. Forum retirement never closes linked cases, annuls decisions or deletes external records." ] }, "roles": [ { "name": "Forum record steward", "responsibilities": [ "Maintain identity, evidence and policy references within assigned authority." ] }, { "name": "Mandate reviewer", "responsibilities": [ "Assess claimed scope and profile applicability; record uncertainty and conflicts." ] }, { "name": "Access custodian", "responsibilities": [ "Authorize audience views and redaction under the applicable policy." ] }, { "name": "Records custodian", "responsibilities": [ "Apply retention and disposition decisions with source-system responsibility." ] }, { "name": "Assisting agent", "responsibilities": [ "Prepare local drafts and checks; refuse unsupported authority or external legal acts." ] } ], "access": { "default_rule": "Deny restricted record access unless the applicable role, purpose and record-class rule authorize it. Publish only explicitly designated public forum metadata.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Court orders, confidentiality, privilege, sealed records and data-protection restrictions require a documented scope and authorized decision.", "Party status is not a universal grant of complete file access. Apply the actual case policy at its master; mediation communications have their own profile." ], "audit_requirements": [ "Record actor role, purpose, policy revision, requested scope and decision with minimal necessary data.", "Reference the authoritative audit service; do not replicate case payloads or imply perpetual retention of personal audit data." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read AGENTS.md and the adopting-Dimension authority/access policies.", "Read spec.yaml, publication holds and pinned composition bindings.", "Resolve forum and evidence masters before proposing a change." ] } }, "coverage": { "claim": "Source-grounded proposed forum entity structure using selected European, English civil-procedure and international commercial dispute-resolution evidence. Separate local no-tools self-audit completed. The draft is noncanonical, with independent-review, source/version, legal-profile and executable-conformance holds; no universal or operational legal completeness is claimed.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Forum identity is separate from operator, case and judgment identifiers." }, { "dimension": "lifecycle", "status": "covered", "notes": "Establishment and retirement assertions preserve evidence and successor distinctions." }, { "dimension": "relationships", "status": "covered", "notes": "Incoming registry reference and optional external master references retain ownership boundaries." }, { "dimension": "temporal", "status": "covered", "notes": "Effective and observed time, profile revisions and uncertainty are distinct." }, { "dimension": "provenance", "status": "covered", "notes": "Attribution and revision evidence are required; truth and authority are separately reviewed." }, { "dimension": "ownership", "status": "covered", "notes": "Forum metadata stewardship does not override case or document custody." }, { "dimension": "validation", "status": "gap", "notes": "Research schema is checked; nested instance schemas and operational legal validation are absent." }, { "dimension": "access", "status": "covered", "notes": "Audience-specific rules and exceptions govern local views and external case access." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Lawful disposition, holds and payload erasure qualify reference continuity." }, { "dimension": "interoperability", "status": "gap", "notes": "ECLI and PROV-O are conceptual mappings; executable bindings remain untested." }, { "dimension": "direct properties", "status": "covered", "notes": "Kind, mandate, scope, status and locations apply; physical dimensions belong to facilities, not the abstract forum." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Identifier, provenance and freshness questions separate recognition from legal status." }, { "dimension": "capabilities and actions", "status": "covered", "notes": "Offered powers differ from agent permissions; local operations have refusal conditions." }, { "dimension": "context and evidence", "status": "covered", "notes": "Regional profiles, mandate basis and external references constrain interpretation." } ], "known_omissions": [ "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." ], "conflicts": [], "regional_assumptions": [ "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." ], "adversarial_checks": [ "Reject the legacy proceeding root because a separate case model is registered.", "Reject mediation-as-adjudication, complete-party-access and universal one-dispute/one-forum assumptions.", "Reject operator identity, public web presence, ECLI or a record edit as evidence of legal power.", "Reject local route preview as filing, assignment or a case-specific competence ruling.", "Reject immutable history as a reason to retain personal data indefinitely." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "entity", "status": "accepted", "rationale": "The root is an identifiable forum with mandate and policy continuity. The legacy A19 proceeding-centered material is split conceptually against registered case, evidence, judgment and enforcement siblings, whose masters remain external. The incoming registry reference still resolves a competent forum. The registry standalone-mm value classifies the record plane, not the schema subject kind." }, "decisions": [ { "concept": "Forum entity boundary", "disposition": "accepted", "rationale": "Identity, mandate, offerings and stewardship persist independently of particular cases. A forum record is neither the case root nor the legal operator master." }, { "concept": "Legacy and supplement proceeding root", "disposition": "rejected for this successor", "rationale": "The separate Court / Arbitration Case, Evidence Item, Judgment and Enforcement Action models own the corresponding legacy subjects. The unreviewed supplement supplies no independent evidence." }, { "concept": "Incoming Registry Pattern relationship", "disposition": "accepted with boundary clarification", "rationale": "Contested entries can reference a competent forum. Forum-level procedure offerings stay here; linked case execution and registry administration do not become local lifecycles." }, { "concept": "Operator, tribunal and mediation profiles", "disposition": "qualified", "rationale": "Role and classification questions distinguish the administrator, deciding body and bounded ad hoc tribunal. A facilitative mediation profile cannot acquire binding adjudicative power by sharing the model." }, { "concept": "Competence and legal effect", "disposition": "separated", "rationale": "Mandate assertions require basis, scope, review state and exceptions. Neither public web presence, a directory route nor a local update decides competence for a case." }, { "concept": "Case cardinality and routing", "disposition": "legacy universality rejected", "rationale": "The admitted result avoids mandatory one-dispute/one-proceeding and universal one-forum assignments. Consolidation, review and uncertain referrals remain external case relationships." }, { "concept": "Identifier and physical-place mapping", "disposition": "qualified", "rationale": "ECLI identifies judgments; court-code mapping is an optional alignment. Forum identity, operator identity, premises and case-specific juridical place remain separate." }, { "concept": "Local operation authority", "disposition": "accepted as proposed only", "rationale": "All six operations have authority, evidence and revision preconditions with refusal outcomes. They prepare records, reports or previews without external legal acts." }, { "concept": "Access and retention", "disposition": "accepted with profile dependency", "rationale": "Audience rules reject blanket party or public access. Payload erasure, legal holds and minimal lawful tombstones qualify continuity without modifying linked legal records." }, { "concept": "Source coverage and currency", "disposition": "limited", "rationale": "Seven documents were available through browser retrieval; mediation and privacy support uses narrow indexed official excerpts. The arbitration note is an informational 1985 source. Direct HTTP was not attempted and no response status was measured." }, { "concept": "Nested schemas and mappings", "disposition": "deferred", "rationale": "Candidate fields and conceptual ECLI/PROV-O alignments are useful research outputs but provide no nested instance schemas, pinned model contracts, fixtures or executable legal conformance." }, { "concept": "Independent provider assurance", "disposition": "waived and held", "rationale": "Only Codex research is admitted. This distinct no-tools phase is a local self-audit of frozen evidence and cannot substitute for independent second-provider review." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped with zero attempts; the separate local Codex self-audit is not independent second-provider review.", "Live source and version verification remains incomplete. Direct HTTP checks were not attempted under the owner-reported sandbox block: zero measured HTTP 200 responses. Seven source documents were browser-readable; mediation and GDPR support is limited to indexed official excerpts. Current consolidation, amendments and source authenticity require coordinator and specialist checks.", "Jurisdiction-specific establishment, competence, appointment, procedure, access, privacy, retention and review rules require qualified profile validation. The informational 1985 arbitration note is not the amended 2006 law or a domestic enactment. Specialist forum profiles and legal applicability remain unverified.", "Nested instance schemas, role and classification vocabularies, pinned neighbor bindings, ECLI/PROV-O mappings and adversarial fixtures remain incomplete. Proposed local functions are unimplemented; no operational, security or legal-compliance certification is claimed.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "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." ] }, "statistics": { "sources": 9, "bundles": 6, "layers": 12, "findings": 12, "questions": 36, "artifacts": 12, "functions": 6 } }