# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T02:49:00Z", "synthesisSha256": "aab2d0baac1ea477671c0b6403be68b96fb3f63ff37002d8a1633b637f22308d", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-POL-001", "registryId": "vr.wm-pol-001", "name": "Legal Instrument / Norm", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Society, people and institutions", "industry": [ "Cross-industry" ], "domain": [ "SOC.POL.NRM" ], "tags": [ "legal", "instrument", "norm", "soc.pol.nrm" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-pol-001-legal-instrument-norm/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-pol-001", "model": { "registry_id": "vr.wm-pol-001", "model_id": "WM-POL-001", "name": "Legal Instrument / Norm", "entry_kind": "aggregate", "purpose": "Represent an authority-backed legal instrument and the norms expressed by its addressable source fragments, independent of storage and interface format.", "scope_statement": "Owns legal-work, expression, manifestation, source, provision and norm linkage; instrument class; authority and legal-basis references; structure and citations; authenticity and provenance; deontic assertions; lifecycle, temporal applicability, interpretation, access and projections. Organizations, lawmaking procedures, cases, enforcement events, affected parties, places and generic document storage remain external masters.", "in_scope": [ "Legal work, expression, manifestation, item, authoritative source, provision and norm identity", "Authority, class, structure, citation, normative meaning, lifecycle, time, applicability, conflict and provenance", "Authentication, consolidation, controlled disclosure, retention, interoperability and safe agent operations" ], "out_of_scope": [ "Issuing organization, legislative or administrative procedure and generic document repository masters", "Court or arbitration case, enforcement event, affected person, asset and place masters", "Automated legal advice, universally binding interpretation or substantive law common to every jurisdiction" ], "boundary_notes": [ { "neighbor": "Organization and Government", "distinction": "Authorities are external organizations referenced in a specific legal capacity; the legal instrument owns neither their identity nor governance.", "source_refs": [ "SRC-001", "SRC-006" ] }, { "neighbor": "Legislative or Rulemaking Process", "distinction": "The process produces adoption and publication evidence; the instrument aggregate preserves outputs and lifecycle assertions but not the workflow master.", "source_refs": [ "SRC-001" ] }, { "neighbor": "Court or Arbitration Case", "distinction": "A case may interpret, invalidate or apply an instrument, but its parties, procedure, evidence and decision lifecycle remain a separate model.", "source_refs": [ "SRC-003" ] }, { "neighbor": "Policy or Generic Rule", "distinction": "A policy or rule may lack legal-source authority; this aggregate requires explicit legal-source, jurisdiction and competent-authority bindings.", "source_refs": [ "SRC-003" ] }, { "neighbor": "Document and Record", "distinction": "Files and records are manifestations or evidence items; they do not replace authority-qualified legal-work identity or normative semantics.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Akoma Ntoso Version 1.0, Part 1: XML Vocabulary", "organization": "OASIS", "url": "https://docs.oasis-open.org/legaldocml/akn-core/v1.0/os/part1-vocabulary/akn-core-v1.0-os-part1-vocabulary.html", "version_or_date": "OASIS Standard, 29 August 2018", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:48:00Z", "relevance": "Defines source-oriented legal-document structure, metadata, references, identifiers, lifecycle events, modifications and analysis markup for legislation and other legal documents." }, { "id": "SRC-002", "title": "Akoma Ntoso Version 1.0, Part 2: Specifications", "organization": "OASIS", "url": "https://docs.oasis-open.org/legaldocml/akn-core/v1.0/os/part2-specs/akn-core-v1.0-os-part2-specs.html", "version_or_date": "OASIS Standard, 29 August 2018", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:48:00Z", "relevance": "Specifies naming, identification, references and conformance rules used to preserve addressable legal-document identity across expressions and manifestations." }, { "id": "SRC-003", "title": "LegalRuleML Core Specification Version 1.0", "organization": "OASIS", "url": "https://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/os/legalruleml-core-spec-v1.0-os.html", "version_or_date": "OASIS Standard, 30 August 2021", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:48:00Z", "relevance": "Defines formal features for legal norms and rules, including legal sources, authority, jurisdiction, temporal characteristics, deontic effects, defeasibility, exceptions and overrides." }, { "id": "SRC-004", "title": "What is the European Legislation Identifier", "organization": "Publications Office of the European Union", "url": "https://eur-lex.europa.eu/eli-register/what_is_eli.html", "version_or_date": "Official ELI register page, updated 27 January 2026", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:48:00Z", "relevance": "Defines ELI identification, metadata, publication and synchronization pillars and applies work, expression and manifestation distinctions to legislation." }, { "id": "SRC-005", "title": "ELI Subdivisions Specifications", "organization": "European Legislation Identifier Task Force", "url": "https://eur-lex.europa.eu/content/eli-register/ELI-subdivisions-specifications-v2.pdf", "version_or_date": "Version 2, official specification accessed 6 September 2026", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:48:00Z", "relevance": "Provides persistent identification and metadata guidance for addressable subdivisions such as articles, recitals and annexes." }, { "id": "SRC-006", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "W3C Recommendation, 30 April 2013", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:48:00Z", "relevance": "Provides interoperable provenance for entities, activities, agents, derivation, generation, attribution and qualified responsibility." }, { "id": "SRC-007", "title": "Time Ontology in OWL", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/owl-time/", "version_or_date": "W3C Candidate Recommendation Draft, 15 November 2022", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:48:00Z", "relevance": "Provides instants, intervals, temporal relations, duration and alternative temporal-reference systems needed to distinguish legal event and applicability times." }, { "id": "SRC-008", "title": "SKOS Simple Knowledge Organization System Reference", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/skos-reference/", "version_or_date": "W3C Recommendation, 18 August 2009", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:48:00Z", "relevance": "Supports governed concept schemes, labels, notation and mappings for instrument type, legal status, subject, jurisdiction and other controlled classifications." }, { "id": "SRC-009", "title": "Council conclusions inviting the introduction of the European Legislation Identifier", "organization": "Council of the European Union", "url": "https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A52012XG1026%2801%29", "version_or_date": "Official Journal C 325, 26 October 2012", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:48:00Z", "relevance": "Establishes the ELI policy basis for URI identification, metadata and machine-readable publication while preserving differences among national legal systems." }, { "id": "SRC-010", "title": "Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339", "version_or_date": "RFC 3339, July 2002", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:48:00Z", "relevance": "Defines machine timestamps with seconds and an explicit UTC offset for legal, publication, observation, knowledge and processing events." } ], "structure": { "bundles": [ { "id": "identity-authority-and-legal-class", "name": "Identity, authority and legal class", "description": "Identifies legal works and their authority-qualified classifications without treating a title, citation or file as timeless identity.", "rationale": "A legal work, language expression, manifestation, item, authoritative source and expressed norm can have different identities and masters.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-008", "SRC-009" ], "layers": [ { "id": "work-expression-manifestation-and-item", "name": "Work, expression, manifestation and item", "description": "Separates intellectual legal work from language realization, file embodiment and held copy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "findings": [ { "id": "authoritative-work-identifier-and-master-register", "name": "Authoritative work identifier and master register", "description": "Authority-qualified work identifier, namespace, register, resolver, alternate identifiers and collision state.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "questions": [ { "id": "authoritative-work-identifier-and-master-register-q01", "text": "What exact identities, classes, values, links and explicit unknowns define authoritative work identifier and master register?", "kind": "identity", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "authoritative-work-identifier-and-master-register-q02", "text": "Which competent authority, source fragment, publication, evidence and legal or knowledge time supports authoritative work identifier and master register?", "kind": "evidence", "answer_data": [ "authority", "source and fragment", "publication", "times", "evidence" ] }, { "id": "authoritative-work-identifier-and-master-register-q03", "text": "How may authoritative work identifier and master register be validated, contested, corrected, superseded, retained or disclosed without erasing cited history?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "retention", "access" ] } ], "data_elements": [ { "id": "authoritative-work-identifier-and-master-register-data", "name": "Authoritative work identifier and master register data", "description": "Structured authority-qualified data for authoritative work identifier and master register.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "artifacts": [ { "id": "authoritative-work-identifier-and-master-register-record", "name": "Authoritative work identifier and master register record", "description": "Versioned evidence-bearing record for authoritative work identifier and master register with source anchors, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical legal-instrument record", "authoritative source or evidence reference" ], "serial": true, "identity_strategy": "Legal-work identifier plus authoritative-work-identifier-and-master-register assertion or event identifier; title, citation, URL, date, text and hash never identify the work alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "inline_only_rationale": null }, { "id": "expression-manifestation-item-and-language-binding", "name": "Expression, manifestation, item and language binding", "description": "Expression language and version, manifestation format and rendition, item location, hash, status and links to the same work.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "questions": [ { "id": "expression-manifestation-item-and-language-binding-q01", "text": "What exact identities, classes, values, links and explicit unknowns define expression, manifestation, item and language binding?", "kind": "composition", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "expression-manifestation-item-and-language-binding-q02", "text": "Which competent authority, source fragment, publication, evidence and legal or knowledge time supports expression, manifestation, item and language binding?", "kind": "evidence", "answer_data": [ "authority", "source and fragment", "publication", "times", "evidence" ] }, { "id": "expression-manifestation-item-and-language-binding-q03", "text": "How may expression, manifestation, item and language binding be validated, contested, corrected, superseded, retained or disclosed without erasing cited history?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "retention", "access" ] } ], "data_elements": [ { "id": "expression-manifestation-item-and-language-binding-data", "name": "Expression, manifestation, item and language binding data", "description": "Structured authority-qualified data for expression, manifestation, item and language binding.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "artifacts": [ { "id": "expression-manifestation-item-and-language-binding-record", "name": "Expression, manifestation, item and language binding record", "description": "Versioned evidence-bearing record for expression, manifestation, item and language binding with source anchors, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical legal-instrument record", "authoritative source or evidence reference" ], "serial": true, "identity_strategy": "Legal-work identifier plus expression-manifestation-item-and-language-binding assertion or event identifier; title, citation, URL, date, text and hash never identify the work alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "instrument-class-authority-and-legal-basis", "name": "Instrument class, authority and legal basis", "description": "Classifies the instrument and attributes creation or promulgation to competent external authorities.", "source_refs": [ "SRC-001", "SRC-003", "SRC-008", "SRC-009" ], "findings": [ { "id": "instrument-type-jurisdiction-subject-and-classification", "name": "Instrument type, jurisdiction, subject and classification", "description": "Versioned type, legal-system profile, territorial scope, subject concepts, hierarchy and class-definition evidence.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008", "SRC-009" ], "questions": [ { "id": "instrument-type-jurisdiction-subject-and-classification-q01", "text": "What exact identities, classes, values, links and explicit unknowns define instrument type, jurisdiction, subject and classification?", "kind": "classification", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "instrument-type-jurisdiction-subject-and-classification-q02", "text": "Which competent authority, source fragment, publication, evidence and legal or knowledge time supports instrument type, jurisdiction, subject and classification?", "kind": "evidence", "answer_data": [ "authority", "source and fragment", "publication", "times", "evidence" ] }, { "id": "instrument-type-jurisdiction-subject-and-classification-q03", "text": "How may instrument type, jurisdiction, subject and classification be validated, contested, corrected, superseded, retained or disclosed without erasing cited history?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "retention", "access" ] } ], "data_elements": [ { "id": "instrument-type-jurisdiction-subject-and-classification-data", "name": "Instrument type, jurisdiction, subject and classification data", "description": "Structured authority-qualified data for instrument type, jurisdiction, subject and classification.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-008", "SRC-009" ] } ], "artifacts": [ { "id": "instrument-type-jurisdiction-subject-and-classification-record", "name": "Instrument type, jurisdiction, subject and classification record", "description": "Versioned evidence-bearing record for instrument type, jurisdiction, subject and classification with source anchors, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical legal-instrument record", "authoritative source or evidence reference" ], "serial": true, "identity_strategy": "Legal-work identifier plus instrument-type-jurisdiction-subject-and-classification assertion or event identifier; title, citation, URL, date, text and hash never identify the work alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "issuing-adopting-promulgating-and-publishing-authority", "name": "Issuing, adopting, promulgating and publishing authority", "description": "External organization and role references, competence basis, enabling instrument, delegation, signature and authority interval.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "questions": [ { "id": "issuing-adopting-promulgating-and-publishing-authority-q01", "text": "What exact identities, classes, values, links and explicit unknowns define issuing, adopting, promulgating and publishing authority?", "kind": "authority", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "issuing-adopting-promulgating-and-publishing-authority-q02", "text": "Which competent authority, source fragment, publication, evidence and legal or knowledge time supports issuing, adopting, promulgating and publishing authority?", "kind": "evidence", "answer_data": [ "authority", "source and fragment", "publication", "times", "evidence" ] }, { "id": "issuing-adopting-promulgating-and-publishing-authority-q03", "text": "How may issuing, adopting, promulgating and publishing authority be validated, contested, corrected, superseded, retained or disclosed without erasing cited history?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "retention", "access" ] } ], "data_elements": [ { "id": "issuing-adopting-promulgating-and-publishing-authority-data", "name": "Issuing, adopting, promulgating and publishing authority data", "description": "Structured authority-qualified data for issuing, adopting, promulgating and publishing authority.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "issuing-adopting-promulgating-and-publishing-authority-record", "name": "Issuing, adopting, promulgating and publishing authority record", "description": "Versioned evidence-bearing record for issuing, adopting, promulgating and publishing authority with source anchors, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical legal-instrument record", "authoritative source or evidence reference" ], "serial": true, "identity_strategy": "Legal-work identifier plus issuing-adopting-promulgating-and-publishing-authority assertion or event identifier; title, citation, URL, date, text and hash never identify the work alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "structure-addressability-and-source-evidence", "name": "Structure, addressability and source evidence", "description": "Makes provisions and source fragments stably addressable and proves which manifestation is authoritative for a stated purpose.", "rationale": "Rendered numbering and URLs can change; citation and authenticity need version, source, authority and fragment identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006" ], "layers": [ { "id": "document-structure-and-provision-addresses", "name": "Document structure and provision addresses", "description": "Represents hierarchy, ordering and stable addresses for provisions and supporting components.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ], "findings": [ { "id": "preamble-recital-provision-schedule-and-annex-structure", "name": "Preamble, recital, provision, schedule and annex structure", "description": "Ordered component tree with stable component identifiers, displayed labels, headings, numbering history and containment.", "source_refs": [ "SRC-001", "SRC-005" ], "questions": [ { "id": "preamble-recital-provision-schedule-and-annex-structure-q01", "text": "What exact identities, classes, values, links and explicit unknowns define preamble, recital, provision, schedule and annex structure?", "kind": "composition", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "preamble-recital-provision-schedule-and-annex-structure-q02", "text": "Which competent authority, source fragment, publication, evidence and legal or knowledge time supports preamble, recital, provision, schedule and annex structure?", "kind": "evidence", "answer_data": [ "authority", "source and fragment", "publication", "times", "evidence" ] }, { "id": "preamble-recital-provision-schedule-and-annex-structure-q03", "text": "How may preamble, recital, provision, schedule and annex structure be validated, contested, corrected, superseded, retained or disclosed without erasing cited history?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "retention", "access" ] } ], "data_elements": [ { "id": "preamble-recital-provision-schedule-and-annex-structure-data", "name": "Preamble, recital, provision, schedule and annex structure data", "description": "Structured authority-qualified data for preamble, recital, provision, schedule and annex structure.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005" ] } ], "artifacts": [ { "id": "preamble-recital-provision-schedule-and-annex-structure-record", "name": "Preamble, recital, provision, schedule and annex structure record", "description": "Versioned evidence-bearing record for preamble, recital, provision, schedule and annex structure with source anchors, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical legal-instrument record", "authoritative source or evidence reference" ], "serial": true, "identity_strategy": "Legal-work identifier plus preamble-recital-provision-schedule-and-annex-structure assertion or event identifier; title, citation, URL, date, text and hash never identify the work alone.", "source_refs": [ "SRC-001", "SRC-005" ] } ], "inline_only_rationale": null }, { "id": "citation-cross-reference-and-version-resolution", "name": "Citation, cross-reference and version resolution", "description": "Source and target work or provision, citation text, static or dynamic semantics, language, valid time and resolution outcome.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ], "questions": [ { "id": "citation-cross-reference-and-version-resolution-q01", "text": "What exact identities, classes, values, links and explicit unknowns define citation, cross-reference and version resolution?", "kind": "relationship", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "citation-cross-reference-and-version-resolution-q02", "text": "Which competent authority, source fragment, publication, evidence and legal or knowledge time supports citation, cross-reference and version resolution?", "kind": "evidence", "answer_data": [ "authority", "source and fragment", "publication", "times", "evidence" ] }, { "id": "citation-cross-reference-and-version-resolution-q03", "text": "How may citation, cross-reference and version resolution be validated, contested, corrected, superseded, retained or disclosed without erasing cited history?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "retention", "access" ] } ], "data_elements": [ { "id": "citation-cross-reference-and-version-resolution-data", "name": "Citation, cross-reference and version resolution data", "description": "Structured authority-qualified data for citation, cross-reference and version resolution.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] } ], "artifacts": [ { "id": "citation-cross-reference-and-version-resolution-record", "name": "Citation, cross-reference and version resolution record", "description": "Versioned evidence-bearing record for citation, cross-reference and version resolution with source anchors, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical legal-instrument record", "authoritative source or evidence reference" ], "serial": true, "identity_strategy": "Legal-work identifier plus citation-cross-reference-and-version-resolution assertion or event identifier; title, citation, URL, date, text and hash never identify the work alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "authenticity-provenance-and-integrity", "name": "Authenticity, provenance and integrity", "description": "Attributes source publication, derivation and verification without equating availability with legal authority.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-009" ], "findings": [ { "id": "authoritative-source-publication-authentication-and-copy-status", "name": "Authoritative source, publication, authentication and copy status", "description": "Official publisher, gazette or register, publication act, signature or seal evidence, copy class, verification method and result.", "source_refs": [ "SRC-001", "SRC-004", "SRC-009" ], "questions": [ { "id": "authoritative-source-publication-authentication-and-copy-status-q01", "text": "What exact identities, classes, values, links and explicit unknowns define authoritative source, publication, authentication and copy status?", "kind": "evidence", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "authoritative-source-publication-authentication-and-copy-status-q02", "text": "Which competent authority, source fragment, publication, evidence and legal or knowledge time supports authoritative source, publication, authentication and copy status?", "kind": "evidence", "answer_data": [ "authority", "source and fragment", "publication", "times", "evidence" ] }, { "id": "authoritative-source-publication-authentication-and-copy-status-q03", "text": "How may authoritative source, publication, authentication and copy status be validated, contested, corrected, superseded, retained or disclosed without erasing cited history?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "retention", "access" ] } ], "data_elements": [ { "id": "authoritative-source-publication-authentication-and-copy-status-data", "name": "Authoritative source, publication, authentication and copy status data", "description": "Structured authority-qualified data for authoritative source, publication, authentication and copy status.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-009" ] } ], "artifacts": [ { "id": "authoritative-source-publication-authentication-and-copy-status-record", "name": "Authoritative source, publication, authentication and copy status record", "description": "Versioned evidence-bearing record for authoritative source, publication, authentication and copy status with source anchors, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical legal-instrument record", "authoritative source or evidence reference" ], "serial": true, "identity_strategy": "Legal-work identifier plus authoritative-source-publication-authentication-and-copy-status assertion or event identifier; title, citation, URL, date, text and hash never identify the work alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "provenance-derivation-custody-digest-and-correction-history", "name": "Provenance, derivation, custody, digest and correction history", "description": "Generated, derived and attributed relations, responsible agents, custody changes, digests, fixes and knowledge time.", "source_refs": [ "SRC-006", "SRC-010" ], "questions": [ { "id": "provenance-derivation-custody-digest-and-correction-history-q01", "text": "What exact identities, classes, values, links and explicit unknowns define provenance, derivation, custody, digest and correction history?", "kind": "provenance", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "provenance-derivation-custody-digest-and-correction-history-q02", "text": "Which competent authority, source fragment, publication, evidence and legal or knowledge time supports provenance, derivation, custody, digest and correction history?", "kind": "evidence", "answer_data": [ "authority", "source and fragment", "publication", "times", "evidence" ] }, { "id": "provenance-derivation-custody-digest-and-correction-history-q03", "text": "How may provenance, derivation, custody, digest and correction history be validated, contested, corrected, superseded, retained or disclosed without erasing cited history?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "retention", "access" ] } ], "data_elements": [ { "id": "provenance-derivation-custody-digest-and-correction-history-data", "name": "Provenance, derivation, custody, digest and correction history data", "description": "Structured authority-qualified data for provenance, derivation, custody, digest and correction history.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-006", "SRC-010" ] } ], "artifacts": [ { "id": "provenance-derivation-custody-digest-and-correction-history-record", "name": "Provenance, derivation, custody, digest and correction history record", "description": "Versioned evidence-bearing record for provenance, derivation, custody, digest and correction history with source anchors, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical legal-instrument record", "authoritative source or evidence reference" ], "serial": true, "identity_strategy": "Legal-work identifier plus provenance-derivation-custody-digest-and-correction-history assertion or event identifier; title, citation, URL, date, text and hash never identify the work alone.", "source_refs": [ "SRC-006", "SRC-010" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "normative-meaning-and-rule-linkage", "name": "Normative meaning and rule linkage", "description": "Links formal or structured normative assertions to exact legal-source fragments while preserving uncertainty and interpretive authority.", "rationale": "Source text, a legal norm and an executable rule are related but not interchangeable and may differ by interpretation or formalization.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005", "SRC-006", "SRC-008" ], "layers": [ { "id": "constitutive-and-prescriptive-statements", "name": "Constitutive and prescriptive statements", "description": "Represents statement identity, source anchor, semantics and formalization status.", "source_refs": [ "SRC-003", "SRC-005" ], "findings": [ { "id": "norm-statement-source-anchor-and-formalization", "name": "Norm statement, source anchor and formalization", "description": "Norm identity, exact source fragments, natural-language reading, formal expression, author, method, confidence and validation.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ], "questions": [ { "id": "norm-statement-source-anchor-and-formalization-q01", "text": "What exact identities, classes, values, links and explicit unknowns define norm statement, source anchor and formalization?", "kind": "definition", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "norm-statement-source-anchor-and-formalization-q02", "text": "Which competent authority, source fragment, publication, evidence and legal or knowledge time supports norm statement, source anchor and formalization?", "kind": "evidence", "answer_data": [ "authority", "source and fragment", "publication", "times", "evidence" ] }, { "id": "norm-statement-source-anchor-and-formalization-q03", "text": "How may norm statement, source anchor and formalization be validated, contested, corrected, superseded, retained or disclosed without erasing cited history?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "retention", "access" ] } ], "data_elements": [ { "id": "norm-statement-source-anchor-and-formalization-data", "name": "Norm statement, source anchor and formalization data", "description": "Structured authority-qualified data for norm statement, source anchor and formalization.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "norm-statement-source-anchor-and-formalization-record", "name": "Norm statement, source anchor and formalization record", "description": "Versioned evidence-bearing record for norm statement, source anchor and formalization with source anchors, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical legal-instrument record", "authoritative source or evidence reference" ], "serial": true, "identity_strategy": "Legal-work identifier plus norm-statement-source-anchor-and-formalization assertion or event identifier; title, citation, URL, date, text and hash never identify the work alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null }, { "id": "constitutive-definition-status-power-and-institutional-fact", "name": "Constitutive definition, status, power and institutional fact", "description": "Terms, qualifications, powers, statuses and institutional consequences established under a named legal profile.", "source_refs": [ "SRC-003" ], "questions": [ { "id": "constitutive-definition-status-power-and-institutional-fact-q01", "text": "What exact identities, classes, values, links and explicit unknowns define constitutive definition, status, power and institutional fact?", "kind": "definition", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "constitutive-definition-status-power-and-institutional-fact-q02", "text": "Which competent authority, source fragment, publication, evidence and legal or knowledge time supports constitutive definition, status, power and institutional fact?", "kind": "evidence", "answer_data": [ "authority", "source and fragment", "publication", "times", "evidence" ] }, { "id": "constitutive-definition-status-power-and-institutional-fact-q03", "text": "How may constitutive definition, status, power and institutional fact be validated, contested, corrected, superseded, retained or disclosed without erasing cited history?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "retention", "access" ] } ], "data_elements": [ { "id": "constitutive-definition-status-power-and-institutional-fact-data", "name": "Constitutive definition, status, power and institutional fact data", "description": "Structured authority-qualified data for constitutive definition, status, power and institutional fact.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003" ] } ], "artifacts": [ { "id": "constitutive-definition-status-power-and-institutional-fact-record", "name": "Constitutive definition, status, power and institutional fact record", "description": "Versioned evidence-bearing record for constitutive definition, status, power and institutional fact with source anchors, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical legal-instrument record", "authoritative source or evidence reference" ], "serial": true, "identity_strategy": "Legal-work identifier plus constitutive-definition-status-power-and-institutional-fact assertion or event identifier; title, citation, URL, date, text and hash never identify the work alone.", "source_refs": [ "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "deontic-effects-conditions-and-exceptions", "name": "Deontic effects, conditions and exceptions", "description": "Captures duty, liberty, prohibition and related consequences with bearer, action and triggering context.", "source_refs": [ "SRC-003" ], "findings": [ { "id": "obligation-permission-prohibition-right-and-power", "name": "Obligation, permission, prohibition, right and power", "description": "Modality, bearer, counterparty, action, object, deadline, jurisdiction, source anchor and asserted legal effect.", "source_refs": [ "SRC-003" ], "questions": [ { "id": "obligation-permission-prohibition-right-and-power-q01", "text": "What exact identities, classes, values, links and explicit unknowns define obligation, permission, prohibition, right and power?", "kind": "requirement", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "obligation-permission-prohibition-right-and-power-q02", "text": "Which competent authority, source fragment, publication, evidence and legal or knowledge time supports obligation, permission, prohibition, right and power?", "kind": "evidence", "answer_data": [ "authority", "source and fragment", "publication", "times", "evidence" ] }, { "id": "obligation-permission-prohibition-right-and-power-q03", "text": "How may obligation, permission, prohibition, right and power be validated, contested, corrected, superseded, retained or disclosed without erasing cited history?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "retention", "access" ] } ], "data_elements": [ { "id": "obligation-permission-prohibition-right-and-power-data", "name": "Obligation, permission, prohibition, right and power data", "description": "Structured authority-qualified data for obligation, permission, prohibition, right and power.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003" ] } ], "artifacts": [ { "id": "obligation-permission-prohibition-right-and-power-record", "name": "Obligation, permission, prohibition, right and power record", "description": "Versioned evidence-bearing record for obligation, permission, prohibition, right and power with source anchors, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical legal-instrument record", "authoritative source or evidence reference" ], "serial": true, "identity_strategy": "Legal-work identifier plus obligation-permission-prohibition-right-and-power assertion or event identifier; title, citation, URL, date, text and hash never identify the work alone.", "source_refs": [ "SRC-003" ] } ], "inline_only_rationale": null }, { "id": "condition-exception-violation-sanction-reparation-and-remedy", "name": "Condition, exception, violation, sanction, reparation and remedy", "description": "Activation and termination conditions, exception scope, breach criteria, consequence, cure, remedy and competent authority.", "source_refs": [ "SRC-003" ], "questions": [ { "id": "condition-exception-violation-sanction-reparation-and-remedy-q01", "text": "What exact identities, classes, values, links and explicit unknowns define condition, exception, violation, sanction, reparation and remedy?", "kind": "exception", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "condition-exception-violation-sanction-reparation-and-remedy-q02", "text": "Which competent authority, source fragment, publication, evidence and legal or knowledge time supports condition, exception, violation, sanction, reparation and remedy?", "kind": "evidence", "answer_data": [ "authority", "source and fragment", "publication", "times", "evidence" ] }, { "id": "condition-exception-violation-sanction-reparation-and-remedy-q03", "text": "How may condition, exception, violation, sanction, reparation and remedy be validated, contested, corrected, superseded, retained or disclosed without erasing cited history?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "retention", "access" ] } ], "data_elements": [ { "id": "condition-exception-violation-sanction-reparation-and-remedy-data", "name": "Condition, exception, violation, sanction, reparation and remedy data", "description": "Structured authority-qualified data for condition, exception, violation, sanction, reparation and remedy.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003" ] } ], "artifacts": [ { "id": "condition-exception-violation-sanction-reparation-and-remedy-record", "name": "Condition, exception, violation, sanction, reparation and remedy record", "description": "Versioned evidence-bearing record for condition, exception, violation, sanction, reparation and remedy with source anchors, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical legal-instrument record", "authoritative source or evidence reference" ], "serial": true, "identity_strategy": "Legal-work identifier plus condition-exception-violation-sanction-reparation-and-remedy assertion or event identifier; title, citation, URL, date, text and hash never identify the work alone.", "source_refs": [ "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "lifecycle-versioning-and-consolidation", "name": "Lifecycle, versioning and consolidation", "description": "Preserves authority-qualified status assertions and every amendment, correction and consolidated view.", "rationale": "Draft, adoption, publication, validity, force and applicability do not form one universal sequence, and consolidated text is not the original act.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006", "SRC-007", "SRC-010" ], "layers": [ { "id": "legal-state-and-event-history", "name": "Legal state and event history", "description": "Separates state assertions from the events and evidence said to establish them.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-007", "SRC-010" ], "findings": [ { "id": "draft-adopted-promulgated-published-valid-in-force-suspended-and-repealed-state", "name": "Draft, adopted, promulgated, published, valid, in-force, suspended and repealed state", "description": "Profile-qualified state, deciding authority, scope, source, effective interval, confidence, contest and observation status.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "draft-adopted-promulgated-published-valid-in-force-suspended-and-repealed-state-q01", "text": "What exact identities, classes, values, links and explicit unknowns define draft, adopted, promulgated, published, valid, in-force, suspended and repealed state?", "kind": "state", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "draft-adopted-promulgated-published-valid-in-force-suspended-and-repealed-state-q02", "text": "Which competent authority, source fragment, publication, evidence and legal or knowledge time supports draft, adopted, promulgated, published, valid, in-force, suspended and repealed state?", "kind": "evidence", "answer_data": [ "authority", "source and fragment", "publication", "times", "evidence" ] }, { "id": "draft-adopted-promulgated-published-valid-in-force-suspended-and-repealed-state-q03", "text": "How may draft, adopted, promulgated, published, valid, in-force, suspended and repealed state be validated, contested, corrected, superseded, retained or disclosed without erasing cited history?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "retention", "access" ] } ], "data_elements": [ { "id": "draft-adopted-promulgated-published-valid-in-force-suspended-and-repealed-state-data", "name": "Draft, adopted, promulgated, published, valid, in-force, suspended and repealed state data", "description": "Structured authority-qualified data for draft, adopted, promulgated, published, valid, in-force, suspended and repealed state.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "draft-adopted-promulgated-published-valid-in-force-suspended-and-repealed-state-record", "name": "Draft, adopted, promulgated, published, valid, in-force, suspended and repealed state record", "description": "Versioned evidence-bearing record for draft, adopted, promulgated, published, valid, in-force, suspended and repealed state with source anchors, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical legal-instrument record", "authoritative source or evidence reference" ], "serial": true, "identity_strategy": "Legal-work identifier plus draft-adopted-promulgated-published-valid-in-force-suspended-and-repealed-state assertion or event identifier; title, citation, URL, date, text and hash never identify the work alone.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null }, { "id": "adoption-signature-publication-commencement-suspension-repeal-and-expiry-event", "name": "Adoption, signature, publication, commencement, suspension, repeal and expiry event", "description": "Event kind, authority, instrument, affected work or provisions, decision and effect times, evidence and resulting state assertion.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-007", "SRC-010" ], "questions": [ { "id": "adoption-signature-publication-commencement-suspension-repeal-and-expiry-event-q01", "text": "What exact identities, classes, values, links and explicit unknowns define adoption, signature, publication, commencement, suspension, repeal and expiry event?", "kind": "lifecycle", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "adoption-signature-publication-commencement-suspension-repeal-and-expiry-event-q02", "text": "Which competent authority, source fragment, publication, evidence and legal or knowledge time supports adoption, signature, publication, commencement, suspension, repeal and expiry event?", "kind": "evidence", "answer_data": [ "authority", "source and fragment", "publication", "times", "evidence" ] }, { "id": "adoption-signature-publication-commencement-suspension-repeal-and-expiry-event-q03", "text": "How may adoption, signature, publication, commencement, suspension, repeal and expiry event be validated, contested, corrected, superseded, retained or disclosed without erasing cited history?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "retention", "access" ] } ], "data_elements": [ { "id": "adoption-signature-publication-commencement-suspension-repeal-and-expiry-event-data", "name": "Adoption, signature, publication, commencement, suspension, repeal and expiry event data", "description": "Structured authority-qualified data for adoption, signature, publication, commencement, suspension, repeal and expiry event.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-007", "SRC-010" ] } ], "artifacts": [ { "id": "adoption-signature-publication-commencement-suspension-repeal-and-expiry-event-record", "name": "Adoption, signature, publication, commencement, suspension, repeal and expiry event record", "description": "Versioned evidence-bearing record for adoption, signature, publication, commencement, suspension, repeal and expiry event with source anchors, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical legal-instrument record", "authoritative source or evidence reference" ], "serial": true, "identity_strategy": "Legal-work identifier plus adoption-signature-publication-commencement-suspension-repeal-and-expiry-event assertion or event identifier; title, citation, URL, date, text and hash never identify the work alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-007", "SRC-010" ] } ], "inline_only_rationale": null } ] }, { "id": "amendment-correction-and-consolidation-lineage", "name": "Amendment, correction and consolidation lineage", "description": "Connects original acts, modifying acts, corrected expressions and derived consolidated views.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006" ], "findings": [ { "id": "amendment-repeal-substitution-renumbering-and-correction-operation", "name": "Amendment, repeal, substitution, renumbering and correction operation", "description": "Modifying instrument, source and target provisions, operation, authority, legal effect, text delta, unresolved target and provenance.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "amendment-repeal-substitution-renumbering-and-correction-operation-q01", "text": "What exact identities, classes, values, links and explicit unknowns define amendment, repeal, substitution, renumbering and correction operation?", "kind": "process", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "amendment-repeal-substitution-renumbering-and-correction-operation-q02", "text": "Which competent authority, source fragment, publication, evidence and legal or knowledge time supports amendment, repeal, substitution, renumbering and correction operation?", "kind": "evidence", "answer_data": [ "authority", "source and fragment", "publication", "times", "evidence" ] }, { "id": "amendment-repeal-substitution-renumbering-and-correction-operation-q03", "text": "How may amendment, repeal, substitution, renumbering and correction operation be validated, contested, corrected, superseded, retained or disclosed without erasing cited history?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "retention", "access" ] } ], "data_elements": [ { "id": "amendment-repeal-substitution-renumbering-and-correction-operation-data", "name": "Amendment, repeal, substitution, renumbering and correction operation data", "description": "Structured authority-qualified data for amendment, repeal, substitution, renumbering and correction operation.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "amendment-repeal-substitution-renumbering-and-correction-operation-record", "name": "Amendment, repeal, substitution, renumbering and correction operation record", "description": "Versioned evidence-bearing record for amendment, repeal, substitution, renumbering and correction operation with source anchors, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical legal-instrument record", "authoritative source or evidence reference" ], "serial": true, "identity_strategy": "Legal-work identifier plus amendment-repeal-substitution-renumbering-and-correction-operation assertion or event identifier; title, citation, URL, date, text and hash never identify the work alone.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null }, { "id": "original-version-consolidated-view-derivation-and-applicability-snapshot", "name": "Original version, consolidated view, derivation and applicability snapshot", "description": "Version graph, consolidation date, applied modifications, unresolved conflicts, publisher, non-authoritative warning and source digests.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "questions": [ { "id": "original-version-consolidated-view-derivation-and-applicability-snapshot-q01", "text": "What exact identities, classes, values, links and explicit unknowns define original version, consolidated view, derivation and applicability snapshot?", "kind": "provenance", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "original-version-consolidated-view-derivation-and-applicability-snapshot-q02", "text": "Which competent authority, source fragment, publication, evidence and legal or knowledge time supports original version, consolidated view, derivation and applicability snapshot?", "kind": "evidence", "answer_data": [ "authority", "source and fragment", "publication", "times", "evidence" ] }, { "id": "original-version-consolidated-view-derivation-and-applicability-snapshot-q03", "text": "How may original version, consolidated view, derivation and applicability snapshot be validated, contested, corrected, superseded, retained or disclosed without erasing cited history?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "retention", "access" ] } ], "data_elements": [ { "id": "original-version-consolidated-view-derivation-and-applicability-snapshot-data", "name": "Original version, consolidated view, derivation and applicability snapshot data", "description": "Structured authority-qualified data for original version, consolidated view, derivation and applicability snapshot.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "original-version-consolidated-view-derivation-and-applicability-snapshot-record", "name": "Original version, consolidated view, derivation and applicability snapshot record", "description": "Versioned evidence-bearing record for original version, consolidated view, derivation and applicability snapshot with source anchors, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical legal-instrument record", "authoritative source or evidence reference" ], "serial": true, "identity_strategy": "Legal-work identifier plus original-version-consolidated-view-derivation-and-applicability-snapshot assertion or event identifier; title, citation, URL, date, text and hash never identify the work alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "time-applicability-jurisdiction-and-conflict", "name": "Time, applicability, jurisdiction and conflict", "description": "Records the axes and scopes on which an instrument or norm may apply and preserves competing interpretive assertions.", "rationale": "Applicability is a source-qualified conclusion that can vary by provision, party, territory, facts, time and competent interpreter.", "source_refs": [ "SRC-003", "SRC-007", "SRC-008", "SRC-010" ], "layers": [ { "id": "temporal-and-jurisdictional-applicability", "name": "Temporal and jurisdictional applicability", "description": "Represents separate time axes and legal reach without silently deciding a case.", "source_refs": [ "SRC-003", "SRC-007", "SRC-010" ], "findings": [ { "id": "enactment-publication-commencement-efficacy-applicability-and-knowledge-time", "name": "Enactment, publication, commencement, efficacy, applicability and knowledge time", "description": "Distinct instants or intervals, provision scope, timezone, precision, retroactivity, temporal exceptions, source and assertion authority.", "source_refs": [ "SRC-003", "SRC-007", "SRC-010" ], "questions": [ { "id": "enactment-publication-commencement-efficacy-applicability-and-knowledge-time-q01", "text": "What exact identities, classes, values, links and explicit unknowns define enactment, publication, commencement, efficacy, applicability and knowledge time?", "kind": "temporal", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "enactment-publication-commencement-efficacy-applicability-and-knowledge-time-q02", "text": "Which competent authority, source fragment, publication, evidence and legal or knowledge time supports enactment, publication, commencement, efficacy, applicability and knowledge time?", "kind": "evidence", "answer_data": [ "authority", "source and fragment", "publication", "times", "evidence" ] }, { "id": "enactment-publication-commencement-efficacy-applicability-and-knowledge-time-q03", "text": "How may enactment, publication, commencement, efficacy, applicability and knowledge time be validated, contested, corrected, superseded, retained or disclosed without erasing cited history?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "retention", "access" ] } ], "data_elements": [ { "id": "enactment-publication-commencement-efficacy-applicability-and-knowledge-time-data", "name": "Enactment, publication, commencement, efficacy, applicability and knowledge time data", "description": "Structured authority-qualified data for enactment, publication, commencement, efficacy, applicability and knowledge time.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-007", "SRC-010" ] } ], "artifacts": [ { "id": "enactment-publication-commencement-efficacy-applicability-and-knowledge-time-record", "name": "Enactment, publication, commencement, efficacy, applicability and knowledge time record", "description": "Versioned evidence-bearing record for enactment, publication, commencement, efficacy, applicability and knowledge time with source anchors, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical legal-instrument record", "authoritative source or evidence reference" ], "serial": true, "identity_strategy": "Legal-work identifier plus enactment-publication-commencement-efficacy-applicability-and-knowledge-time assertion or event identifier; title, citation, URL, date, text and hash never identify the work alone.", "source_refs": [ "SRC-003", "SRC-007", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "territorial-personal-material-institutional-and-procedural-scope", "name": "Territorial, personal, material, institutional and procedural scope", "description": "Jurisdiction references, covered persons and subjects, institutional reach, procedure, connecting factor, exclusions and conflicts rules.", "source_refs": [ "SRC-003", "SRC-008" ], "questions": [ { "id": "territorial-personal-material-institutional-and-procedural-scope-q01", "text": "What exact identities, classes, values, links and explicit unknowns define territorial, personal, material, institutional and procedural scope?", "kind": "relationship", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "territorial-personal-material-institutional-and-procedural-scope-q02", "text": "Which competent authority, source fragment, publication, evidence and legal or knowledge time supports territorial, personal, material, institutional and procedural scope?", "kind": "evidence", "answer_data": [ "authority", "source and fragment", "publication", "times", "evidence" ] }, { "id": "territorial-personal-material-institutional-and-procedural-scope-q03", "text": "How may territorial, personal, material, institutional and procedural scope be validated, contested, corrected, superseded, retained or disclosed without erasing cited history?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "retention", "access" ] } ], "data_elements": [ { "id": "territorial-personal-material-institutional-and-procedural-scope-data", "name": "Territorial, personal, material, institutional and procedural scope data", "description": "Structured authority-qualified data for territorial, personal, material, institutional and procedural scope.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "territorial-personal-material-institutional-and-procedural-scope-record", "name": "Territorial, personal, material, institutional and procedural scope record", "description": "Versioned evidence-bearing record for territorial, personal, material, institutional and procedural scope with source anchors, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical legal-instrument record", "authoritative source or evidence reference" ], "serial": true, "identity_strategy": "Legal-work identifier plus territorial-personal-material-institutional-and-procedural-scope assertion or event identifier; title, citation, URL, date, text and hash never identify the work alone.", "source_refs": [ "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "priority-override-interpretation-and-contest", "name": "Priority, override, interpretation and contest", "description": "Keeps formal conflict relations and attributed interpretations separate from final adjudication.", "source_refs": [ "SRC-003", "SRC-006" ], "findings": [ { "id": "priority-override-derogation-exception-and-conflict-assertion", "name": "Priority, override, derogation, exception and conflict assertion", "description": "Conflicting norms, relation type, scope, authority, basis, time, condition, unresolved state and confidence.", "source_refs": [ "SRC-003" ], "questions": [ { "id": "priority-override-derogation-exception-and-conflict-assertion-q01", "text": "What exact identities, classes, values, links and explicit unknowns define priority, override, derogation, exception and conflict assertion?", "kind": "decision", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "priority-override-derogation-exception-and-conflict-assertion-q02", "text": "Which competent authority, source fragment, publication, evidence and legal or knowledge time supports priority, override, derogation, exception and conflict assertion?", "kind": "evidence", "answer_data": [ "authority", "source and fragment", "publication", "times", "evidence" ] }, { "id": "priority-override-derogation-exception-and-conflict-assertion-q03", "text": "How may priority, override, derogation, exception and conflict assertion be validated, contested, corrected, superseded, retained or disclosed without erasing cited history?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "retention", "access" ] } ], "data_elements": [ { "id": "priority-override-derogation-exception-and-conflict-assertion-data", "name": "Priority, override, derogation, exception and conflict assertion data", "description": "Structured authority-qualified data for priority, override, derogation, exception and conflict assertion.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003" ] } ], "artifacts": [ { "id": "priority-override-derogation-exception-and-conflict-assertion-record", "name": "Priority, override, derogation, exception and conflict assertion record", "description": "Versioned evidence-bearing record for priority, override, derogation, exception and conflict assertion with source anchors, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical legal-instrument record", "authoritative source or evidence reference" ], "serial": true, "identity_strategy": "Legal-work identifier plus priority-override-derogation-exception-and-conflict-assertion assertion or event identifier; title, citation, URL, date, text and hash never identify the work alone.", "source_refs": [ "SRC-003" ] } ], "inline_only_rationale": null }, { "id": "interpretive-decision-guidance-commentary-and-contest", "name": "Interpretive decision, guidance, commentary and contest", "description": "Interpreter, authority class, cited sources, affected provisions, holding or guidance, jurisdiction, precedential scope, dissent and later treatment.", "source_refs": [ "SRC-003", "SRC-006" ], "questions": [ { "id": "interpretive-decision-guidance-commentary-and-contest-q01", "text": "What exact identities, classes, values, links and explicit unknowns define interpretive decision, guidance, commentary and contest?", "kind": "evidence", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "interpretive-decision-guidance-commentary-and-contest-q02", "text": "Which competent authority, source fragment, publication, evidence and legal or knowledge time supports interpretive decision, guidance, commentary and contest?", "kind": "evidence", "answer_data": [ "authority", "source and fragment", "publication", "times", "evidence" ] }, { "id": "interpretive-decision-guidance-commentary-and-contest-q03", "text": "How may interpretive decision, guidance, commentary and contest be validated, contested, corrected, superseded, retained or disclosed without erasing cited history?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "retention", "access" ] } ], "data_elements": [ { "id": "interpretive-decision-guidance-commentary-and-contest-data", "name": "Interpretive decision, guidance, commentary and contest data", "description": "Structured authority-qualified data for interpretive decision, guidance, commentary and contest.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "interpretive-decision-guidance-commentary-and-contest-record", "name": "Interpretive decision, guidance, commentary and contest record", "description": "Versioned evidence-bearing record for interpretive decision, guidance, commentary and contest with source anchors, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical legal-instrument record", "authoritative source or evidence reference" ], "serial": true, "identity_strategy": "Legal-work identifier plus interpretive-decision-guidance-commentary-and-contest assertion or event identifier; title, citation, URL, date, text and hash never identify the work alone.", "source_refs": [ "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "interoperability-access-and-agent-governance", "name": "Interoperability, access and agent governance", "description": "Provides loss-aware projections, controlled disclosure, retention and safe automated operations.", "rationale": "A convenient XML, RDF, JSON or rule projection can lose authority, version, source anchoring, applicability and uncertainty unless its limits stay explicit.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-008", "SRC-010" ], "layers": [ { "id": "classification-projection-and-access-views", "name": "Classification, projection and access views", "description": "Maps the aggregate to public legal-information formats and purpose-bound views.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-008" ], "findings": [ { "id": "akoma-ntoso-legalruleml-eli-prov-time-and-skos-projection", "name": "Akoma Ntoso, LegalRuleML, ELI, PROV, Time and SKOS projection", "description": "Source and target versions, identity mapping, transformed fields, source anchors, semantics, omissions and round-trip limits.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008" ], "questions": [ { "id": "akoma-ntoso-legalruleml-eli-prov-time-and-skos-projection-q01", "text": "What exact identities, classes, values, links and explicit unknowns define akoma ntoso, legalruleml, eli, prov, time and skos projection?", "kind": "interoperability", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "akoma-ntoso-legalruleml-eli-prov-time-and-skos-projection-q02", "text": "Which competent authority, source fragment, publication, evidence and legal or knowledge time supports akoma ntoso, legalruleml, eli, prov, time and skos projection?", "kind": "evidence", "answer_data": [ "authority", "source and fragment", "publication", "times", "evidence" ] }, { "id": "akoma-ntoso-legalruleml-eli-prov-time-and-skos-projection-q03", "text": "How may akoma ntoso, legalruleml, eli, prov, time and skos projection be validated, contested, corrected, superseded, retained or disclosed without erasing cited history?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "retention", "access" ] } ], "data_elements": [ { "id": "akoma-ntoso-legalruleml-eli-prov-time-and-skos-projection-data", "name": "Akoma Ntoso, LegalRuleML, ELI, PROV, Time and SKOS projection data", "description": "Structured authority-qualified data for akoma ntoso, legalruleml, eli, prov, time and skos projection.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "akoma-ntoso-legalruleml-eli-prov-time-and-skos-projection-record", "name": "Akoma Ntoso, LegalRuleML, ELI, PROV, Time and SKOS projection record", "description": "Versioned evidence-bearing record for akoma ntoso, legalruleml, eli, prov, time and skos projection with source anchors, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical legal-instrument record", "authoritative source or evidence reference" ], "serial": true, "identity_strategy": "Legal-work identifier plus akoma-ntoso-legalruleml-eli-prov-time-and-skos-projection assertion or event identifier; title, citation, URL, date, text and hash never identify the work alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "official-public-restricted-draft-protected-annex-and-purpose-view", "name": "Official public, restricted draft, protected annex and purpose view", "description": "Audience, purpose, legal status, redaction, subdivision visibility, language, attribution, expiry, inference risk and access decision.", "source_refs": [ "SRC-001", "SRC-004", "SRC-009" ], "questions": [ { "id": "official-public-restricted-draft-protected-annex-and-purpose-view-q01", "text": "What exact identities, classes, values, links and explicit unknowns define official public, restricted draft, protected annex and purpose view?", "kind": "access", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "official-public-restricted-draft-protected-annex-and-purpose-view-q02", "text": "Which competent authority, source fragment, publication, evidence and legal or knowledge time supports official public, restricted draft, protected annex and purpose view?", "kind": "evidence", "answer_data": [ "authority", "source and fragment", "publication", "times", "evidence" ] }, { "id": "official-public-restricted-draft-protected-annex-and-purpose-view-q03", "text": "How may official public, restricted draft, protected annex and purpose view be validated, contested, corrected, superseded, retained or disclosed without erasing cited history?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "retention", "access" ] } ], "data_elements": [ { "id": "official-public-restricted-draft-protected-annex-and-purpose-view-data", "name": "Official public, restricted draft, protected annex and purpose view data", "description": "Structured authority-qualified data for official public, restricted draft, protected annex and purpose view.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-009" ] } ], "artifacts": [ { "id": "official-public-restricted-draft-protected-annex-and-purpose-view-record", "name": "Official public, restricted draft, protected annex and purpose view record", "description": "Versioned evidence-bearing record for official public, restricted draft, protected annex and purpose view with source anchors, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical legal-instrument record", "authoritative source or evidence reference" ], "serial": true, "identity_strategy": "Legal-work identifier plus official-public-restricted-draft-protected-annex-and-purpose-view assertion or event identifier; title, citation, URL, date, text and hash never identify the work alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "safe-agent-operations-validation-and-records", "name": "Safe agent operations, validation and records", "description": "Controls autonomous proposals, accountable confirmation, invariants, retention and recovery.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-010" ], "findings": [ { "id": "agent-operation-authority-purpose-preconditions-and-confirmation", "name": "Agent operation, authority, purpose, preconditions and confirmation", "description": "Classifies register, publish, cite, formalize, amend, consolidate, disclose and retire operations as autonomous, propose, confirm or forbidden.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "agent-operation-authority-purpose-preconditions-and-confirmation-q01", "text": "What exact identities, classes, values, links and explicit unknowns define agent operation, authority, purpose, preconditions and confirmation?", "kind": "security", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "agent-operation-authority-purpose-preconditions-and-confirmation-q02", "text": "Which competent authority, source fragment, publication, evidence and legal or knowledge time supports agent operation, authority, purpose, preconditions and confirmation?", "kind": "evidence", "answer_data": [ "authority", "source and fragment", "publication", "times", "evidence" ] }, { "id": "agent-operation-authority-purpose-preconditions-and-confirmation-q03", "text": "How may agent operation, authority, purpose, preconditions and confirmation be validated, contested, corrected, superseded, retained or disclosed without erasing cited history?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "retention", "access" ] } ], "data_elements": [ { "id": "agent-operation-authority-purpose-preconditions-and-confirmation-data", "name": "Agent operation, authority, purpose, preconditions and confirmation data", "description": "Structured authority-qualified data for agent operation, authority, purpose, preconditions and confirmation.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "agent-operation-authority-purpose-preconditions-and-confirmation-record", "name": "Agent operation, authority, purpose, preconditions and confirmation record", "description": "Versioned evidence-bearing record for agent operation, authority, purpose, preconditions and confirmation with source anchors, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical legal-instrument record", "authoritative source or evidence reference" ], "serial": true, "identity_strategy": "Legal-work identifier plus agent-operation-authority-purpose-preconditions-and-confirmation assertion or event identifier; title, citation, URL, date, text and hash never identify the work alone.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null }, { "id": "prewrite-postwrite-validation-concurrency-retention-and-recovery", "name": "Pre-write and post-write validation, concurrency, retention and recovery", "description": "Identity, authority, address, citation, time, lifecycle, formalization, access and stale-head checks with immutable history and rollback evidence.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-010" ], "questions": [ { "id": "prewrite-postwrite-validation-concurrency-retention-and-recovery-q01", "text": "What exact identities, classes, values, links and explicit unknowns define pre-write and post-write validation, concurrency, retention and recovery?", "kind": "validation", "answer_data": [ "identities and values", "class and profile", "links", "unknowns" ] }, { "id": "prewrite-postwrite-validation-concurrency-retention-and-recovery-q02", "text": "Which competent authority, source fragment, publication, evidence and legal or knowledge time supports pre-write and post-write validation, concurrency, retention and recovery?", "kind": "evidence", "answer_data": [ "authority", "source and fragment", "publication", "times", "evidence" ] }, { "id": "prewrite-postwrite-validation-concurrency-retention-and-recovery-q03", "text": "How may pre-write and post-write validation, concurrency, retention and recovery be validated, contested, corrected, superseded, retained or disclosed without erasing cited history?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "retention", "access" ] } ], "data_elements": [ { "id": "prewrite-postwrite-validation-concurrency-retention-and-recovery-data", "name": "Pre-write and post-write validation, concurrency, retention and recovery data", "description": "Structured authority-qualified data for pre-write and post-write validation, concurrency, retention and recovery.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-010" ] } ], "artifacts": [ { "id": "prewrite-postwrite-validation-concurrency-retention-and-recovery-record", "name": "Pre-write and post-write validation, concurrency, retention and recovery record", "description": "Versioned evidence-bearing record for pre-write and post-write validation, concurrency, retention and recovery with source anchors, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical legal-instrument record", "authoritative source or evidence reference" ], "serial": true, "identity_strategy": "Legal-work identifier plus prewrite-postwrite-validation-concurrency-retention-and-recovery assertion or event identifier; title, citation, URL, date, text and hash never identify the work alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-010" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-legal-work", "name": "Register legal work", "description": "Create authority-qualified identity, class, master register and initial source binding.", "inputs": [ "register", "work identifier", "class", "authority", "source" ], "outputs": [ "registered legal work revision" ], "preconditions": [ "authority, namespace and uniqueness validate" ], "effects": [ "the work becomes resolvable without collapsing its expressions" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "add-expression-or-manifestation", "name": "Add expression or manifestation", "description": "Bind a language expression, file manifestation or held item to the same legal work.", "inputs": [ "work", "language or media", "content", "publisher" ], "outputs": [ "expression or manifestation record" ], "preconditions": [ "work and derivation resolve" ], "effects": [ "the new representation is separately identifiable and attributable" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006" ] }, { "id": "authenticate-authoritative-source", "name": "Authenticate authoritative source", "description": "Record publisher, publication act, authenticity evidence, digest and copy status.", "inputs": [ "manifestation", "publisher", "evidence", "verification method" ], "outputs": [ "source authentication assertion" ], "preconditions": [ "publisher role and evidence are known" ], "effects": [ "official and unofficial copies remain distinguishable" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-006", "SRC-009" ] }, { "id": "address-provision-and-citation", "name": "Address provision and citation", "description": "Mint or bind stable subdivision identities and resolve static or dynamic citations.", "inputs": [ "work", "component tree", "citation", "version context" ], "outputs": [ "address and resolution records" ], "preconditions": [ "source versions and numbering history resolve" ], "effects": [ "provisions stay citable across rendition and renumbering" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "bind-norm-to-source", "name": "Bind norm to source", "description": "Attach a structured or formal norm to exact source fragments with author, method and confidence.", "inputs": [ "norm", "source fragments", "formalization", "authority" ], "outputs": [ "source-linked norm assertion" ], "preconditions": [ "source fragments and expression version resolve" ], "effects": [ "formal semantics remain attributable and contestable" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "id": "record-legal-lifecycle-event", "name": "Record legal lifecycle event", "description": "Append adoption, publication, commencement, suspension, repeal, expiry or correction evidence.", "inputs": [ "work or provision", "event", "authority", "times", "evidence" ], "outputs": [ "lifecycle event and state assertion" ], "preconditions": [ "competence, affected scope and times validate" ], "effects": [ "state changes without overwriting prior assertions" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-007", "SRC-010" ] }, { "id": "construct-consolidated-view", "name": "Construct consolidated view", "description": "Apply cited modifications to create a dated non-authoritative or authority-qualified consolidated expression.", "inputs": [ "base expression", "modifications", "cutoff time", "profile" ], "outputs": [ "consolidated view and derivation graph" ], "preconditions": [ "all applied sources and unresolved conflicts are explicit" ], "effects": [ "the view remains distinct from original acts" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "assess-applicability-as-assertion", "name": "Assess applicability as assertion", "description": "Produce a source-qualified applicability result for stated facts without claiming universal legal judgment.", "inputs": [ "norms", "facts", "party", "place", "time", "profile" ], "outputs": [ "applicability assertion with uncertainty" ], "preconditions": [ "versions, jurisdiction and authority scope resolve" ], "effects": [ "reasoning inputs and unresolved conflicts stay inspectable" ], "source_refs": [ "SRC-003", "SRC-007" ] }, { "id": "issue-interoperability-view", "name": "Issue interoperability view", "description": "Project a selected legal-work revision to Akoma Ntoso, LegalRuleML, ELI or linked-data form with declared loss.", "inputs": [ "work revision", "target profile", "purpose", "access context" ], "outputs": [ "validated projection" ], "preconditions": [ "target version and disclosure policy validate" ], "effects": [ "projection links source digest and omissions" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "retire-or-supersede-legal-work", "name": "Retire or supersede legal work", "description": "Mark expiry, repeal or replacement while preserving citations, versions, sources and successor resolution.", "inputs": [ "work", "authority", "reason", "successors", "effect time" ], "outputs": [ "retirement event and tombstone" ], "preconditions": [ "authority and successor mapping validate" ], "effects": [ "future active use is blocked while history stays citable" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-010" ] } ], "composition": [ { "target": "Organization, Government and Authority models", "relation": "REFERENCE", "purpose": "Resolve issuing, adopting, promulgating, publishing and interpreting actors without duplicating their masters.", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "target": "Legislative Process, Court Case, Enforcement Event, Person, Place and Document models", "relation": "REFERENCE", "purpose": "Connect the instrument to external creation, interpretation, application, party, jurisdiction and storage contexts.", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "target": "Akoma Ntoso", "relation": "ALIGN", "purpose": "Project legal-document structure, identifiers, references, metadata and lifecycle markup.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "LegalRuleML", "relation": "ALIGN", "purpose": "Project source-linked formal norms, modalities, temporal characteristics, exceptions and override relations.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "ELI, PROV-O, OWL-Time and SKOS", "relation": "ALIGN", "purpose": "Project legal-resource identity, metadata, provenance, time and controlled classifications with explicit version and loss.", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Dimension identity, owner, legal-register authority, publication authority and namespace", "Legal work, expression, manifestation, provision, norm, lifecycle, citation and interpretation registries", "Master-system mappings for authority, instrument, source, case, party, place and event references", "Identity, authority, authenticity, temporal, citation, amendment, access, retention and agent-operation policies" ], "namespace_guidance": "Mint legal-work and assertion identifiers only when no authoritative legal register identity exists; keep organizations, procedures, cases, enforcement events, parties, places and generic documents as typed references.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md", "Dimension-local legal work, provision, norm, citation, lifecycle and interpretation registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by authority-qualified legal-work identifier and register, never by title, citation, URL, language, text, file, date or digest.", "Keep work, expression, manifestation, item, authoritative source, provision, norm and formal rule separately identifiable." ], "patch_rules": [ "Extensions declare legal-system profile, target finding, source, authority, vocabulary versions, temporal semantics and interoperability impact.", "Identity, authority, source anchoring, normative semantics or lifecycle changes require a successor version, migration map and continued resolution of cited history." ], "compatibility_rules": [ "Unknown additive fields may be ignored only when identity, authority, source, provision addresses, legal times, lifecycle, access and provenance remain intact.", "Every Akoma Ntoso, LegalRuleML, ELI or linked-data projection pins versions and states transformed fields, omissions and round-trip limits." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-register identifier for the legal work, qualified by issuing or publishing jurisdiction.", "Governed globally resolvable legal-resource IRI with authoritative register binding.", "Dimension UUID or ULID when no external identifier exists." ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and offset or Z; separate adoption, signature, publication, commencement, efficacy, applicability, observation, knowledge and ingestion times.", "serial_naming_rule": "Use {legal-work-id}--{artifact-kind}--{assertion-or-event-id}; never use title, citation, URL, language, date or hash alone.", "integrity_rule": "Store digest, media type, language, publisher, source and profile versions, authority, valid and knowledge times, source anchors, quality, licence and access marking." }, "policies": [ "Only a competent legal or publication authority may establish canonical source status or authority-qualified lifecycle effect.", "Publication, online availability, a formal rule or a consolidated view never alone proves validity, force or applicability.", "Agents may extract, validate and propose; amendment, legal-status assertion, final interpretation, wider disclosure and destructive retirement require accountable authority.", "Conflicting texts, norms, interpretations and temporal assertions remain separately attributable until resolved by a competent process." ], "crud": { "read": [ "Resolve Dimension, legal-system profile, register, authority, work version, expression language, provision address, legal time and access purpose." ], "create": [ "Create work identity, authority, class, source, expression and explicit unknowns before norms, lifecycle conclusions or projections." ], "update": [ "Append assertion or event with authority, reason, source fragments, legal and knowledge time and validation; never overwrite cited history." ], "delete": [ "Apply legal hold and records policy; prefer repeal, expiry, supersession or tombstone and never cascade to authorities, cases, parties or events." ] }, "roles": [ { "name": "Legal-register authority", "responsibilities": [ "Own canonical work identity, instrument class and authority-qualified lifecycle." ] }, { "name": "Official publisher", "responsibilities": [ "Publish authoritative expressions and manifestations with authenticity evidence." ] }, { "name": "Legislative or rulemaking authority", "responsibilities": [ "Own adoption, amendment, repeal and enabling-power evidence." ] }, { "name": "Legal information steward", "responsibilities": [ "Maintain structure, citations, consolidation lineage and controlled classifications." ] }, { "name": "Norm formalization reviewer", "responsibilities": [ "Validate source anchoring, modalities, conditions and uncertainty of formal norms." ] }, { "name": "Access and records steward", "responsibilities": [ "Apply disclosure, protected-annex, retention and legal-hold policy." ] }, { "name": "Interoperability steward", "responsibilities": [ "Validate format mappings, source identity and declared information loss." ] } ], "access": { "default_rule": "Deny mutation and restricted draft or protected-provision disclosure unless register, role, purpose and field policy grant it; expose only the necessary source and precision.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Statutory, judicial, oversight or emergency access cites authority and remains purpose-bound, attributable and reviewable." ], "audit_requirements": [ "Log actor, agent, role, purpose, legal work, operation, policy, RFC 3339 time, authority, affected source fragments and outcome." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read Dimension legal-register, source-authority, temporal, citation, amendment, interpretation, access and retention policies.", "Read this model and linked organization, process, case, event, party and place models before mutation." ] } }, "coverage": { "claim": "A source-grounded reviewable draft of a legal instrument and its source-linked norms across Akoma Ntoso, LegalRuleML, ELI, PROV-O, OWL-Time and SKOS, without universal substantive-law, legal-advice, binding-interpretation or certified crosswalk claims.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Authority-qualified work identity and separate expression, manifestation, item, source, provision and norm identity are explicit." }, { "dimension": "classification and definition", "status": "covered", "notes": "Instrument, jurisdiction, subject, status and norm classifications are versioned." }, { "dimension": "direct properties", "status": "covered", "notes": "Structure, text anchors, citations, modality, conditions, legal states and integrity properties are first-class." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Authority, authenticity, publication, derivation, verification and confidence evidence are covered." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Register, publish, address, cite, formalize, amend, consolidate, project and retire operations are governed." }, { "dimension": "composition", "status": "covered", "notes": "Authorities, procedures, cases, enforcement events, parties, places and generic documents retain external masters." }, { "dimension": "lifecycle", "status": "covered", "notes": "Drafting, adoption, signature, publication, commencement, suspension, repeal, expiry, correction and supersession preserve history." }, { "dimension": "relationships", "status": "covered", "notes": "Citations, amendments, derivations, overrides, exceptions, successors and interpretations are typed and attributable." }, { "dimension": "temporal", "status": "covered", "notes": "Legal event, validity, force, efficacy, applicability, observation and knowledge times remain distinct." }, { "dimension": "spatial", "status": "covered", "notes": "Territorial jurisdiction and place references are covered without importing geographic masters." }, { "dimension": "provenance", "status": "covered", "notes": "Source publication, derivation, attribution, custody, digest and formalization history remain attributable." }, { "dimension": "ownership and stewardship", "status": "covered", "notes": "Register, publisher, lawmaking, formalization, access and interoperability roles remain separate." }, { "dimension": "validation and quality", "status": "covered", "notes": "Identity, authority, addresses, citations, time, lifecycle, formalization, access and stale-head checks are explicit." }, { "dimension": "access and privacy", "status": "covered", "notes": "Public, restricted draft, protected annex and purpose-bound views are covered." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Original sources, amendments, superseded versions, citations and tombstones are preserved." }, { "dimension": "interoperability", "status": "covered", "notes": "Akoma Ntoso, LegalRuleML, ELI, PROV, OWL-Time and SKOS projections are loss-aware." } ], "known_omissions": [ "No independent Claude or Grok result was available; later comparative legal and legal-informatics review is required before canonical promotion.", "Jurisdiction-specific constitutional hierarchy, legislative procedure, publication law, treaty law, customary law, religious law and multilingual drafting profiles require specialist review.", "The frozen relation ledger contains no approved WM-POL-001 rows; all composition targets remain draft.", "Certified Akoma Ntoso, LegalRuleML, ELI and linked-data crosswalks, validation fixtures and legal-system profiles remain future work." ], "conflicts": [ "A legally authoritative instrument source and a formal norm or executable rule are not interchangeable.", "Validity, force, efficacy, applicability and publication can disagree for the same work or provision.", "Original acts, correcting acts, amendments and consolidated views can expose different text without sharing the same legal authority." ], "regional_assumptions": [ "ELI is a European interoperability framework and does not define universal substantive law.", "Akoma Ntoso and LegalRuleML are representation standards and do not create legal authority or binding interpretation.", "A jurisdiction's competent authorities and adopted legal-system profile control legal effect." ], "adversarial_checks": [ "Reject identity inferred from title, citation, URL, language, text, file or hash alone.", "Reject a publication or consolidation represented as binding without competent-authority evidence.", "Reject a formalized rule treated as identical to its legal source or as uncontested interpretation.", "Reject applicability or conflict resolution that hides facts, provision versions, jurisdiction, time, authority or uncertainty.", "Reject destructive amendment or deletion that erases cited source and lifecycle history." ] }, "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": "aggregate", "status": "accepted only with separable legal-work, expression, manifestation, source, provision and norm identities", "rationale": "The combined catalogue identity is useful when source and norm must travel together, but a file, legal source, natural-language provision and formal norm remain separately attributable objects. Organizations, procedures, cases, enforcement events, parties, places and generic repositories stay external masters." }, "decisions": [ { "concept": "Aggregate boundary", "disposition": "accepted with internal identity separation", "rationale": "A legal instrument and its expressed norms may share one package only when work, expression, manifestation, authoritative source, provision and norm identifiers never collapse." }, { "concept": "Authority and authenticity", "disposition": "accepted as attributable assertions", "rationale": "Publication, signature, seal, register and digest evidence are preserved, but legal authority is never inferred from availability or file integrity alone." }, { "concept": "Norm formalization", "disposition": "accepted as source-linked and contestable", "rationale": "Every structured or executable rule cites exact source fragments, author, method, version and confidence and cannot silently replace the legal text." }, { "concept": "Legal states and time", "disposition": "accepted as profile-qualified multi-axis assertions", "rationale": "Adoption, publication, validity, force, efficacy, applicability, observation and knowledge time can differ by provision and jurisdiction." }, { "concept": "Amendment and consolidation", "disposition": "accepted as immutable lineage", "rationale": "Original, modifying and correcting acts remain distinct, while every consolidated view records applied sources, cutoff and unresolved conflicts." }, { "concept": "Citation semantics", "disposition": "accepted as version-scoped relations", "rationale": "Static and dynamic citations identify target work or provision, version rule, language and resolution result rather than relying on rendered numbering." }, { "concept": "Conflict and interpretation", "disposition": "no universal adjudication", "rationale": "Priority, override, derogation, exception, guidance and holdings remain authority-qualified assertions and do not become automatic legal advice." }, { "concept": "Interoperability", "disposition": "accepted as loss-aware projections", "rationale": "Akoma Ntoso, LegalRuleML, ELI and W3C vocabularies serve different purposes, so mappings pin versions and disclose source, semantic and round-trip loss." }, { "concept": "Approved registry composition", "disposition": "held pending relation governance", "rationale": "The approved relation ledger contains no WM-POL-001 rows, so proposed links to organizations, processes, cases, events, parties, places and document masters remain draft." } ], "publicationHolds": [ "Claude and Grok timed out during their bounded attempts, so independent external review is absent and explicitly waived for this published reviewable draft.", "The approved relationship ledger contains no WM-POL-001 rows, so all proposed sibling composition remains draft.", "Jurisdiction-specific constitutional hierarchy, legislative procedure, publication law, treaty, customary, religious and multilingual drafting profiles require specialist review.", "Certified Akoma Ntoso, LegalRuleML, ELI, PROV-O, OWL-Time and SKOS crosswalks and legal-system conformance fixtures remain unverified.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Approve identifiers and relation cardinalities for organization, authority, process, case, enforcement event, party, place and generic document models.", "Develop jurisdiction, instrument-type, treaty, delegated legislation, customary law and multilingual drafting profiles.", "Create fixtures for provision renumbering, partial commencement, retroactivity, conflicting amendments, protected annexes, unofficial translations and disputed consolidation.", "Validate certified legal-document and legal-rule projections with source-anchor, authority, time, information-loss and round-trip tests." ] }, "statistics": { "sources": 10, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }