{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-plc-004","code":"wm-plc-004-administrative-area","url":"https://ver.cy/models/wm-plc-004-administrative-area/","name":"Administrative Area","alternateNames":["U4"],"kind":"world-model","status":"published","version":"0.3.0-research.1","language":"en","classifiers":{"family":"World Models","category":"Physical world and living systems","entryKind":"entity","plane":"","domain":["PHY.PLC.ADM"],"industry":["Cross-industry"],"navPath":"NAV.PHY.PLC.ADM","tags":["administrative","area","phy.plc.adm"],"facets":{}},"whatItIs":"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.","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":{"in":["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":["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"],"boundaries":[{"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."},{"neighbor":"Settlement, Place and Address","distinction":"A settlement or locality can cross or sit within units, and addresses locate objects; none defines administrative identity."},{"neighbor":"Statistical, Postal and Electoral Area","distinction":"These purpose-built zones can map to administrative units but retain independent authority, geometry and lifecycle."},{"neighbor":"Land Parcel","distinction":"A parcel is a land-administration spatial unit at property or cadastral grain, not an administrative government territory."},{"neighbor":"Sovereignty and Territorial Claim","distinction":"The model preserves who claims or recognizes an extent and for what scope but never decides universal sovereignty."}]},"distinguishingFeatures":["Models a governed territorial unit with legal or statistical standing, unlike a settlement or place that is a named locality.","Keeps boundary assertions per source, so official, statistical, claimed and de facto lines can coexist for one unit.","Separates the unit from the government that administers it and from the jurisdiction whose law applies there.","Treats codes such as ISO 3166-2 or NUTS as versioned bindings, not as the identity of the unit itself."],"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.","layers":[{"id":"master-identity-and-code-systems","name":"Master identity and code systems","description":"Stable identity, source register and versioned codes.","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.","questions":[{"text":"What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for authoritative unit identifier, register and issuing authority?","id":"authoritative-unit-identifier-register-and-issuing-authority-q01","kind":"identity"},{"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?","id":"authoritative-unit-identifier-register-and-issuing-authority-q02","kind":"evidence"},{"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?","id":"authoritative-unit-identifier-register-and-issuing-authority-q03","kind":"validation"}]},{"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.","questions":[{"text":"What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for national, iso, m49, nuts, salb and local code bindings?","id":"national-iso-m49-nuts-salb-and-local-code-bindings-q01","kind":"classification"},{"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?","id":"national-iso-m49-nuts-salb-and-local-code-bindings-q02","kind":"evidence"},{"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?","id":"national-iso-m49-nuts-salb-and-local-code-bindings-q03","kind":"validation"}]}]},{"id":"unit-class-level-and-names","name":"Unit class, level and names","description":"Administrative classification and multilingual naming history.","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.","questions":[{"text":"What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for administrative-unit type, level, order and classification?","id":"administrative-unit-type-level-order-and-classification-q01","kind":"classification"},{"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?","id":"administrative-unit-type-level-order-and-classification-q02","kind":"evidence"},{"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?","id":"administrative-unit-type-level-order-and-classification-q03","kind":"validation"}]},{"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.","questions":[{"text":"What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for official, short, long, multilingual, historic and variant names?","id":"official-short-long-multilingual-historic-and-variant-names-q01","kind":"definition"},{"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?","id":"official-short-long-multilingual-historic-and-variant-names-q02","kind":"evidence"},{"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?","id":"official-short-long-multilingual-historic-and-variant-names-q03","kind":"validation"}]}]}]},{"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.","layers":[{"id":"constitutive-authority-and-instrument","name":"Constitutive authority and instrument","description":"Legal or official basis and the organization exercising competence.","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.","questions":[{"text":"What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for constituting instrument, authority, jurisdiction and legal effect?","id":"constituting-instrument-authority-jurisdiction-and-legal-effect-q01","kind":"authority"},{"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?","id":"constituting-instrument-authority-jurisdiction-and-legal-effect-q02","kind":"evidence"},{"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?","id":"constituting-instrument-authority-jurisdiction-and-legal-effect-q03","kind":"validation"}]},{"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.","questions":[{"text":"What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for government organization, seat, capacity and competence reference?","id":"government-organization-seat-capacity-and-competence-reference-q01","kind":"relationship"},{"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?","id":"government-organization-seat-capacity-and-competence-reference-q02","kind":"evidence"},{"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?","id":"government-organization-seat-capacity-and-competence-reference-q03","kind":"validation"}]}]},{"id":"administrative-and-spatial-hierarchy","name":"Administrative and spatial hierarchy","description":"Versioned parent, containment and grouping relations.","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.","questions":[{"text":"What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for administrative parent, child, predecessor and sibling relations?","id":"administrative-parent-child-predecessor-and-sibling-relations-q01","kind":"relationship"},{"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?","id":"administrative-parent-child-predecessor-and-sibling-relations-q02","kind":"evidence"},{"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?","id":"administrative-parent-child-predecessor-and-sibling-relations-q03","kind":"validation"}]},{"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.","questions":[{"text":"What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for geometric containment, statistical region and overlap relations?","id":"geometric-containment-statistical-region-and-overlap-relations-q01","kind":"spatial"},{"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?","id":"geometric-containment-statistical-region-and-overlap-relations-q02","kind":"evidence"},{"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?","id":"geometric-containment-statistical-region-and-overlap-relations-q03","kind":"validation"}]}]}]},{"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.","layers":[{"id":"boundary-assertions-and-recognition","name":"Boundary assertions and recognition","description":"Source-qualified official, statistical, claimed, disputed and de facto extents.","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.","questions":[{"text":"What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for official, statistical, claimed, disputed and de facto boundary?","id":"official-statistical-claimed-disputed-and-de-facto-boundary-q01","kind":"spatial"},{"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?","id":"official-statistical-claimed-disputed-and-de-facto-boundary-q02","kind":"evidence"},{"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?","id":"official-statistical-claimed-disputed-and-de-facto-boundary-q03","kind":"validation"}]},{"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.","questions":[{"text":"What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for boundary segment, point, source, demarcation and agreement?","id":"boundary-segment-point-source-demarcation-and-agreement-q01","kind":"composition"},{"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?","id":"boundary-segment-point-source-demarcation-and-agreement-q02","kind":"evidence"},{"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?","id":"boundary-segment-point-source-demarcation-and-agreement-q03","kind":"validation"}]}]},{"id":"geometry-crs-topology-and-measures","name":"Geometry, CRS, topology and measures","description":"Coordinate semantics, special topology and measured extents.","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.","questions":[{"text":"What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for geometry, crs, axis order, dimensionality, precision and accuracy?","id":"geometry-crs-axis-order-dimensionality-precision-and-accuracy-q01","kind":"measurement"},{"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?","id":"geometry-crs-axis-order-dimensionality-precision-and-accuracy-q02","kind":"evidence"},{"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?","id":"geometry-crs-axis-order-dimensionality-precision-and-accuracy-q03","kind":"validation"}]},{"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.","questions":[{"text":"What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for area, coastline, enclave, exclave, hole, adjacency and topology?","id":"area-coastline-enclave-exclave-hole-adjacency-and-topology-q01","kind":"spatial"},{"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?","id":"area-coastline-enclave-exclave-hole-adjacency-and-topology-q02","kind":"evidence"},{"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?","id":"area-coastline-enclave-exclave-hole-adjacency-and-topology-q03","kind":"validation"}]}]}]},{"id":"lifecycle-change-and-lineage","name":"Lifecycle, change and lineage","description":"Preserves creation, modification and replacement of administrative units.","layers":[{"id":"state-and-bitemporal-effectivity","name":"State and bitemporal effectivity","description":"Current and historic state with separate legal and knowledge time.","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.","questions":[{"text":"What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for proposed, active, suspended, disputed, superseded and abolished state?","id":"proposed-active-suspended-disputed-superseded-and-abolished-state-q01","kind":"state"},{"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?","id":"proposed-active-suspended-disputed-superseded-and-abolished-state-q02","kind":"evidence"},{"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?","id":"proposed-active-suspended-disputed-superseded-and-abolished-state-q03","kind":"validation"}]},{"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.","questions":[{"text":"What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for decision, legal-effect, observation, publication and knowledge time?","id":"decision-legal-effect-observation-publication-and-knowledge-time-q01","kind":"temporal"},{"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?","id":"decision-legal-effect-observation-publication-and-knowledge-time-q02","kind":"evidence"},{"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?","id":"decision-legal-effect-observation-publication-and-knowledge-time-q03","kind":"validation"}]}]},{"id":"territorial-and-classification-change","name":"Territorial and classification change","description":"Authorized transformations and identity consequences.","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.","questions":[{"text":"What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for creation, split, merger, transfer, annexation and boundary adjustment?","id":"creation-split-merger-transfer-annexation-and-boundary-adjustment-q01","kind":"lifecycle"},{"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?","id":"creation-split-merger-transfer-annexation-and-boundary-adjustment-q02","kind":"evidence"},{"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?","id":"creation-split-merger-transfer-annexation-and-boundary-adjustment-q03","kind":"validation"}]},{"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.","questions":[{"text":"What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for renaming, recoding, reclassification, successor and tombstone?","id":"renaming-recoding-reclassification-successor-and-tombstone-q01","kind":"lifecycle"},{"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?","id":"renaming-recoding-reclassification-successor-and-tombstone-q02","kind":"evidence"},{"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?","id":"renaming-recoding-reclassification-successor-and-tombstone-q03","kind":"validation"}]}]}]},{"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.","layers":[{"id":"places-zones-and-functional-context","name":"Places, zones and functional context","description":"External settlement and service-area relations.","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.","questions":[{"text":"What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for settlement, locality, address, parcel and building reference?","id":"settlement-locality-address-parcel-and-building-reference-q01","kind":"relationship"},{"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?","id":"settlement-locality-address-parcel-and-building-reference-q02","kind":"evidence"},{"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?","id":"settlement-locality-address-parcel-and-building-reference-q03","kind":"validation"}]},{"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.","questions":[{"text":"What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for postal, electoral, service, planning, timezone and jurisdiction reference?","id":"postal-electoral-service-planning-timezone-and-jurisdiction-reference-q01","kind":"relationship"},{"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?","id":"postal-electoral-service-planning-timezone-and-jurisdiction-reference-q02","kind":"evidence"},{"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?","id":"postal-electoral-service-planning-timezone-and-jurisdiction-reference-q03","kind":"validation"}]}]},{"id":"statistics-observations-and-recognition-conflict","name":"Statistics, observations and recognition conflict","description":"Time-qualified measures and competing sovereignty or status claims.","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.","questions":[{"text":"What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for population, area, statistic, indicator, reference time and method?","id":"population-area-statistic-indicator-reference-time-and-method-q01","kind":"measurement"},{"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?","id":"population-area-statistic-indicator-reference-time-and-method-q02","kind":"evidence"},{"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?","id":"population-area-statistic-indicator-reference-time-and-method-q03","kind":"validation"}]},{"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.","questions":[{"text":"What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for territorial claim, recognition status, dispute and neutral display?","id":"territorial-claim-recognition-status-dispute-and-neutral-display-q01","kind":"provenance"},{"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?","id":"territorial-claim-recognition-status-dispute-and-neutral-display-q02","kind":"evidence"},{"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?","id":"territorial-claim-recognition-status-dispute-and-neutral-display-q03","kind":"validation"}]}]}]},{"id":"interoperability-governance-and-agent-operations","name":"Interoperability, governance and agent operations","description":"Controls mappings, provenance, disclosure and safe automated maintenance.","layers":[{"id":"classifiers-projections-and-access","name":"Classifiers, projections and access","description":"Versioned code and geospatial projections with purpose controls.","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.","questions":[{"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?","id":"iso-m49-nuts-salb-inspire-gml-geosparql-and-geojson-projection-q01","kind":"interoperability"},{"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?","id":"iso-m49-nuts-salb-inspire-gml-geosparql-and-geojson-projection-q02","kind":"evidence"},{"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?","id":"iso-m49-nuts-salb-inspire-gml-geosparql-and-geojson-projection-q03","kind":"validation"}]},{"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.","questions":[{"text":"What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for public map, statistical, restricted and dispute-sensitive view?","id":"public-map-statistical-restricted-and-dispute-sensitive-view-q01","kind":"access"},{"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?","id":"public-map-statistical-restricted-and-dispute-sensitive-view-q02","kind":"evidence"},{"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?","id":"public-map-statistical-restricted-and-dispute-sensitive-view-q03","kind":"validation"}]}]},{"id":"safe-agent-control-and-validation","name":"Safe agent control and validation","description":"Authorized operations, invariants, concurrency and audit.","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.","questions":[{"text":"What exact identifiers, codes, names, geometry qualifiers and explicit unknowns must be recorded for agent operation authority, purpose, preconditions and confirmation?","id":"agent-operation-authority-purpose-preconditions-and-confirmation-q01","kind":"security"},{"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?","id":"agent-operation-authority-purpose-preconditions-and-confirmation-q02","kind":"evidence"},{"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?","id":"agent-operation-authority-purpose-preconditions-and-confirmation-q03","kind":"validation"}]},{"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.","questions":[{"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?","id":"prewrite-postwrite-validation-conflict-concurrency-and-recovery-q01","kind":"validation"},{"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?","id":"prewrite-postwrite-validation-conflict-concurrency-and-recovery-q02","kind":"evidence"},{"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?","id":"prewrite-postwrite-validation-conflict-concurrency-and-recovery-q03","kind":"validation"}]}]}]}]},"agentConduct":{"may":["Validate boundary geometry, topology and CRS and report gaps or overlaps.","Resolve a unit by code or name for a stated date and code system.","Propose a territorial change with its source instrument for authority review.","Issue a purpose-bound view at the minimum precision the use needs."],"mustNot":["Change canonical unit identity, level or legal-effect state without register authority.","Present one claimed or disputed boundary as the universally recognised line.","Infer current administrative identity from a code, name or population figure alone.","Reuse a retired or reassigned code as if it still named the old unit.","Suppress a recorded dispute or recognition assertion from a view that requests it."],"requiresHuman":["Registering a merger, split, abolition or reclassification of a unit.","Recording or publishing a recognition or dispute position on a contested boundary.","Releasing sensitive boundary or authority data beyond its granted audience."]},"ethics":{"considerations":["Boundary representations in disputed regions carry political weight and can harm people on either side if presented as settled.","Unit boundaries decide access to services, voting and taxation, so errors shift rights between residents.","Historic units must remain resolvable so that old records about people and land keep their meaning."],"affectedParties":["Residents of the area","Public authorities and statistical offices","Communities in disputed or recently changed territories"]},"owners":{"steward":"Dimension identity, owner, administrative-register authority, boundary steward and namespace","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."]}],"masterSystems":[]},"relations":[{"target":"Government, Jurisdiction, Instrument, Place, Address, Zone, Parcel, Statistic and Dispute models","type":"references","note":"Connect administrative territory to external legal, organizational, spatial, observational and dispute masters."},{"target":"ISO 3166 and ISO 19112","type":"aligned","note":"Bind versioned country or subdivision codes and geographic-identifier schemes without replacing the master identity."},{"target":"UN M49 and SALB","type":"aligned","note":"Project statistical area codes and time-aware first or second administrative boundary references."},{"target":"INSPIRE Administrative Units and NUTS","type":"aligned","note":"Project European administrative and statistical unit identifiers, levels, names, geometry and lifecycle."},{"target":"GML, GeoSPARQL and GeoJSON","type":"aligned","note":"Publish geometry and semantic-spatial views with CRS, topology, dispute and mapping-loss declarations."},{"target":"Government and Jurisdiction","type":"neighbor","note":"A government is an organization and a jurisdiction is a competence relation; the administrative area is the territorial unit they may govern."},{"target":"Settlement, Place and Address","type":"neighbor","note":"A settlement or locality can cross or sit within units, and addresses locate objects; none defines administrative identity."},{"target":"Statistical, Postal and Electoral Area","type":"neighbor","note":"These purpose-built zones can map to administrative units but retain independent authority, geometry and lifecycle."},{"target":"Land Parcel","type":"neighbor","note":"A parcel is a land-administration spatial unit at property or cadastral grain, not an administrative government territory."},{"target":"Sovereignty and Territorial Claim","type":"neighbor","note":"The model preserves who claims or recognizes an extent and for what scope but never decides universal sovereignty."},{"target":"WM-PLC-005","type":"contains"}],"interaction":{"identity":{"applicability":"required","items":["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."]},"properties":{"applicability":"required","items":["Area in square kilometres, computed on a stated equal-area projection.","Boundary length in kilometres, with the source scale or resolution stated.","Positional accuracy of boundary vertices in metres, against a stated reference survey.","Coordinate reference system and epoch of the boundary geometry."]},"recognition":{"applicability":"optional","items":["An administrative area has an issuing register, a unit type and level, codes, official names and an effective period.","It is often confused with a settlement, postal zone, electoral district or statistical grid cell that shares its name."]},"capabilities":{"applicability":"required","items":["Register administrative area: Create the master identity, unit type, register, authority and initial effective state.","Bind code or name: Append a versioned code-system binding or official, historic or language-qualified name.","Bind administrative hierarchy: Append a typed parent, child, containment or statistical-grouping relation.","Attach boundary assertion: Append an official, statistical, claimed, disputed or de facto geometry with source and recognition scope.","Validate geometry and topology: Check validity, CRS, parts, holes, adjacency, overlaps, gaps and measured area.","Propose territorial change: Create a case for split, merger, transfer, annexation or boundary adjustment.","Register change or reclassification: Apply an authorized territorial, hierarchy, name, code or class change and preserve successors.","Record recognition or dispute: Append a claimant, recognizing party, claimed extent, basis and neutral-display rule.","Issue administrative-area view: Create a purpose-bound code, hierarchy, statistical or map projection with declared loss.","Retire administrative area: Abolish or supersede a unit while preserving code, name, boundary and lineage tombstones."]},"hazards":{"applicability":"required","items":["Outdated boundaries route emergency services or benefits to the wrong authority.","Code reuse after reorganisation silently merges histories of different units.","Coordinate reference system mismatch shifts boundaries and misassigns parcels or addresses.","Publishing contested lines as official provokes diplomatic or community conflict."]},"interfaces":{"applicability":"required","items":["ISO 3166-2 country subdivision codes.","UN M49 standard country or area codes for statistical use.","Eurostat NUTS and LAU classifications.","INSPIRE Administrative Units data specification.","OGC Simple Features and GeoJSON (IETF RFC 7946) for boundary geometry."]},"context":{"applicability":"required","items":["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."]}},"sources":[{"title":"ISO 3166 Country Codes","url":"https://www.iso.org/iso-3166-country-codes.html","note":"International Organization for Standardization"},{"title":"Standard country or area codes for statistical use, M49","url":"https://unstats.un.org/unsd/methodology/m49/","note":"United Nations Statistics Division"},{"title":"INSPIRE Data Specification on Administrative Units","url":"https://inspire.ec.europa.eu/id/document/tg/au","note":"European Commission INSPIRE"},{"title":"OGC GeoSPARQL 1.1","url":"https://docs.ogc.org/is/22-047r1/22-047r1.html","note":"Open Geospatial Consortium"},{"title":"Geography Markup Language","url":"https://www.ogc.org/standards/gml","note":"Open Geospatial Consortium"},{"title":"ISO 19112 Geographic information, Spatial referencing by geographic identifiers","url":"https://www.iso.org/standard/74046.html","note":"International Organization for Standardization"},{"title":"Regulation on the establishment of a common classification of territorial units for statistics","url":"https://eur-lex.europa.eu/eli/reg/2003/1059/oj","note":"European Union"},{"title":"Second Administrative Level Boundaries","url":"https://salb.un.org/","note":"United Nations"},{"title":"The GeoJSON Format","url":"https://www.rfc-editor.org/rfc/rfc7946","note":"Internet Engineering Task Force"},{"title":"Date and Time on the Internet: Timestamps","url":"https://www.rfc-editor.org/rfc/rfc3339","note":"Internet Engineering Task Force"}],"openQuestions":["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.","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."],"resources":{"spec":"/models/wm-plc-004-administrative-area/spec.yaml","agents":"/models/wm-plc-004-administrative-area/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-plc-004"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-plc-004-administrative-area/spec.yaml","ver-cy/world-models/card-supplements/wm-plc-004-administrative-area.json"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-09-06T02:35:12Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"filled","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-05, unreviewed). Written from the published specification and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}