# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T02:35:12Z", "synthesisSha256": "ea8184c4bc4497b7206edc113a65fcefa11da02bab7b56646ebb18a6dce66340", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-PLC-004", "registryId": "vr.wm-plc-004", "name": "Administrative Area", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.PLC.ADM" ], "tags": [ "administrative", "area", "phy.plc.adm" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-plc-004-administrative-area/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-plc-004", "model": { "registry_id": "vr.wm-plc-004", "model_id": "WM-PLC-004", "name": "Administrative Area", "entry_kind": "entity", "purpose": "Represent a governed administrative or official statistical territorial unit with stable identity, versioned codes and names, authority, hierarchy, direct boundary geometry and lifecycle independent of storage and interface format.", "scope_statement": "Owns administrative-area identity, type and level, code and name bindings, constitutive authority references, typed hierarchy, source-qualified boundaries, CRS, topology, effective time, lifecycle, recognition and provenance. Governments, jurisdictions, instruments, settlements, addresses, zones, parcels, terrain, statistics and disputes remain external masters.", "in_scope": [ "Unit identity, code systems, names, class, level, authority and instruments", "Administrative and spatial hierarchy, boundary roles, geometry, CRS, area, topology and quality", "Lifecycle and lineage, place and statistic references, disputes, projections and safe operations" ], "out_of_scope": [ "Government organization, legal jurisdiction and sovereignty adjudication", "Settlement, address, postal, electoral, service and planning zones, parcel, terrain and population masters", "Universal recognition of codes, boundaries or territorial claims" ], "boundary_notes": [ { "neighbor": "Government and Jurisdiction", "distinction": "A government is an organization and a jurisdiction is a competence relation; the administrative area is the territorial unit they may govern.", "source_refs": [ "SRC-003" ] }, { "neighbor": "Settlement, Place and Address", "distinction": "A settlement or locality can cross or sit within units, and addresses locate objects; none defines administrative identity.", "source_refs": [ "SRC-006" ] }, { "neighbor": "Statistical, Postal and Electoral Area", "distinction": "These purpose-built zones can map to administrative units but retain independent authority, geometry and lifecycle.", "source_refs": [ "SRC-002", "SRC-007" ] }, { "neighbor": "Land Parcel", "distinction": "A parcel is a land-administration spatial unit at property or cadastral grain, not an administrative government territory.", "source_refs": [ "SRC-003" ] }, { "neighbor": "Sovereignty and Territorial Claim", "distinction": "The model preserves who claims or recognizes an extent and for what scope but never decides universal sovereignty.", "source_refs": [ "SRC-002", "SRC-008" ] } ] }, "sources": [ { "id": "SRC-001", "title": "ISO 3166 Country Codes", "organization": "International Organization for Standardization", "url": "https://www.iso.org/iso-3166-country-codes.html", "version_or_date": "ISO 3166 code family, official service accessed 6 September 2026", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:33:00Z", "relevance": "Provides governed country, subdivision and formerly-used code families; every code requires part, edition or update context and cannot replace a jurisdiction's own administrative-unit identity." }, { "id": "SRC-002", "title": "Standard country or area codes for statistical use, M49", "organization": "United Nations Statistics Division", "url": "https://unstats.un.org/unsd/methodology/m49/", "version_or_date": "UN M49 methodology and current list, accessed 6 September 2026", "source_type": "classifier", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:33:00Z", "relevance": "Provides numerical country and area codes and geographic-region groupings for statistical use, including change history and explicit statistical purpose." }, { "id": "SRC-003", "title": "INSPIRE Data Specification on Administrative Units", "organization": "European Commission INSPIRE", "url": "https://inspire.ec.europa.eu/id/document/tg/au", "version_or_date": "Technical Guidelines, current document service accessed 6 September 2026", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:33:00Z", "relevance": "Defines administrative units, boundaries, levels, national codes, names, residence of authority and lifecycle metadata for European spatial-data interoperability." }, { "id": "SRC-004", "title": "OGC GeoSPARQL 1.1", "organization": "Open Geospatial Consortium", "url": "https://docs.ogc.org/is/22-047r1/22-047r1.html", "version_or_date": "OGC 22-047r1, Version 1.1", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:33:00Z", "relevance": "Defines feature and geometry representations, coordinate reference system serialization and topological relations for semantic spatial projections." }, { "id": "SRC-005", "title": "Geography Markup Language", "organization": "Open Geospatial Consortium", "url": "https://www.ogc.org/standards/gml", "version_or_date": "GML standard family, accessed 6 September 2026", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:33:00Z", "relevance": "Provides feature, geometry, coordinate reference system, topology and temporal encodings used by administrative-boundary exchange profiles." }, { "id": "SRC-006", "title": "ISO 19112 Geographic information, Spatial referencing by geographic identifiers", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/74046.html", "version_or_date": "ISO 19112:2019", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:33:00Z", "relevance": "Provides a conceptual scheme for spatial references based on geographic identifiers and gazetteer relationships, useful for code and name based location without equating identifiers with geometry." }, { "id": "SRC-007", "title": "Regulation on the establishment of a common classification of territorial units for statistics", "organization": "European Union", "url": "https://eur-lex.europa.eu/eli/reg/2003/1059/oj", "version_or_date": "Regulation (EC) No 1059/2003, consolidated framework", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:33:00Z", "relevance": "Establishes NUTS territorial units for statistics and amendment cycles; these statistical units are not automatically equivalent to administrative or legal jurisdictions." }, { "id": "SRC-008", "title": "Second Administrative Level Boundaries", "organization": "United Nations", "url": "https://salb.un.org/", "version_or_date": "UN SALB service, accessed 6 September 2026", "source_type": "registry", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:33:00Z", "relevance": "Provides a UN-supported repository and methodology for first and second subnational administrative boundaries and their temporal changes, with national-source and validation context." }, { "id": "SRC-009", "title": "The GeoJSON Format", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc7946", "version_or_date": "RFC 7946, August 2016", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:33:00Z", "relevance": "Defines a WGS 84 web geometry encoding and antimeridian rules; it is a display or exchange projection and cannot preserve every native CRS, topology or disputed-boundary semantic." }, { "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:33:00Z", "relevance": "Defines timestamps with seconds and explicit UTC relation for legal-effect, observation, publication, knowledge and lifecycle events." } ], "structure": { "bundles": [ { "id": "identity-codes-names-and-class", "name": "Identity, codes, names and class", "description": "Identifies one administrative unit in its authoritative system and distinguishes its names and external code projections.", "rationale": "Names and codes change, collide and serve different purposes; none is a timeless global identity by itself.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ], "layers": [ { "id": "master-identity-and-code-systems", "name": "Master identity and code systems", "description": "Stable identity, source register and versioned codes.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ], "findings": [ { "id": "authoritative-unit-identifier-register-and-issuing-authority", "name": "Authoritative unit identifier, register and issuing authority", "description": "Stable unit identifier, namespace, master register, issuing authority, resolution state and aliases.", "source_refs": [ "SRC-003", "SRC-006" ], "questions": [ { "id": "authoritative-unit-identifier-register-and-issuing-authority-q01", "text": "What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for authoritative unit identifier, register and issuing authority?", "kind": "identity", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "authoritative-unit-identifier-register-and-issuing-authority-q02", "text": "Which register, government, statistical authority, source and evidence establishes authoritative unit identifier, register and issuing authority, at what legal, observation and knowledge time, and for which recognition scope?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "recognition scope", "evidence" ] }, { "id": "authoritative-unit-identifier-register-and-issuing-authority-q03", "text": "How may authoritative unit identifier, register and issuing authority be validated, contested, corrected, superseded, retained or disclosed without erasing history or conflating hierarchy, geometry and authority?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "authoritative-unit-identifier-register-and-issuing-authority-data", "name": "Authoritative unit identifier, register and issuing authority data", "description": "Structured source-qualified data for authoritative unit identifier, register and issuing authority.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "authoritative-unit-identifier-register-and-issuing-authority-record", "name": "Authoritative unit identifier, register and issuing authority record", "description": "Versioned evidence-bearing record for authoritative unit identifier, register and issuing authority with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical administrative-area record", "official or statistical evidence reference" ], "serial": true, "identity_strategy": "Administrative-area identifier plus authoritative-unit-identifier-register-and-issuing-authority assertion or event identifier; names, codes, geometry, dates and hashes never identify the unit alone.", "source_refs": [ "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "national-iso-m49-nuts-salb-and-local-code-bindings", "name": "National, ISO, M49, NUTS, SALB and local code bindings", "description": "Code-list identity, part or scheme, edition, code, validity, issuer, mapping scope and retired-code successor.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007", "SRC-008" ], "questions": [ { "id": "national-iso-m49-nuts-salb-and-local-code-bindings-q01", "text": "What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for national, iso, m49, nuts, salb and local code bindings?", "kind": "classification", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "national-iso-m49-nuts-salb-and-local-code-bindings-q02", "text": "Which register, government, statistical authority, source and evidence establishes national, iso, m49, nuts, salb and local code bindings, at what legal, observation and knowledge time, and for which recognition scope?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "recognition scope", "evidence" ] }, { "id": "national-iso-m49-nuts-salb-and-local-code-bindings-q03", "text": "How may national, iso, m49, nuts, salb and local code bindings be validated, contested, corrected, superseded, retained or disclosed without erasing history or conflating hierarchy, geometry and authority?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "national-iso-m49-nuts-salb-and-local-code-bindings-data", "name": "National, ISO, M49, NUTS, SALB and local code bindings data", "description": "Structured source-qualified data for national, iso, m49, nuts, salb and local code bindings.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "national-iso-m49-nuts-salb-and-local-code-bindings-record", "name": "National, ISO, M49, NUTS, SALB and local code bindings record", "description": "Versioned evidence-bearing record for national, iso, m49, nuts, salb and local code bindings with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical administrative-area record", "official or statistical evidence reference" ], "serial": true, "identity_strategy": "Administrative-area identifier plus national-iso-m49-nuts-salb-and-local-code-bindings assertion or event identifier; names, codes, geometry, dates and hashes never identify the unit alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "unit-class-level-and-names", "name": "Unit class, level and names", "description": "Administrative classification and multilingual naming history.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ], "findings": [ { "id": "administrative-unit-type-level-order-and-classification", "name": "Administrative-unit type, level, order and classification", "description": "Jurisdiction-defined type and level, hierarchy order, official or statistical status, class criteria and version.", "source_refs": [ "SRC-003", "SRC-007" ], "questions": [ { "id": "administrative-unit-type-level-order-and-classification-q01", "text": "What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for administrative-unit type, level, order and classification?", "kind": "classification", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "administrative-unit-type-level-order-and-classification-q02", "text": "Which register, government, statistical authority, source and evidence establishes administrative-unit type, level, order and classification, at what legal, observation and knowledge time, and for which recognition scope?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "recognition scope", "evidence" ] }, { "id": "administrative-unit-type-level-order-and-classification-q03", "text": "How may administrative-unit type, level, order and classification be validated, contested, corrected, superseded, retained or disclosed without erasing history or conflating hierarchy, geometry and authority?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "administrative-unit-type-level-order-and-classification-data", "name": "Administrative-unit type, level, order and classification data", "description": "Structured source-qualified data for administrative-unit type, level, order and classification.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-007" ] } ], "artifacts": [ { "id": "administrative-unit-type-level-order-and-classification-record", "name": "Administrative-unit type, level, order and classification record", "description": "Versioned evidence-bearing record for administrative-unit type, level, order and classification with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical administrative-area record", "official or statistical evidence reference" ], "serial": true, "identity_strategy": "Administrative-area identifier plus administrative-unit-type-level-order-and-classification assertion or event identifier; names, codes, geometry, dates and hashes never identify the unit alone.", "source_refs": [ "SRC-003", "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "official-short-long-multilingual-historic-and-variant-names", "name": "Official, short, long, multilingual, historic and variant names", "description": "Language, script, name type, authority, valid interval, transliteration, pronunciation and deprecated forms.", "source_refs": [ "SRC-003", "SRC-006" ], "questions": [ { "id": "official-short-long-multilingual-historic-and-variant-names-q01", "text": "What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for official, short, long, multilingual, historic and variant names?", "kind": "definition", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "official-short-long-multilingual-historic-and-variant-names-q02", "text": "Which register, government, statistical authority, source and evidence establishes official, short, long, multilingual, historic and variant names, at what legal, observation and knowledge time, and for which recognition scope?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "recognition scope", "evidence" ] }, { "id": "official-short-long-multilingual-historic-and-variant-names-q03", "text": "How may official, short, long, multilingual, historic and variant names be validated, contested, corrected, superseded, retained or disclosed without erasing history or conflating hierarchy, geometry and authority?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "official-short-long-multilingual-historic-and-variant-names-data", "name": "Official, short, long, multilingual, historic and variant names data", "description": "Structured source-qualified data for official, short, long, multilingual, historic and variant names.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "official-short-long-multilingual-historic-and-variant-names-record", "name": "Official, short, long, multilingual, historic and variant names record", "description": "Versioned evidence-bearing record for official, short, long, multilingual, historic and variant names with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical administrative-area record", "official or statistical evidence reference" ], "serial": true, "identity_strategy": "Administrative-area identifier plus official-short-long-multilingual-historic-and-variant-names assertion or event identifier; names, codes, geometry, dates and hashes never identify the unit alone.", "source_refs": [ "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "authority-hierarchy-and-jurisdiction-context", "name": "Authority, hierarchy and jurisdiction context", "description": "Connects the unit to constitutive authority and several non-equivalent hierarchy relations.", "rationale": "Administrative parentage, territorial containment, statistical nesting and governmental competence can diverge.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-007" ], "layers": [ { "id": "constitutive-authority-and-instrument", "name": "Constitutive authority and instrument", "description": "Legal or official basis and the organization exercising competence.", "source_refs": [ "SRC-003", "SRC-007" ], "findings": [ { "id": "constituting-instrument-authority-jurisdiction-and-legal-effect", "name": "Constituting instrument, authority, jurisdiction and legal effect", "description": "External instrument, issuing authority, legal basis, applicable jurisdiction, effective interval, publication and contest status.", "source_refs": [ "SRC-003", "SRC-007" ], "questions": [ { "id": "constituting-instrument-authority-jurisdiction-and-legal-effect-q01", "text": "What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for constituting instrument, authority, jurisdiction and legal effect?", "kind": "authority", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "constituting-instrument-authority-jurisdiction-and-legal-effect-q02", "text": "Which register, government, statistical authority, source and evidence establishes constituting instrument, authority, jurisdiction and legal effect, at what legal, observation and knowledge time, and for which recognition scope?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "recognition scope", "evidence" ] }, { "id": "constituting-instrument-authority-jurisdiction-and-legal-effect-q03", "text": "How may constituting instrument, authority, jurisdiction and legal effect be validated, contested, corrected, superseded, retained or disclosed without erasing history or conflating hierarchy, geometry and authority?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "constituting-instrument-authority-jurisdiction-and-legal-effect-data", "name": "Constituting instrument, authority, jurisdiction and legal effect data", "description": "Structured source-qualified data for constituting instrument, authority, jurisdiction and legal effect.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-007" ] } ], "artifacts": [ { "id": "constituting-instrument-authority-jurisdiction-and-legal-effect-record", "name": "Constituting instrument, authority, jurisdiction and legal effect record", "description": "Versioned evidence-bearing record for constituting instrument, authority, jurisdiction and legal effect with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical administrative-area record", "official or statistical evidence reference" ], "serial": true, "identity_strategy": "Administrative-area identifier plus constituting-instrument-authority-jurisdiction-and-legal-effect assertion or event identifier; names, codes, geometry, dates and hashes never identify the unit alone.", "source_refs": [ "SRC-003", "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "government-organization-seat-capacity-and-competence-reference", "name": "Government organization, seat, capacity and competence reference", "description": "External governing organization and seat references, role or capacity, competence domain, delegation and validity.", "source_refs": [ "SRC-003" ], "questions": [ { "id": "government-organization-seat-capacity-and-competence-reference-q01", "text": "What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for government organization, seat, capacity and competence reference?", "kind": "relationship", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "government-organization-seat-capacity-and-competence-reference-q02", "text": "Which register, government, statistical authority, source and evidence establishes government organization, seat, capacity and competence reference, at what legal, observation and knowledge time, and for which recognition scope?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "recognition scope", "evidence" ] }, { "id": "government-organization-seat-capacity-and-competence-reference-q03", "text": "How may government organization, seat, capacity and competence reference be validated, contested, corrected, superseded, retained or disclosed without erasing history or conflating hierarchy, geometry and authority?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "government-organization-seat-capacity-and-competence-reference-data", "name": "Government organization, seat, capacity and competence reference data", "description": "Structured source-qualified data for government organization, seat, capacity and competence reference.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003" ] } ], "artifacts": [ { "id": "government-organization-seat-capacity-and-competence-reference-record", "name": "Government organization, seat, capacity and competence reference record", "description": "Versioned evidence-bearing record for government organization, seat, capacity and competence reference with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical administrative-area record", "official or statistical evidence reference" ], "serial": true, "identity_strategy": "Administrative-area identifier plus government-organization-seat-capacity-and-competence-reference assertion or event identifier; names, codes, geometry, dates and hashes never identify the unit alone.", "source_refs": [ "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "administrative-and-spatial-hierarchy", "name": "Administrative and spatial hierarchy", "description": "Versioned parent, containment and grouping relations.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-007" ], "findings": [ { "id": "administrative-parent-child-predecessor-and-sibling-relations", "name": "Administrative parent, child, predecessor and sibling relations", "description": "Typed hierarchy edges, authority, level consistency, valid time, exceptions and successor lineage.", "source_refs": [ "SRC-003", "SRC-006" ], "questions": [ { "id": "administrative-parent-child-predecessor-and-sibling-relations-q01", "text": "What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for administrative parent, child, predecessor and sibling relations?", "kind": "relationship", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "administrative-parent-child-predecessor-and-sibling-relations-q02", "text": "Which register, government, statistical authority, source and evidence establishes administrative parent, child, predecessor and sibling relations, at what legal, observation and knowledge time, and for which recognition scope?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "recognition scope", "evidence" ] }, { "id": "administrative-parent-child-predecessor-and-sibling-relations-q03", "text": "How may administrative parent, child, predecessor and sibling relations be validated, contested, corrected, superseded, retained or disclosed without erasing history or conflating hierarchy, geometry and authority?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "administrative-parent-child-predecessor-and-sibling-relations-data", "name": "Administrative parent, child, predecessor and sibling relations data", "description": "Structured source-qualified data for administrative parent, child, predecessor and sibling relations.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "administrative-parent-child-predecessor-and-sibling-relations-record", "name": "Administrative parent, child, predecessor and sibling relations record", "description": "Versioned evidence-bearing record for administrative parent, child, predecessor and sibling relations with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical administrative-area record", "official or statistical evidence reference" ], "serial": true, "identity_strategy": "Administrative-area identifier plus administrative-parent-child-predecessor-and-sibling-relations assertion or event identifier; names, codes, geometry, dates and hashes never identify the unit alone.", "source_refs": [ "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "geometric-containment-statistical-region-and-overlap-relations", "name": "Geometric containment, statistical region and overlap relations", "description": "Spatial containment or overlap and statistical grouping links kept separate from administrative subordination.", "source_refs": [ "SRC-002", "SRC-004", "SRC-007" ], "questions": [ { "id": "geometric-containment-statistical-region-and-overlap-relations-q01", "text": "What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for geometric containment, statistical region and overlap relations?", "kind": "spatial", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "geometric-containment-statistical-region-and-overlap-relations-q02", "text": "Which register, government, statistical authority, source and evidence establishes geometric containment, statistical region and overlap relations, at what legal, observation and knowledge time, and for which recognition scope?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "recognition scope", "evidence" ] }, { "id": "geometric-containment-statistical-region-and-overlap-relations-q03", "text": "How may geometric containment, statistical region and overlap relations be validated, contested, corrected, superseded, retained or disclosed without erasing history or conflating hierarchy, geometry and authority?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "geometric-containment-statistical-region-and-overlap-relations-data", "name": "Geometric containment, statistical region and overlap relations data", "description": "Structured source-qualified data for geometric containment, statistical region and overlap relations.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-007" ] } ], "artifacts": [ { "id": "geometric-containment-statistical-region-and-overlap-relations-record", "name": "Geometric containment, statistical region and overlap relations record", "description": "Versioned evidence-bearing record for geometric containment, statistical region and overlap relations with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical administrative-area record", "official or statistical evidence reference" ], "serial": true, "identity_strategy": "Administrative-area identifier plus geometric-containment-statistical-region-and-overlap-relations assertion or event identifier; names, codes, geometry, dates and hashes never identify the unit alone.", "source_refs": [ "SRC-002", "SRC-004", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "boundaries-geometry-topology-and-extent", "name": "Boundaries, geometry, topology and extent", "description": "Represents competing territorial extents with the coordinate and topology context needed to interpret them.", "rationale": "An official boundary, claimed boundary, statistical generalization and de facto control line can disagree without any one geometry settling recognition.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-008", "SRC-009" ], "layers": [ { "id": "boundary-assertions-and-recognition", "name": "Boundary assertions and recognition", "description": "Source-qualified official, statistical, claimed, disputed and de facto extents.", "source_refs": [ "SRC-003", "SRC-008" ], "findings": [ { "id": "official-statistical-claimed-disputed-and-de-facto-boundary", "name": "Official, statistical, claimed, disputed and de facto boundary", "description": "Geometry role, asserting authority, recognition audience, basis, effective interval, confidence and conflict set.", "source_refs": [ "SRC-003", "SRC-008" ], "questions": [ { "id": "official-statistical-claimed-disputed-and-de-facto-boundary-q01", "text": "What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for official, statistical, claimed, disputed and de facto boundary?", "kind": "spatial", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "official-statistical-claimed-disputed-and-de-facto-boundary-q02", "text": "Which register, government, statistical authority, source and evidence establishes official, statistical, claimed, disputed and de facto boundary, at what legal, observation and knowledge time, and for which recognition scope?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "recognition scope", "evidence" ] }, { "id": "official-statistical-claimed-disputed-and-de-facto-boundary-q03", "text": "How may official, statistical, claimed, disputed and de facto boundary be validated, contested, corrected, superseded, retained or disclosed without erasing history or conflating hierarchy, geometry and authority?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "official-statistical-claimed-disputed-and-de-facto-boundary-data", "name": "Official, statistical, claimed, disputed and de facto boundary data", "description": "Structured source-qualified data for official, statistical, claimed, disputed and de facto boundary.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "official-statistical-claimed-disputed-and-de-facto-boundary-record", "name": "Official, statistical, claimed, disputed and de facto boundary record", "description": "Versioned evidence-bearing record for official, statistical, claimed, disputed and de facto boundary with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical administrative-area record", "official or statistical evidence reference" ], "serial": true, "identity_strategy": "Administrative-area identifier plus official-statistical-claimed-disputed-and-de-facto-boundary assertion or event identifier; names, codes, geometry, dates and hashes never identify the unit alone.", "source_refs": [ "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "boundary-segment-point-source-demarcation-and-agreement", "name": "Boundary segment, point, source, demarcation and agreement", "description": "Ordered components, monuments or natural features, source survey or treaty, demarcation state and neighboring-party agreement.", "source_refs": [ "SRC-003", "SRC-008" ], "questions": [ { "id": "boundary-segment-point-source-demarcation-and-agreement-q01", "text": "What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for boundary segment, point, source, demarcation and agreement?", "kind": "composition", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "boundary-segment-point-source-demarcation-and-agreement-q02", "text": "Which register, government, statistical authority, source and evidence establishes boundary segment, point, source, demarcation and agreement, at what legal, observation and knowledge time, and for which recognition scope?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "recognition scope", "evidence" ] }, { "id": "boundary-segment-point-source-demarcation-and-agreement-q03", "text": "How may boundary segment, point, source, demarcation and agreement be validated, contested, corrected, superseded, retained or disclosed without erasing history or conflating hierarchy, geometry and authority?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "boundary-segment-point-source-demarcation-and-agreement-data", "name": "Boundary segment, point, source, demarcation and agreement data", "description": "Structured source-qualified data for boundary segment, point, source, demarcation and agreement.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "boundary-segment-point-source-demarcation-and-agreement-record", "name": "Boundary segment, point, source, demarcation and agreement record", "description": "Versioned evidence-bearing record for boundary segment, point, source, demarcation and agreement with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical administrative-area record", "official or statistical evidence reference" ], "serial": true, "identity_strategy": "Administrative-area identifier plus boundary-segment-point-source-demarcation-and-agreement assertion or event identifier; names, codes, geometry, dates and hashes never identify the unit alone.", "source_refs": [ "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "geometry-crs-topology-and-measures", "name": "Geometry, CRS, topology and measures", "description": "Coordinate semantics, special topology and measured extents.", "source_refs": [ "SRC-004", "SRC-005", "SRC-009" ], "findings": [ { "id": "geometry-crs-axis-order-dimensionality-precision-and-accuracy", "name": "Geometry, CRS, axis order, dimensionality, precision and accuracy", "description": "Geometry primitive, native CRS, axis order, coordinate epoch, dimensionality, transformation, precision, scale and accuracy.", "source_refs": [ "SRC-004", "SRC-005", "SRC-009" ], "questions": [ { "id": "geometry-crs-axis-order-dimensionality-precision-and-accuracy-q01", "text": "What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for geometry, crs, axis order, dimensionality, precision and accuracy?", "kind": "measurement", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "geometry-crs-axis-order-dimensionality-precision-and-accuracy-q02", "text": "Which register, government, statistical authority, source and evidence establishes geometry, crs, axis order, dimensionality, precision and accuracy, at what legal, observation and knowledge time, and for which recognition scope?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "recognition scope", "evidence" ] }, { "id": "geometry-crs-axis-order-dimensionality-precision-and-accuracy-q03", "text": "How may geometry, crs, axis order, dimensionality, precision and accuracy be validated, contested, corrected, superseded, retained or disclosed without erasing history or conflating hierarchy, geometry and authority?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "geometry-crs-axis-order-dimensionality-precision-and-accuracy-data", "name": "Geometry, CRS, axis order, dimensionality, precision and accuracy data", "description": "Structured source-qualified data for geometry, crs, axis order, dimensionality, precision and accuracy.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-009" ] } ], "artifacts": [ { "id": "geometry-crs-axis-order-dimensionality-precision-and-accuracy-record", "name": "Geometry, CRS, axis order, dimensionality, precision and accuracy record", "description": "Versioned evidence-bearing record for geometry, crs, axis order, dimensionality, precision and accuracy with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical administrative-area record", "official or statistical evidence reference" ], "serial": true, "identity_strategy": "Administrative-area identifier plus geometry-crs-axis-order-dimensionality-precision-and-accuracy assertion or event identifier; names, codes, geometry, dates and hashes never identify the unit alone.", "source_refs": [ "SRC-004", "SRC-005", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "area-coastline-enclave-exclave-hole-adjacency-and-topology", "name": "Area, coastline, enclave, exclave, hole, adjacency and topology", "description": "Official and calculated area, unit and method, coastline rule, parts, holes, enclaves, exclaves, neighbors, overlap and gap checks.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ], "questions": [ { "id": "area-coastline-enclave-exclave-hole-adjacency-and-topology-q01", "text": "What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for area, coastline, enclave, exclave, hole, adjacency and topology?", "kind": "spatial", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "area-coastline-enclave-exclave-hole-adjacency-and-topology-q02", "text": "Which register, government, statistical authority, source and evidence establishes area, coastline, enclave, exclave, hole, adjacency and topology, at what legal, observation and knowledge time, and for which recognition scope?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "recognition scope", "evidence" ] }, { "id": "area-coastline-enclave-exclave-hole-adjacency-and-topology-q03", "text": "How may area, coastline, enclave, exclave, hole, adjacency and topology be validated, contested, corrected, superseded, retained or disclosed without erasing history or conflating hierarchy, geometry and authority?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "area-coastline-enclave-exclave-hole-adjacency-and-topology-data", "name": "Area, coastline, enclave, exclave, hole, adjacency and topology data", "description": "Structured source-qualified data for area, coastline, enclave, exclave, hole, adjacency and topology.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "area-coastline-enclave-exclave-hole-adjacency-and-topology-record", "name": "Area, coastline, enclave, exclave, hole, adjacency and topology record", "description": "Versioned evidence-bearing record for area, coastline, enclave, exclave, hole, adjacency and topology with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical administrative-area record", "official or statistical evidence reference" ], "serial": true, "identity_strategy": "Administrative-area identifier plus area-coastline-enclave-exclave-hole-adjacency-and-topology assertion or event identifier; names, codes, geometry, dates and hashes never identify the unit alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "lifecycle-change-and-lineage", "name": "Lifecycle, change and lineage", "description": "Preserves creation, modification and replacement of administrative units.", "rationale": "Renaming may preserve identity, while split, merger, transfer or reclassification may create new units; jurisdictional law controls the distinction.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007", "SRC-008", "SRC-010" ], "layers": [ { "id": "state-and-bitemporal-effectivity", "name": "State and bitemporal effectivity", "description": "Current and historic state with separate legal and knowledge time.", "source_refs": [ "SRC-003", "SRC-010" ], "findings": [ { "id": "proposed-active-suspended-disputed-superseded-and-abolished-state", "name": "Proposed, active, suspended, disputed, superseded and abolished state", "description": "Profile-qualified state, deciding authority, reason, effective interval, publication, contest and observation status.", "source_refs": [ "SRC-003", "SRC-008" ], "questions": [ { "id": "proposed-active-suspended-disputed-superseded-and-abolished-state-q01", "text": "What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for proposed, active, suspended, disputed, superseded and abolished state?", "kind": "state", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "proposed-active-suspended-disputed-superseded-and-abolished-state-q02", "text": "Which register, government, statistical authority, source and evidence establishes proposed, active, suspended, disputed, superseded and abolished state, at what legal, observation and knowledge time, and for which recognition scope?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "recognition scope", "evidence" ] }, { "id": "proposed-active-suspended-disputed-superseded-and-abolished-state-q03", "text": "How may proposed, active, suspended, disputed, superseded and abolished state be validated, contested, corrected, superseded, retained or disclosed without erasing history or conflating hierarchy, geometry and authority?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "proposed-active-suspended-disputed-superseded-and-abolished-state-data", "name": "Proposed, active, suspended, disputed, superseded and abolished state data", "description": "Structured source-qualified data for proposed, active, suspended, disputed, superseded and abolished state.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "proposed-active-suspended-disputed-superseded-and-abolished-state-record", "name": "Proposed, active, suspended, disputed, superseded and abolished state record", "description": "Versioned evidence-bearing record for proposed, active, suspended, disputed, superseded and abolished state with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical administrative-area record", "official or statistical evidence reference" ], "serial": true, "identity_strategy": "Administrative-area identifier plus proposed-active-suspended-disputed-superseded-and-abolished-state assertion or event identifier; names, codes, geometry, dates and hashes never identify the unit alone.", "source_refs": [ "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "decision-legal-effect-observation-publication-and-knowledge-time", "name": "Decision, legal-effect, observation, publication and knowledge time", "description": "Distinct time axes, precision, timezone, retroactive effect, source revision and later correction.", "source_refs": [ "SRC-003", "SRC-008", "SRC-010" ], "questions": [ { "id": "decision-legal-effect-observation-publication-and-knowledge-time-q01", "text": "What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for decision, legal-effect, observation, publication and knowledge time?", "kind": "temporal", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "decision-legal-effect-observation-publication-and-knowledge-time-q02", "text": "Which register, government, statistical authority, source and evidence establishes decision, legal-effect, observation, publication and knowledge time, at what legal, observation and knowledge time, and for which recognition scope?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "recognition scope", "evidence" ] }, { "id": "decision-legal-effect-observation-publication-and-knowledge-time-q03", "text": "How may decision, legal-effect, observation, publication and knowledge time be validated, contested, corrected, superseded, retained or disclosed without erasing history or conflating hierarchy, geometry and authority?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "decision-legal-effect-observation-publication-and-knowledge-time-data", "name": "Decision, legal-effect, observation, publication and knowledge time data", "description": "Structured source-qualified data for decision, legal-effect, observation, publication and knowledge time.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-008", "SRC-010" ] } ], "artifacts": [ { "id": "decision-legal-effect-observation-publication-and-knowledge-time-record", "name": "Decision, legal-effect, observation, publication and knowledge time record", "description": "Versioned evidence-bearing record for decision, legal-effect, observation, publication and knowledge time with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical administrative-area record", "official or statistical evidence reference" ], "serial": true, "identity_strategy": "Administrative-area identifier plus decision-legal-effect-observation-publication-and-knowledge-time assertion or event identifier; names, codes, geometry, dates and hashes never identify the unit alone.", "source_refs": [ "SRC-003", "SRC-008", "SRC-010" ] } ], "inline_only_rationale": null } ] }, { "id": "territorial-and-classification-change", "name": "Territorial and classification change", "description": "Authorized transformations and identity consequences.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007", "SRC-008" ], "findings": [ { "id": "creation-split-merger-transfer-annexation-and-boundary-adjustment", "name": "Creation, split, merger, transfer, annexation and boundary adjustment", "description": "Change case, parties, instrument, predecessor and successor units, transferred extent, population reference, approval and effect.", "source_refs": [ "SRC-003", "SRC-008" ], "questions": [ { "id": "creation-split-merger-transfer-annexation-and-boundary-adjustment-q01", "text": "What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for creation, split, merger, transfer, annexation and boundary adjustment?", "kind": "lifecycle", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "creation-split-merger-transfer-annexation-and-boundary-adjustment-q02", "text": "Which register, government, statistical authority, source and evidence establishes creation, split, merger, transfer, annexation and boundary adjustment, at what legal, observation and knowledge time, and for which recognition scope?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "recognition scope", "evidence" ] }, { "id": "creation-split-merger-transfer-annexation-and-boundary-adjustment-q03", "text": "How may creation, split, merger, transfer, annexation and boundary adjustment be validated, contested, corrected, superseded, retained or disclosed without erasing history or conflating hierarchy, geometry and authority?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "creation-split-merger-transfer-annexation-and-boundary-adjustment-data", "name": "Creation, split, merger, transfer, annexation and boundary adjustment data", "description": "Structured source-qualified data for creation, split, merger, transfer, annexation and boundary adjustment.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "creation-split-merger-transfer-annexation-and-boundary-adjustment-record", "name": "Creation, split, merger, transfer, annexation and boundary adjustment record", "description": "Versioned evidence-bearing record for creation, split, merger, transfer, annexation and boundary adjustment with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical administrative-area record", "official or statistical evidence reference" ], "serial": true, "identity_strategy": "Administrative-area identifier plus creation-split-merger-transfer-annexation-and-boundary-adjustment assertion or event identifier; names, codes, geometry, dates and hashes never identify the unit alone.", "source_refs": [ "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "renaming-recoding-reclassification-successor-and-tombstone", "name": "Renaming, recoding, reclassification, successor and tombstone", "description": "Whether identity persists, code and name changes, old-to-new mappings, successor proportions and durable historic resolution.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007" ], "questions": [ { "id": "renaming-recoding-reclassification-successor-and-tombstone-q01", "text": "What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for renaming, recoding, reclassification, successor and tombstone?", "kind": "lifecycle", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "renaming-recoding-reclassification-successor-and-tombstone-q02", "text": "Which register, government, statistical authority, source and evidence establishes renaming, recoding, reclassification, successor and tombstone, at what legal, observation and knowledge time, and for which recognition scope?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "recognition scope", "evidence" ] }, { "id": "renaming-recoding-reclassification-successor-and-tombstone-q03", "text": "How may renaming, recoding, reclassification, successor and tombstone be validated, contested, corrected, superseded, retained or disclosed without erasing history or conflating hierarchy, geometry and authority?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "renaming-recoding-reclassification-successor-and-tombstone-data", "name": "Renaming, recoding, reclassification, successor and tombstone data", "description": "Structured source-qualified data for renaming, recoding, reclassification, successor and tombstone.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007" ] } ], "artifacts": [ { "id": "renaming-recoding-reclassification-successor-and-tombstone-record", "name": "Renaming, recoding, reclassification, successor and tombstone record", "description": "Versioned evidence-bearing record for renaming, recoding, reclassification, successor and tombstone with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical administrative-area record", "official or statistical evidence reference" ], "serial": true, "identity_strategy": "Administrative-area identifier plus renaming-recoding-reclassification-successor-and-tombstone assertion or event identifier; names, codes, geometry, dates and hashes never identify the unit alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "place-context-statistics-and-disputes", "name": "Place context, statistics and disputes", "description": "Links administrative units to places, functional zones, observations and recognition disputes without importing their masters.", "rationale": "Population, address coverage, postal service, elections and de facto control describe contexts that may not share the administrative boundary.", "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-007", "SRC-008" ], "layers": [ { "id": "places-zones-and-functional-context", "name": "Places, zones and functional context", "description": "External settlement and service-area relations.", "source_refs": [ "SRC-003", "SRC-006" ], "findings": [ { "id": "settlement-locality-address-parcel-and-building-reference", "name": "Settlement, locality, address, parcel and building reference", "description": "Typed external place and feature links, relation basis, containment or service semantics, time and uncertainty.", "source_refs": [ "SRC-003", "SRC-006" ], "questions": [ { "id": "settlement-locality-address-parcel-and-building-reference-q01", "text": "What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for settlement, locality, address, parcel and building reference?", "kind": "relationship", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "settlement-locality-address-parcel-and-building-reference-q02", "text": "Which register, government, statistical authority, source and evidence establishes settlement, locality, address, parcel and building reference, at what legal, observation and knowledge time, and for which recognition scope?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "recognition scope", "evidence" ] }, { "id": "settlement-locality-address-parcel-and-building-reference-q03", "text": "How may settlement, locality, address, parcel and building reference be validated, contested, corrected, superseded, retained or disclosed without erasing history or conflating hierarchy, geometry and authority?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "settlement-locality-address-parcel-and-building-reference-data", "name": "Settlement, locality, address, parcel and building reference data", "description": "Structured source-qualified data for settlement, locality, address, parcel and building reference.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "settlement-locality-address-parcel-and-building-reference-record", "name": "Settlement, locality, address, parcel and building reference record", "description": "Versioned evidence-bearing record for settlement, locality, address, parcel and building reference with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical administrative-area record", "official or statistical evidence reference" ], "serial": true, "identity_strategy": "Administrative-area identifier plus settlement-locality-address-parcel-and-building-reference assertion or event identifier; names, codes, geometry, dates and hashes never identify the unit alone.", "source_refs": [ "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "postal-electoral-service-planning-timezone-and-jurisdiction-reference", "name": "Postal, electoral, service, planning, timezone and jurisdiction reference", "description": "External zones and legal or functional jurisdictions with independent geometry, authority and lifecycle.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ], "questions": [ { "id": "postal-electoral-service-planning-timezone-and-jurisdiction-reference-q01", "text": "What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for postal, electoral, service, planning, timezone and jurisdiction reference?", "kind": "relationship", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "postal-electoral-service-planning-timezone-and-jurisdiction-reference-q02", "text": "Which register, government, statistical authority, source and evidence establishes postal, electoral, service, planning, timezone and jurisdiction reference, at what legal, observation and knowledge time, and for which recognition scope?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "recognition scope", "evidence" ] }, { "id": "postal-electoral-service-planning-timezone-and-jurisdiction-reference-q03", "text": "How may postal, electoral, service, planning, timezone and jurisdiction reference be validated, contested, corrected, superseded, retained or disclosed without erasing history or conflating hierarchy, geometry and authority?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "postal-electoral-service-planning-timezone-and-jurisdiction-reference-data", "name": "Postal, electoral, service, planning, timezone and jurisdiction reference data", "description": "Structured source-qualified data for postal, electoral, service, planning, timezone and jurisdiction reference.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "postal-electoral-service-planning-timezone-and-jurisdiction-reference-record", "name": "Postal, electoral, service, planning, timezone and jurisdiction reference record", "description": "Versioned evidence-bearing record for postal, electoral, service, planning, timezone and jurisdiction reference with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical administrative-area record", "official or statistical evidence reference" ], "serial": true, "identity_strategy": "Administrative-area identifier plus postal-electoral-service-planning-timezone-and-jurisdiction-reference assertion or event identifier; names, codes, geometry, dates and hashes never identify the unit alone.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "statistics-observations-and-recognition-conflict", "name": "Statistics, observations and recognition conflict", "description": "Time-qualified measures and competing sovereignty or status claims.", "source_refs": [ "SRC-002", "SRC-007", "SRC-008" ], "findings": [ { "id": "population-area-statistic-indicator-reference-time-and-method", "name": "Population, area, statistic, indicator, reference time and method", "description": "External observation or dataset, population concept, reference date, geography version, method, estimate status and uncertainty.", "source_refs": [ "SRC-002", "SRC-007" ], "questions": [ { "id": "population-area-statistic-indicator-reference-time-and-method-q01", "text": "What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for population, area, statistic, indicator, reference time and method?", "kind": "measurement", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "population-area-statistic-indicator-reference-time-and-method-q02", "text": "Which register, government, statistical authority, source and evidence establishes population, area, statistic, indicator, reference time and method, at what legal, observation and knowledge time, and for which recognition scope?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "recognition scope", "evidence" ] }, { "id": "population-area-statistic-indicator-reference-time-and-method-q03", "text": "How may population, area, statistic, indicator, reference time and method be validated, contested, corrected, superseded, retained or disclosed without erasing history or conflating hierarchy, geometry and authority?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "population-area-statistic-indicator-reference-time-and-method-data", "name": "Population, area, statistic, indicator, reference time and method data", "description": "Structured source-qualified data for population, area, statistic, indicator, reference time and method.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-007" ] } ], "artifacts": [ { "id": "population-area-statistic-indicator-reference-time-and-method-record", "name": "Population, area, statistic, indicator, reference time and method record", "description": "Versioned evidence-bearing record for population, area, statistic, indicator, reference time and method with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical administrative-area record", "official or statistical evidence reference" ], "serial": true, "identity_strategy": "Administrative-area identifier plus population-area-statistic-indicator-reference-time-and-method assertion or event identifier; names, codes, geometry, dates and hashes never identify the unit alone.", "source_refs": [ "SRC-002", "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "territorial-claim-recognition-status-dispute-and-neutral-display", "name": "Territorial claim, recognition status, dispute and neutral display", "description": "Claimant, claimed extent, basis, recognizing party, scope, valid time, dispute record and purpose-specific neutral-display rule.", "source_refs": [ "SRC-002", "SRC-008" ], "questions": [ { "id": "territorial-claim-recognition-status-dispute-and-neutral-display-q01", "text": "What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for territorial claim, recognition status, dispute and neutral display?", "kind": "provenance", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "territorial-claim-recognition-status-dispute-and-neutral-display-q02", "text": "Which register, government, statistical authority, source and evidence establishes territorial claim, recognition status, dispute and neutral display, at what legal, observation and knowledge time, and for which recognition scope?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "recognition scope", "evidence" ] }, { "id": "territorial-claim-recognition-status-dispute-and-neutral-display-q03", "text": "How may territorial claim, recognition status, dispute and neutral display be validated, contested, corrected, superseded, retained or disclosed without erasing history or conflating hierarchy, geometry and authority?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "territorial-claim-recognition-status-dispute-and-neutral-display-data", "name": "Territorial claim, recognition status, dispute and neutral display data", "description": "Structured source-qualified data for territorial claim, recognition status, dispute and neutral display.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-008" ] } ], "artifacts": [ { "id": "territorial-claim-recognition-status-dispute-and-neutral-display-record", "name": "Territorial claim, recognition status, dispute and neutral display record", "description": "Versioned evidence-bearing record for territorial claim, recognition status, dispute and neutral display with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical administrative-area record", "official or statistical evidence reference" ], "serial": true, "identity_strategy": "Administrative-area identifier plus territorial-claim-recognition-status-dispute-and-neutral-display assertion or event identifier; names, codes, geometry, dates and hashes never identify the unit alone.", "source_refs": [ "SRC-002", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "interoperability-governance-and-agent-operations", "name": "Interoperability, governance and agent operations", "description": "Controls mappings, provenance, disclosure and safe automated maintenance.", "rationale": "Publishing one simplified hierarchy or polygon can erase disputed status, code edition, legal effect and non-administrative mappings.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010" ], "layers": [ { "id": "classifiers-projections-and-access", "name": "Classifiers, projections and access", "description": "Versioned code and geospatial projections with purpose controls.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ], "findings": [ { "id": "iso-m49-nuts-salb-inspire-gml-geosparql-and-geojson-projection", "name": "ISO, M49, NUTS, SALB, INSPIRE, GML, GeoSPARQL and GeoJSON projection", "description": "Source and target versions, code and geometry mappings, hierarchy scope, transformed fields, omissions and round-trip limits.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ], "questions": [ { "id": "iso-m49-nuts-salb-inspire-gml-geosparql-and-geojson-projection-q01", "text": "What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for iso, m49, nuts, salb, inspire, gml, geosparql and geojson projection?", "kind": "interoperability", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "iso-m49-nuts-salb-inspire-gml-geosparql-and-geojson-projection-q02", "text": "Which register, government, statistical authority, source and evidence establishes iso, m49, nuts, salb, inspire, gml, geosparql and geojson projection, at what legal, observation and knowledge time, and for which recognition scope?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "recognition scope", "evidence" ] }, { "id": "iso-m49-nuts-salb-inspire-gml-geosparql-and-geojson-projection-q03", "text": "How may iso, m49, nuts, salb, inspire, gml, geosparql and geojson projection be validated, contested, corrected, superseded, retained or disclosed without erasing history or conflating hierarchy, geometry and authority?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "iso-m49-nuts-salb-inspire-gml-geosparql-and-geojson-projection-data", "name": "ISO, M49, NUTS, SALB, INSPIRE, GML, GeoSPARQL and GeoJSON projection data", "description": "Structured source-qualified data for iso, m49, nuts, salb, inspire, gml, geosparql and geojson projection.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ] } ], "artifacts": [ { "id": "iso-m49-nuts-salb-inspire-gml-geosparql-and-geojson-projection-record", "name": "ISO, M49, NUTS, SALB, INSPIRE, GML, GeoSPARQL and GeoJSON projection record", "description": "Versioned evidence-bearing record for iso, m49, nuts, salb, inspire, gml, geosparql and geojson projection with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical administrative-area record", "official or statistical evidence reference" ], "serial": true, "identity_strategy": "Administrative-area identifier plus iso-m49-nuts-salb-inspire-gml-geosparql-and-geojson-projection assertion or event identifier; names, codes, geometry, dates and hashes never identify the unit alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "public-map-statistical-restricted-and-dispute-sensitive-view", "name": "Public map, statistical, restricted and dispute-sensitive view", "description": "Purpose, audience, boundary role, name and code policy, precision, masking, attribution, expiry and inference risk.", "source_refs": [ "SRC-002", "SRC-003", "SRC-008" ], "questions": [ { "id": "public-map-statistical-restricted-and-dispute-sensitive-view-q01", "text": "What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for public map, statistical, restricted and dispute-sensitive view?", "kind": "access", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "public-map-statistical-restricted-and-dispute-sensitive-view-q02", "text": "Which register, government, statistical authority, source and evidence establishes public map, statistical, restricted and dispute-sensitive view, at what legal, observation and knowledge time, and for which recognition scope?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "recognition scope", "evidence" ] }, { "id": "public-map-statistical-restricted-and-dispute-sensitive-view-q03", "text": "How may public map, statistical, restricted and dispute-sensitive view be validated, contested, corrected, superseded, retained or disclosed without erasing history or conflating hierarchy, geometry and authority?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "public-map-statistical-restricted-and-dispute-sensitive-view-data", "name": "Public map, statistical, restricted and dispute-sensitive view data", "description": "Structured source-qualified data for public map, statistical, restricted and dispute-sensitive view.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-008" ] } ], "artifacts": [ { "id": "public-map-statistical-restricted-and-dispute-sensitive-view-record", "name": "Public map, statistical, restricted and dispute-sensitive view record", "description": "Versioned evidence-bearing record for public map, statistical, restricted and dispute-sensitive view with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical administrative-area record", "official or statistical evidence reference" ], "serial": true, "identity_strategy": "Administrative-area identifier plus public-map-statistical-restricted-and-dispute-sensitive-view assertion or event identifier; names, codes, geometry, dates and hashes never identify the unit alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "safe-agent-control-and-validation", "name": "Safe agent control and validation", "description": "Authorized operations, invariants, concurrency and audit.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-010" ], "findings": [ { "id": "agent-operation-authority-purpose-preconditions-and-confirmation", "name": "Agent operation authority, purpose, preconditions and confirmation", "description": "Classifies register, rename, recode, reparent, change boundary, merge, split, disclose and retire operations as autonomous, propose, confirm or forbidden.", "source_refs": [ "SRC-003" ], "questions": [ { "id": "agent-operation-authority-purpose-preconditions-and-confirmation-q01", "text": "What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for agent operation authority, purpose, preconditions and confirmation?", "kind": "security", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "agent-operation-authority-purpose-preconditions-and-confirmation-q02", "text": "Which register, government, statistical authority, source and evidence establishes agent operation authority, purpose, preconditions and confirmation, at what legal, observation and knowledge time, and for which recognition scope?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "recognition scope", "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 history or conflating hierarchy, geometry and authority?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "agent-operation-authority-purpose-preconditions-and-confirmation-data", "name": "Agent operation authority, purpose, preconditions and confirmation data", "description": "Structured source-qualified data for agent operation authority, purpose, preconditions and confirmation.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "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 authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical administrative-area record", "official or statistical evidence reference" ], "serial": true, "identity_strategy": "Administrative-area identifier plus agent-operation-authority-purpose-preconditions-and-confirmation assertion or event identifier; names, codes, geometry, dates and hashes never identify the unit alone.", "source_refs": [ "SRC-003" ] } ], "inline_only_rationale": null }, { "id": "prewrite-postwrite-validation-conflict-concurrency-and-recovery", "name": "Pre-write and post-write validation, conflict, concurrency and recovery", "description": "Identity, code, authority, hierarchy, CRS, topology, legal time, lineage, dispute, access and stale-head checks with rollback evidence.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-010" ], "questions": [ { "id": "prewrite-postwrite-validation-conflict-concurrency-and-recovery-q01", "text": "What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for pre-write and post-write validation, conflict, concurrency and recovery?", "kind": "validation", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "prewrite-postwrite-validation-conflict-concurrency-and-recovery-q02", "text": "Which register, government, statistical authority, source and evidence establishes pre-write and post-write validation, conflict, concurrency and recovery, at what legal, observation and knowledge time, and for which recognition scope?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "recognition scope", "evidence" ] }, { "id": "prewrite-postwrite-validation-conflict-concurrency-and-recovery-q03", "text": "How may pre-write and post-write validation, conflict, concurrency and recovery be validated, contested, corrected, superseded, retained or disclosed without erasing history or conflating hierarchy, geometry and authority?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "prewrite-postwrite-validation-conflict-concurrency-and-recovery-data", "name": "Pre-write and post-write validation, conflict, concurrency and recovery data", "description": "Structured source-qualified data for pre-write and post-write validation, conflict, concurrency and recovery.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-010" ] } ], "artifacts": [ { "id": "prewrite-postwrite-validation-conflict-concurrency-and-recovery-record", "name": "Pre-write and post-write validation, conflict, concurrency and recovery record", "description": "Versioned evidence-bearing record for pre-write and post-write validation, conflict, concurrency and recovery with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical administrative-area record", "official or statistical evidence reference" ], "serial": true, "identity_strategy": "Administrative-area identifier plus prewrite-postwrite-validation-conflict-concurrency-and-recovery assertion or event identifier; names, codes, geometry, dates and hashes never identify the unit alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-010" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-administrative-area", "name": "Register administrative area", "description": "Create the master identity, unit type, register, authority and initial effective state.", "inputs": [ "register", "identifier", "class", "authority", "instrument" ], "outputs": [ "registered area revision" ], "preconditions": [ "authority and uniqueness validate" ], "effects": [ "unit becomes resolvable with provenance" ], "source_refs": [ "SRC-003", "SRC-006" ] }, { "id": "bind-code-or-name", "name": "Bind code or name", "description": "Append a versioned code-system binding or official, historic or language-qualified name.", "inputs": [ "area", "code or name", "issuer", "interval" ], "outputs": [ "code or name assertion" ], "preconditions": [ "scheme, language and authority validate" ], "effects": [ "aliases remain time-qualified and old references resolve" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "bind-hierarchy", "name": "Bind administrative hierarchy", "description": "Append a typed parent, child, containment or statistical-grouping relation.", "inputs": [ "area", "related area", "relation kind", "authority" ], "outputs": [ "hierarchy revision" ], "preconditions": [ "levels, cycles and time validate" ], "effects": [ "administrative and spatial relations remain separate" ], "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] }, { "id": "attach-boundary-assertion", "name": "Attach boundary assertion", "description": "Append an official, statistical, claimed, disputed or de facto geometry with source and recognition scope.", "inputs": [ "area", "geometry", "role", "source", "CRS" ], "outputs": [ "boundary assertion" ], "preconditions": [ "CRS, authority and role validate" ], "effects": [ "competing boundaries remain attributable" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-008" ] }, { "id": "validate-geometry-and-topology", "name": "Validate geometry and topology", "description": "Check validity, CRS, parts, holes, adjacency, overlaps, gaps and measured area.", "inputs": [ "area revision", "profile", "tolerance" ], "outputs": [ "validation report" ], "preconditions": [ "boundary role and CRS are known" ], "effects": [ "defects and uncertainty become explicit" ], "source_refs": [ "SRC-004", "SRC-005" ] }, { "id": "propose-territorial-change", "name": "Propose territorial change", "description": "Create a case for split, merger, transfer, annexation or boundary adjustment.", "inputs": [ "areas", "instrument", "proposed extents", "authority" ], "outputs": [ "proposed lineage graph" ], "preconditions": [ "current heads and affected claims resolve" ], "effects": [ "proposal stays non-effective pending competent decision" ], "source_refs": [ "SRC-003", "SRC-008" ] }, { "id": "register-change-or-reclassification", "name": "Register change or reclassification", "description": "Apply an authorized territorial, hierarchy, name, code or class change and preserve successors.", "inputs": [ "change case", "decision", "effective time" ], "outputs": [ "successor revisions and events" ], "preconditions": [ "authority, topology and lineage validate" ], "effects": [ "new state takes effect without erasing history" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-010" ] }, { "id": "record-recognition-or-dispute", "name": "Record recognition or dispute", "description": "Append a claimant, recognizing party, claimed extent, basis and neutral-display rule.", "inputs": [ "area", "claim or dispute", "party", "scope" ], "outputs": [ "recognition assertion" ], "preconditions": [ "sources and party authority are known" ], "effects": [ "conflict remains visible without choosing universal sovereignty" ], "source_refs": [ "SRC-002", "SRC-008" ] }, { "id": "issue-administrative-area-view", "name": "Issue administrative-area view", "description": "Create a purpose-bound code, hierarchy, statistical or map projection with declared loss.", "inputs": [ "area revision", "target profile", "purpose" ], "outputs": [ "validated projection" ], "preconditions": [ "versions, access and dispute policy validate" ], "effects": [ "projection links source digest and omissions" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-009" ] }, { "id": "retire-administrative-area", "name": "Retire administrative area", "description": "Abolish or supersede a unit while preserving code, name, boundary and lineage tombstones.", "inputs": [ "area", "authority", "reason", "successors" ], "outputs": [ "retirement event" ], "preconditions": [ "legal effect and successors resolve" ], "effects": [ "future active use is blocked while history remains citable" ], "source_refs": [ "SRC-003", "SRC-008" ] } ], "composition": [ { "target": "Government, Jurisdiction, Instrument, Place, Address, Zone, Parcel, Statistic and Dispute models", "relation": "REFERENCE", "purpose": "Connect administrative territory to external legal, organizational, spatial, observational and dispute masters.", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-006", "SRC-007", "SRC-008" ] }, { "target": "ISO 3166 and ISO 19112", "relation": "ALIGN", "purpose": "Bind versioned country or subdivision codes and geographic-identifier schemes without replacing the master identity.", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "target": "UN M49 and SALB", "relation": "ALIGN", "purpose": "Project statistical area codes and time-aware first or second administrative boundary references.", "required": false, "source_refs": [ "SRC-002", "SRC-008" ] }, { "target": "INSPIRE Administrative Units and NUTS", "relation": "ALIGN", "purpose": "Project European administrative and statistical unit identifiers, levels, names, geometry and lifecycle.", "required": false, "source_refs": [ "SRC-003", "SRC-007" ] }, { "target": "GML, GeoSPARQL and GeoJSON", "relation": "ALIGN", "purpose": "Publish geometry and semantic-spatial views with CRS, topology, dispute and mapping-loss declarations.", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-009" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Dimension identity, owner, administrative-register authority, boundary steward and namespace", "Area, government, instrument, code-list, boundary, place, zone, statistic, dispute and lifecycle registries", "Master-system mappings for area, code, hierarchy, boundary assertion, change case and event identifiers", "Code, naming, hierarchy, CRS, topology, recognition, dispute, access, retention and agent-operation policies" ], "namespace_guidance": "Mint administrative-area and assertion identifiers only when no authoritative register identity exists; keep governments, instruments, settlements, addresses, postal and electoral zones, parcels, statistics and disputes as typed references.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md", "Dimension-local area, code, name, hierarchy, boundary, lineage and recognition registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by authoritative administrative-unit identifier and register, never by name, ISO or statistical code, parent, government, geometry, population, date or hash.", "Keep administrative hierarchy, geometric containment, statistical grouping, jurisdiction and governmental competence distinct." ], "patch_rules": [ "Extensions declare unit profile, target finding, source, authority, code-list versions, CRS, recognition scope and interoperability impact.", "Identity, authority, hierarchy, boundary, legal-effect or lifecycle semantic changes require a successor version, migration map and continued resolution of prior records." ], "compatibility_rules": [ "Unknown additive fields may be ignored only when identity, codes, unit class, authority, hierarchy type, boundary role, CRS, legal effect, recognition and lineage remain intact.", "Every code, hierarchy and geometry projection pins versions and states transformation, omission and round-trip limits." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier for the administrative unit, qualified by register and issuing authority.", "Governed globally resolvable area 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 decision, legal-effect, observation, publication, knowledge and ingestion times.", "serial_naming_rule": "Use {area-id}--{artifact-kind}--{assertion-or-event-id}; never use a name, code, geometry, date or hash alone.", "integrity_rule": "Store digest, media type, issuer, source and profile versions, CRS, authority, recognition scope, valid and knowledge times, quality, licence and access marking." }, "policies": [ "Only a competent register authority may create or change canonical administrative-unit identity and legal-effect state.", "Code, name, geometry, population, postal coverage and government seat never alone prove current administrative identity or authority.", "Official, statistical, claimed, disputed and de facto boundary assertions remain separately attributable.", "Agents may validate and propose; legal change, universal-recognition claims, dispute suppression and wider disclosure require accountable authority." ], "crud": { "read": [ "Resolve Dimension, register, purpose, code editions, hierarchy type, valid and knowledge time, boundary role, CRS and recognition scope." ], "create": [ "Create identity, authority, unit class, instrument, state, source and explicit unknowns before codes, hierarchy or geometry." ], "update": [ "Append assertion or event with authority, reason, time, evidence and validation; never overwrite cited history or competing claims." ], "delete": [ "Apply legal hold and retention; prefer abolition or tombstone and never cascade to governments, places, statistics or disputes." ] }, "roles": [ { "name": "Administrative-register authority", "responsibilities": [ "Own canonical unit identity, class, hierarchy and legal-effect lifecycle." ] }, { "name": "Boundary authority", "responsibilities": [ "Provide authoritative geometry, demarcation and quality evidence." ] }, { "name": "Code-list authority", "responsibilities": [ "Issue versioned codes and preserve retired-code mappings." ] }, { "name": "Statistical authority", "responsibilities": [ "Own statistical groupings, observations, reference geographies and methods." ] }, { "name": "Recognition and dispute steward", "responsibilities": [ "Preserve claims, recognition scope and neutral-display rules without erasure." ] }, { "name": "Geospatial quality steward", "responsibilities": [ "Validate CRS, topology, transformations and measures." ] }, { "name": "Access and records steward", "responsibilities": [ "Apply disclosure, licence, retention and audit policy." ] } ], "access": { "default_rule": "Deny mutation and sensitive boundary or authority disclosure unless register, role, purpose and field policy grant it; expose the minimum necessary precision and claim context.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Statutory, judicial, humanitarian or emergency access cites authority and remains purpose-bound, attributable and reviewable." ], "audit_requirements": [ "Log actor, agent, role, purpose, area, action, policy, RFC 3339 time, authority, recognition scope, affected fields and outcome." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read Dimension area-register, code, hierarchy, boundary, CRS, recognition, dispute, access and retention policies.", "Read this model and linked government, instrument, place, zone, parcel, statistic and dispute models before mutation." ] } }, "coverage": { "claim": "A source-grounded reviewable draft of an administrative area across ISO 3166 and ISO 19112, UN M49 and SALB, INSPIRE Administrative Units, NUTS, OGC GeoSPARQL and GML, GeoJSON and RFC 3339, without universal sovereignty, jurisdictional legal-effect or certified crosswalk claims.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Register-qualified identity, code bindings, unit class and names are explicit." }, { "dimension": "classification and definition", "status": "covered", "notes": "Administrative and statistical types, levels and schemes are versioned." }, { "dimension": "direct properties", "status": "covered", "notes": "Names, codes, hierarchy, boundary geometry, CRS, area and topology are first-class." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Official, statistical, claimed, disputed and de facto sources and confidence are covered." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Register, name, code, bind, map, change, dispute, project and retire operations are governed." }, { "dimension": "composition", "status": "covered", "notes": "Governments, laws, places, zones, parcels, statistics and disputes retain external masters." }, { "dimension": "lifecycle", "status": "covered", "notes": "Creation, split, merger, transfer, annexation, renaming, recoding, reclassification and abolition preserve history." }, { "dimension": "relationships", "status": "covered", "notes": "Administrative parentage, spatial containment, statistical grouping and competence are distinct." }, { "dimension": "temporal", "status": "covered", "notes": "Decision, legal-effect, observation, publication, knowledge and ingestion times remain distinct." }, { "dimension": "spatial", "status": "covered", "notes": "Boundary roles, CRS, dimensionality, accuracy, topology, enclaves and exclaves are covered." }, { "dimension": "provenance", "status": "covered", "notes": "Authorities, instruments, code lists, geometry sources, transformations and claims remain attributable." }, { "dimension": "ownership and stewardship", "status": "covered", "notes": "Register, boundary, code, government, statistical and dispute masters remain separate." }, { "dimension": "validation and quality", "status": "covered", "notes": "Identity, code, hierarchy cycles, CRS, topology, legal time, lineage and stale-head checks are explicit." }, { "dimension": "access and privacy", "status": "covered", "notes": "Purpose views, dispute sensitivity, coordinate precision and inference risk are covered." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Historic codes, names, geometries, disputes, successor lineage and tombstones are preserved." }, { "dimension": "interoperability", "status": "covered", "notes": "ISO 3166, UN M49, NUTS, SALB, INSPIRE, GML, GeoSPARQL and GeoJSON are loss-aware." } ], "known_omissions": [ "No independent Claude or Grok result was available; later administrative, geopolitical and geospatial review is required before canonical promotion.", "Jurisdiction-specific local-government law, sovereignty, indigenous and customary territory, maritime, condominium, historical and conflict-sensitive profiles require specialist review.", "The frozen relation ledger contains no approved WM-PLC-004 rows; composition targets remain draft.", "Certified ISO, M49, NUTS, SALB, INSPIRE, GML, GeoSPARQL and GeoJSON crosswalks and conformance fixtures remain future work." ], "conflicts": [ "Administrative hierarchy, geometric containment, statistical grouping and governmental jurisdiction may disagree.", "Official, claimed, disputed, de facto and statistical boundaries may all be legitimate assertions for different purposes.", "A rename or recode may preserve identity in one jurisdiction while a reclassification or transfer may create a successor in another." ], "regional_assumptions": [ "INSPIRE and NUTS are European profiles and do not define universal administrative law.", "ISO 3166 and UN M49 provide code and statistical schemes and do not settle sovereignty or boundary disputes.", "SALB and geospatial standards support exchange but do not create legal effect for a national register." ], "adversarial_checks": [ "Reject identity from a name, ISO code, map polygon or government name alone.", "Reject hierarchy inferred from geometry containment or statistical grouping without explicit relation type.", "Reject a disputed or de facto line represented as universally recognized official boundary.", "Reject lifecycle change without instrument, authority, effective time and predecessor-successor mapping.", "Reject agent legal change, dispute suppression or universal-recognition claim without accountable confirmation." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "entity", "status": "accepted as a governed administrative or official statistical territorial unit", "rationale": "The unit owns register-qualified identity, codes, names, class, authority links, hierarchy, boundary assertions and lifecycle. Governments, jurisdictions, places, zones, parcels, statistics and disputes remain external masters." }, "decisions": [ { "concept": "Administrative-area identity", "disposition": "accepted as register-qualified", "rationale": "Names, ISO or statistical codes, parent, government and geometry are mutable or purpose-specific and cannot replace the authoritative identifier." }, { "concept": "Area versus government and jurisdiction", "disposition": "accepted as separate models", "rationale": "The area is territorial; a government is an organization and jurisdiction is a competence relation whose extent and time may differ." }, { "concept": "Hierarchy semantics", "disposition": "accepted as multiple typed relations", "rationale": "Administrative parentage, geometric containment, statistical grouping and governmental competence can diverge and must not be inferred from one another." }, { "concept": "Boundary assertions", "disposition": "accepted as parallel source-qualified claims", "rationale": "Official, statistical, claimed, disputed and de facto extents remain separately attributable by authority, recognition audience and time." }, { "concept": "Codes and names", "disposition": "accepted as versioned aliases", "rationale": "Every code and name pins scheme or language, issuer, edition and validity and preserves deprecated-to-successor mappings." }, { "concept": "Lifecycle and lineage", "disposition": "accepted as jurisdiction-profiled successor graph", "rationale": "Splits, mergers, transfers, annexations, renaming, recoding and reclassification record whether identity persists and preserve predecessor history." }, { "concept": "Sovereignty and recognition", "disposition": "no universal adjudication", "rationale": "The model records claimant, recognizing party, scope, basis and disputed extent but cannot decide universally valid sovereignty." }, { "concept": "Interoperability", "disposition": "accepted as loss-aware projections", "rationale": "ISO, UN, European and OGC schemes serve different purposes, so each mapping pins versions and discloses hierarchy, geometry, recognition and round-trip loss." }, { "concept": "Approved registry composition", "disposition": "held pending relation governance", "rationale": "The approved relation ledger contains no WM-PLC-004 rows, so proposed links to governments, jurisdictions, places, zones, parcels, statistics and disputes 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-PLC-004 rows, so all proposed sibling composition remains draft.", "Jurisdiction-specific local-government law, sovereignty, indigenous and customary territory, maritime, historical and conflict-sensitive profiles require specialist review.", "Certified ISO 3166, ISO 19112, M49, SALB, INSPIRE, NUTS, GML, GeoSPARQL and GeoJSON crosswalks and 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 government, jurisdiction, place, address, zone, parcel, statistic and dispute models.", "Develop jurisdiction, historical, maritime, indigenous, customary, occupied and conflict-sensitive administrative-area profiles.", "Create fixtures for hierarchy cycles, wrong code editions, multilingual renaming, enclaves, exclaves, disputed boundaries, split, merger and retroactive effect.", "Validate certified code, hierarchy and geometry projections with recognition, CRS, topology, loss and round-trip tests." ] }, "statistics": { "sources": 10, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }