# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T02:21:44Z", "synthesisSha256": "e43bea76e1325ef1f0c562b9994878a655af80b988b3882e86738df807e3494a", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-PLC-002", "registryId": "vr.wm-plc-002", "name": "Land Parcel", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.PLC.PAR" ], "tags": [ "land", "parcel", "phy.plc.par" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-plc-002-land-parcel/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-plc-002", "model": { "registry_id": "vr.wm-plc-002", "model_id": "WM-PLC-002", "name": "Land Parcel", "entry_kind": "entity", "purpose": "Represent an authoritative or proposed land-administration spatial unit with stable identity, direct geometry, boundary evidence, lifecycle and legal-context links independent of format.", "scope_statement": "Owns parcel identity, class, jurisdiction, status, geometry roles, CRS, boundaries, area, topology, survey and source evidence, quality, lifecycle and provenance. Parties, title, rights, restrictions, responsibilities, address, building, planning, use, valuation and tax remain external.", "in_scope": [ "Parcel identity, jurisdiction, class and spatial-unit boundary", "Geometry, CRS, boundary, area, topology, survey evidence and quality", "Registration state, subdivision, consolidation, lineage, context links, projections and safe operations" ], "out_of_scope": [ "Party, ownership, title and legal-interest lifecycles", "Address, building, site, planning, land cover, valuation, taxation and survey-project masters", "Universal cadastral law or legal effect" ], "boundary_notes": [ { "neighbor": "Title and Ownership", "distinction": "A parcel is a spatial unit; title and ownership are external legal relationships.", "source_refs": [ "SRC-001" ] }, { "neighbor": "Address and Building", "distinction": "Addresses locate and buildings occupy or relate to land but do not identify the parcel.", "source_refs": [ "SRC-002", "SRC-004" ] }, { "neighbor": "Site and Land", "distinction": "A site is a purpose context and land is physical reality; a parcel is a governed administrative spatial unit.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "Survey", "distinction": "Survey owns observations and evidence; the parcel stores accepted or competing boundary assertions and links.", "source_refs": [ "SRC-002" ] } ] }, "sources": [ { "id": "SRC-001", "title": "ISO 19152-1:2024 Land Administration Domain Model, Generic conceptual model", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/81263.html", "version_or_date": "ISO 19152-1:2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:20:00Z", "relevance": "Provides the generic land-administration domain with parties, administrative units, rights, restrictions, responsibilities, spatial units, sources and versioning concepts." }, { "id": "SRC-002", "title": "OGC Land and Infrastructure Conceptual Model Standard", "organization": "Open Geospatial Consortium", "url": "https://docs.ogc.org/is/15-111r1/15-111r1.html", "version_or_date": "OGC 15-111r1, LandInfra 1.0", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:20:00Z", "relevance": "Defines land features, land divisions, interests, documents, survey observations, survey points and feature lifecycle concepts." }, { "id": "SRC-003", "title": "OGC InfraGML Part 7, Land Division", "organization": "Open Geospatial Consortium", "url": "https://docs.ogc.org/is/16-107r2/16-107r2.html", "version_or_date": "OGC 16-107r2, InfraGML 1.0", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:20:00Z", "relevance": "Provides an implementation schema for land divisions, parcels, condominiums, interests and administrative units aligned to LandInfra." }, { "id": "SRC-004", "title": "INSPIRE Data Specification on Cadastral Parcels", "organization": "European Commission INSPIRE", "url": "https://inspire.ec.europa.eu/id/document/tg/cp", "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:20:00Z", "relevance": "Defines cadastral parcels, cadastral zonings, basic property units, national cadastral references, labels, areas, geometry and lifecycle metadata for European interoperability." }, { "id": "SRC-005", "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:20:00Z", "relevance": "Defines feature and geometry vocabularies, coordinate reference system serialization and topological query relations for semantic spatial projection." }, { "id": "SRC-006", "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:20:00Z", "relevance": "Provides standardized geometry, feature, coordinate reference system and topology encodings used by cadastral exchange profiles." }, { "id": "SRC-007", "title": "EPSG Geodetic Parameter Dataset", "organization": "International Association of Oil and Gas Producers", "url": "https://epsg.org/", "version_or_date": "Current registry, accessed 6 September 2026", "source_type": "registry", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:20:00Z", "relevance": "Provides versioned coordinate reference system and transformation identifiers needed to interpret parcel coordinates and area calculations." }, { "id": "SRC-008", "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:20:00Z", "relevance": "Defines a common web geometry encoding with WGS 84 and antimeridian constraints; it is a projection and cannot preserve all cadastral CRS or topology semantics." }, { "id": "SRC-009", "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:20:00Z", "relevance": "Defines timestamps with seconds and explicit UTC relation for registration, survey, legal-effect, observation and lifecycle events." } ], "structure": { "bundles": [ { "id": "identity-class-and-jurisdiction", "name": "Identity, class and jurisdiction", "description": "Identifies one parcel within its land-administration authority and legal context.", "rationale": "Geometry, address, owner and label are mutable or non-unique and cannot replace authoritative parcel identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "layers": [ { "id": "parcel-master-identity", "name": "Parcel master identity", "description": "Stable identifiers, aliases and register context.", "source_refs": [ "SRC-001", "SRC-004" ], "findings": [ { "id": "authoritative-parcel-identifier-register-and-jurisdiction", "name": "Authoritative parcel identifier, register and jurisdiction", "description": "National cadastral reference, issuing authority, register, namespace, local identifiers and resolution state.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "authoritative-parcel-identifier-register-and-jurisdiction-q01", "text": "What exact values, identifiers, geometry qualifiers and explicit unknowns must be recorded for authoritative parcel identifier, register and jurisdiction?", "kind": "identity", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "authoritative-parcel-identifier-register-and-jurisdiction-q02", "text": "Which register, surveyor, authority, source and evidence establishes authoritative parcel identifier, register and jurisdiction, at what legal, observation and knowledge time, and with what accuracy?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "accuracy", "evidence" ] }, { "id": "authoritative-parcel-identifier-register-and-jurisdiction-q03", "text": "How may authoritative parcel identifier, register and jurisdiction be validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring lifecycle?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "authoritative-parcel-identifier-register-and-jurisdiction-data", "name": "Authoritative parcel identifier, register and jurisdiction data", "description": "Structured source-qualified data for authoritative parcel identifier, register and jurisdiction.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "authoritative-parcel-identifier-register-and-jurisdiction-record", "name": "Authoritative parcel identifier, register and jurisdiction record", "description": "Versioned evidence-bearing record for authoritative parcel identifier, register and jurisdiction with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical parcel record", "survey or administrative evidence reference" ], "serial": true, "identity_strategy": "Parcel identifier plus authoritative-parcel-identifier-register-and-jurisdiction assertion or event identifier; address, owner, geometry, date and hash never identify the parcel alone.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null }, { "id": "parcel-type-status-label-address-and-aliases", "name": "Parcel type, status, label, address and aliases", "description": "Profile-qualified class and lifecycle status plus non-authoritative labels, address links and historic aliases.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "parcel-type-status-label-address-and-aliases-q01", "text": "What exact values, identifiers, geometry qualifiers and explicit unknowns must be recorded for parcel type, status, label, address and aliases?", "kind": "classification", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "parcel-type-status-label-address-and-aliases-q02", "text": "Which register, surveyor, authority, source and evidence establishes parcel type, status, label, address and aliases, at what legal, observation and knowledge time, and with what accuracy?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "accuracy", "evidence" ] }, { "id": "parcel-type-status-label-address-and-aliases-q03", "text": "How may parcel type, status, label, address and aliases be validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring lifecycle?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "parcel-type-status-label-address-and-aliases-data", "name": "Parcel type, status, label, address and aliases data", "description": "Structured source-qualified data for parcel type, status, label, address and aliases.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "parcel-type-status-label-address-and-aliases-record", "name": "Parcel type, status, label, address and aliases record", "description": "Versioned evidence-bearing record for parcel type, status, label, address and aliases with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical parcel record", "survey or administrative evidence reference" ], "serial": true, "identity_strategy": "Parcel identifier plus parcel-type-status-label-address-and-aliases assertion or event identifier; address, owner, geometry, date and hash never identify the parcel alone.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "legal-spatial-unit-boundary", "name": "Legal spatial-unit boundary", "description": "Distinguishes the parcel from neighboring concepts and legal relations.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "findings": [ { "id": "spatial-unit-level-dimensionality-and-basic-property-unit", "name": "Spatial-unit level, dimensionality and basic property unit", "description": "2D or 3D spatial-unit class, hierarchy, legal-space semantics and optional grouping in a basic property unit.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ], "questions": [ { "id": "spatial-unit-level-dimensionality-and-basic-property-unit-q01", "text": "What exact values, identifiers, geometry qualifiers and explicit unknowns must be recorded for spatial-unit level, dimensionality and basic property unit?", "kind": "classification", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "spatial-unit-level-dimensionality-and-basic-property-unit-q02", "text": "Which register, surveyor, authority, source and evidence establishes spatial-unit level, dimensionality and basic property unit, at what legal, observation and knowledge time, and with what accuracy?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "accuracy", "evidence" ] }, { "id": "spatial-unit-level-dimensionality-and-basic-property-unit-q03", "text": "How may spatial-unit level, dimensionality and basic property unit be validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring lifecycle?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "spatial-unit-level-dimensionality-and-basic-property-unit-data", "name": "Spatial-unit level, dimensionality and basic property unit data", "description": "Structured source-qualified data for spatial-unit level, dimensionality and basic property unit.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "spatial-unit-level-dimensionality-and-basic-property-unit-record", "name": "Spatial-unit level, dimensionality and basic property unit record", "description": "Versioned evidence-bearing record for spatial-unit level, dimensionality and basic property unit with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical parcel record", "survey or administrative evidence reference" ], "serial": true, "identity_strategy": "Parcel identifier plus spatial-unit-level-dimensionality-and-basic-property-unit assertion or event identifier; address, owner, geometry, date and hash never identify the parcel alone.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null }, { "id": "parcel-versus-land-site-address-building-title-and-interest", "name": "Parcel versus land, site, address, building, title and interest", "description": "Typed non-equivalence and external references preventing inference of ownership or physical occupation from parcel membership.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "parcel-versus-land-site-address-building-title-and-interest-q01", "text": "What exact values, identifiers, geometry qualifiers and explicit unknowns must be recorded for parcel versus land, site, address, building, title and interest?", "kind": "relationship", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "parcel-versus-land-site-address-building-title-and-interest-q02", "text": "Which register, surveyor, authority, source and evidence establishes parcel versus land, site, address, building, title and interest, at what legal, observation and knowledge time, and with what accuracy?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "accuracy", "evidence" ] }, { "id": "parcel-versus-land-site-address-building-title-and-interest-q03", "text": "How may parcel versus land, site, address, building, title and interest be validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring lifecycle?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "parcel-versus-land-site-address-building-title-and-interest-data", "name": "Parcel versus land, site, address, building, title and interest data", "description": "Structured source-qualified data for parcel versus land, site, address, building, title and interest.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "parcel-versus-land-site-address-building-title-and-interest-record", "name": "Parcel versus land, site, address, building, title and interest record", "description": "Versioned evidence-bearing record for parcel versus land, site, address, building, title and interest with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical parcel record", "survey or administrative evidence reference" ], "serial": true, "identity_strategy": "Parcel identifier plus parcel-versus-land-site-address-building-title-and-interest assertion or event identifier; address, owner, geometry, date and hash never identify the parcel alone.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "geometry-boundary-area-and-topology", "name": "Geometry, boundary, area and topology", "description": "Represents direct spatial properties and their authoritative status.", "rationale": "Legal boundary, survey reconstruction, map geometry and occupied fence line can disagree and need separate evidence.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "layers": [ { "id": "geometry-and-coordinate-reference", "name": "Geometry and coordinate reference", "description": "Coordinates, surfaces, volumes and coordinate semantics.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-007" ], "findings": [ { "id": "official-mapped-surveyed-and-observed-geometry", "name": "Official, mapped, surveyed and observed geometry", "description": "Multiple geometry assertions with role, dimensionality, primitive type, source, valid time and authority.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ], "questions": [ { "id": "official-mapped-surveyed-and-observed-geometry-q01", "text": "What exact values, identifiers, geometry qualifiers and explicit unknowns must be recorded for official, mapped, surveyed and observed geometry?", "kind": "spatial", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "official-mapped-surveyed-and-observed-geometry-q02", "text": "Which register, surveyor, authority, source and evidence establishes official, mapped, surveyed and observed geometry, at what legal, observation and knowledge time, and with what accuracy?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "accuracy", "evidence" ] }, { "id": "official-mapped-surveyed-and-observed-geometry-q03", "text": "How may official, mapped, surveyed and observed geometry be validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring lifecycle?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "official-mapped-surveyed-and-observed-geometry-data", "name": "Official, mapped, surveyed and observed geometry data", "description": "Structured source-qualified data for official, mapped, surveyed and observed geometry.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "official-mapped-surveyed-and-observed-geometry-record", "name": "Official, mapped, surveyed and observed geometry record", "description": "Versioned evidence-bearing record for official, mapped, surveyed and observed geometry with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical parcel record", "survey or administrative evidence reference" ], "serial": true, "identity_strategy": "Parcel identifier plus official-mapped-surveyed-and-observed-geometry assertion or event identifier; address, owner, geometry, date and hash never identify the parcel alone.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "crs-axis-order-epoch-transformation-precision-and-accuracy", "name": "CRS, axis order, epoch, transformation, precision and accuracy", "description": "EPSG or other CRS identity and version, axis order, coordinate epoch, transformation path, precision, accuracy and uncertainty.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ], "questions": [ { "id": "crs-axis-order-epoch-transformation-precision-and-accuracy-q01", "text": "What exact values, identifiers, geometry qualifiers and explicit unknowns must be recorded for crs, axis order, epoch, transformation, precision and accuracy?", "kind": "measurement", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "crs-axis-order-epoch-transformation-precision-and-accuracy-q02", "text": "Which register, surveyor, authority, source and evidence establishes crs, axis order, epoch, transformation, precision and accuracy, at what legal, observation and knowledge time, and with what accuracy?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "accuracy", "evidence" ] }, { "id": "crs-axis-order-epoch-transformation-precision-and-accuracy-q03", "text": "How may crs, axis order, epoch, transformation, precision and accuracy be validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring lifecycle?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "crs-axis-order-epoch-transformation-precision-and-accuracy-data", "name": "CRS, axis order, epoch, transformation, precision and accuracy data", "description": "Structured source-qualified data for crs, axis order, epoch, transformation, precision and accuracy.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "crs-axis-order-epoch-transformation-precision-and-accuracy-record", "name": "CRS, axis order, epoch, transformation, precision and accuracy record", "description": "Versioned evidence-bearing record for crs, axis order, epoch, transformation, precision and accuracy with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical parcel record", "survey or administrative evidence reference" ], "serial": true, "identity_strategy": "Parcel identifier plus crs-axis-order-epoch-transformation-precision-and-accuracy assertion or event identifier; address, owner, geometry, date and hash never identify the parcel alone.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "boundary-area-and-topology", "name": "Boundary, area and topology", "description": "Boundary components, calculated measures and neighbor consistency.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-005" ], "findings": [ { "id": "boundary-face-string-point-segment-and-monument", "name": "Boundary face string, point, segment and monument", "description": "Ordered boundary components, legal or survey role, monuments, natural boundaries, source observations and acceptance state.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "questions": [ { "id": "boundary-face-string-point-segment-and-monument-q01", "text": "What exact values, identifiers, geometry qualifiers and explicit unknowns must be recorded for boundary face string, point, segment and monument?", "kind": "composition", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "boundary-face-string-point-segment-and-monument-q02", "text": "Which register, surveyor, authority, source and evidence establishes boundary face string, point, segment and monument, at what legal, observation and knowledge time, and with what accuracy?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "accuracy", "evidence" ] }, { "id": "boundary-face-string-point-segment-and-monument-q03", "text": "How may boundary face string, point, segment and monument be validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring lifecycle?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "boundary-face-string-point-segment-and-monument-data", "name": "Boundary face string, point, segment and monument data", "description": "Structured source-qualified data for boundary face string, point, segment and monument.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "boundary-face-string-point-segment-and-monument-record", "name": "Boundary face string, point, segment and monument record", "description": "Versioned evidence-bearing record for boundary face string, point, segment and monument with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical parcel record", "survey or administrative evidence reference" ], "serial": true, "identity_strategy": "Parcel identifier plus boundary-face-string-point-segment-and-monument assertion or event identifier; address, owner, geometry, date and hash never identify the parcel alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null }, { "id": "official-and-calculated-area-unit-method-and-topology", "name": "Official and calculated area, unit, method and topology", "description": "Area or volume value, unit, calculation method, tolerance, discrepancies, adjacency, containment, overlap and gap checks.", "source_refs": [ "SRC-004", "SRC-005" ], "questions": [ { "id": "official-and-calculated-area-unit-method-and-topology-q01", "text": "What exact values, identifiers, geometry qualifiers and explicit unknowns must be recorded for official and calculated area, unit, method and topology?", "kind": "measurement", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "official-and-calculated-area-unit-method-and-topology-q02", "text": "Which register, surveyor, authority, source and evidence establishes official and calculated area, unit, method and topology, at what legal, observation and knowledge time, and with what accuracy?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "accuracy", "evidence" ] }, { "id": "official-and-calculated-area-unit-method-and-topology-q03", "text": "How may official and calculated area, unit, method and topology be validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring lifecycle?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "official-and-calculated-area-unit-method-and-topology-data", "name": "Official and calculated area, unit, method and topology data", "description": "Structured source-qualified data for official and calculated area, unit, method and topology.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "official-and-calculated-area-unit-method-and-topology-record", "name": "Official and calculated area, unit, method and topology record", "description": "Versioned evidence-bearing record for official and calculated area, unit, method and topology with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical parcel record", "survey or administrative evidence reference" ], "serial": true, "identity_strategy": "Parcel identifier plus official-and-calculated-area-unit-method-and-topology assertion or event identifier; address, owner, geometry, date and hash never identify the parcel alone.", "source_refs": [ "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "survey-source-quality-and-evidence", "name": "Survey source, quality and evidence", "description": "Connects parcel assertions to observations, documents and quality controls.", "rationale": "A drawn polygon is not legal evidence unless the source, survey method, authority, accuracy and acceptance are known.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-007" ], "layers": [ { "id": "survey-observations-and-control", "name": "Survey observations and control", "description": "Measurements, equipment, reference points and adjustment.", "source_refs": [ "SRC-002", "SRC-007" ], "findings": [ { "id": "survey-event-method-equipment-observation-and-adjustment", "name": "Survey event, method, equipment, observation and adjustment", "description": "External survey identity, surveyor authority, method, equipment calibration, raw observation links, network adjustment and residuals.", "source_refs": [ "SRC-002", "SRC-007" ], "questions": [ { "id": "survey-event-method-equipment-observation-and-adjustment-q01", "text": "What exact values, identifiers, geometry qualifiers and explicit unknowns must be recorded for survey event, method, equipment, observation and adjustment?", "kind": "evidence", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "survey-event-method-equipment-observation-and-adjustment-q02", "text": "Which register, surveyor, authority, source and evidence establishes survey event, method, equipment, observation and adjustment, at what legal, observation and knowledge time, and with what accuracy?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "accuracy", "evidence" ] }, { "id": "survey-event-method-equipment-observation-and-adjustment-q03", "text": "How may survey event, method, equipment, observation and adjustment be validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring lifecycle?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "survey-event-method-equipment-observation-and-adjustment-data", "name": "Survey event, method, equipment, observation and adjustment data", "description": "Structured source-qualified data for survey event, method, equipment, observation and adjustment.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-007" ] } ], "artifacts": [ { "id": "survey-event-method-equipment-observation-and-adjustment-record", "name": "Survey event, method, equipment, observation and adjustment record", "description": "Versioned evidence-bearing record for survey event, method, equipment, observation and adjustment with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical parcel record", "survey or administrative evidence reference" ], "serial": true, "identity_strategy": "Parcel identifier plus survey-event-method-equipment-observation-and-adjustment assertion or event identifier; address, owner, geometry, date and hash never identify the parcel alone.", "source_refs": [ "SRC-002", "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "survey-point-control-monument-coordinates-and-recovery", "name": "Survey point, control, monument, coordinates and recovery", "description": "Point identity, role, marker, coordinates, CRS, accuracy, condition, witness references and recovery history.", "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ], "questions": [ { "id": "survey-point-control-monument-coordinates-and-recovery-q01", "text": "What exact values, identifiers, geometry qualifiers and explicit unknowns must be recorded for survey point, control, monument, coordinates and recovery?", "kind": "spatial", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "survey-point-control-monument-coordinates-and-recovery-q02", "text": "Which register, surveyor, authority, source and evidence establishes survey point, control, monument, coordinates and recovery, at what legal, observation and knowledge time, and with what accuracy?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "accuracy", "evidence" ] }, { "id": "survey-point-control-monument-coordinates-and-recovery-q03", "text": "How may survey point, control, monument, coordinates and recovery be validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring lifecycle?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "survey-point-control-monument-coordinates-and-recovery-data", "name": "Survey point, control, monument, coordinates and recovery data", "description": "Structured source-qualified data for survey point, control, monument, coordinates and recovery.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ] } ], "artifacts": [ { "id": "survey-point-control-monument-coordinates-and-recovery-record", "name": "Survey point, control, monument, coordinates and recovery record", "description": "Versioned evidence-bearing record for survey point, control, monument, coordinates and recovery with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical parcel record", "survey or administrative evidence reference" ], "serial": true, "identity_strategy": "Parcel identifier plus survey-point-control-monument-coordinates-and-recovery assertion or event identifier; address, owner, geometry, date and hash never identify the parcel alone.", "source_refs": [ "SRC-002", "SRC-003", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "source-documents-and-quality", "name": "Source documents and quality", "description": "Administrative and spatial evidence plus fitness for use.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "findings": [ { "id": "spatial-source-administrative-source-plan-and-instrument", "name": "Spatial source, administrative source, plan and instrument", "description": "External document identifiers, issuer, date, legal effect, affected parcels, digest, archive and supersession links.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "spatial-source-administrative-source-plan-and-instrument-q01", "text": "What exact values, identifiers, geometry qualifiers and explicit unknowns must be recorded for spatial source, administrative source, plan and instrument?", "kind": "provenance", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "spatial-source-administrative-source-plan-and-instrument-q02", "text": "Which register, surveyor, authority, source and evidence establishes spatial source, administrative source, plan and instrument, at what legal, observation and knowledge time, and with what accuracy?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "accuracy", "evidence" ] }, { "id": "spatial-source-administrative-source-plan-and-instrument-q03", "text": "How may spatial source, administrative source, plan and instrument be validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring lifecycle?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "spatial-source-administrative-source-plan-and-instrument-data", "name": "Spatial source, administrative source, plan and instrument data", "description": "Structured source-qualified data for spatial source, administrative source, plan and instrument.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "spatial-source-administrative-source-plan-and-instrument-record", "name": "Spatial source, administrative source, plan and instrument record", "description": "Versioned evidence-bearing record for spatial source, administrative source, plan and instrument with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical parcel record", "survey or administrative evidence reference" ], "serial": true, "identity_strategy": "Parcel identifier plus spatial-source-administrative-source-plan-and-instrument assertion or event identifier; address, owner, geometry, date and hash never identify the parcel alone.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null }, { "id": "completeness-positional-thematic-temporal-quality-and-lineage", "name": "Completeness, positional, thematic, temporal quality and lineage", "description": "Quality scope, measure, result, conformance, capture method, update date, transformation lineage and limitations.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ], "questions": [ { "id": "completeness-positional-thematic-temporal-quality-and-lineage-q01", "text": "What exact values, identifiers, geometry qualifiers and explicit unknowns must be recorded for completeness, positional, thematic, temporal quality and lineage?", "kind": "quality", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "completeness-positional-thematic-temporal-quality-and-lineage-q02", "text": "Which register, surveyor, authority, source and evidence establishes completeness, positional, thematic, temporal quality and lineage, at what legal, observation and knowledge time, and with what accuracy?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "accuracy", "evidence" ] }, { "id": "completeness-positional-thematic-temporal-quality-and-lineage-q03", "text": "How may completeness, positional, thematic, temporal quality and lineage be validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring lifecycle?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "completeness-positional-thematic-temporal-quality-and-lineage-data", "name": "Completeness, positional, thematic, temporal quality and lineage data", "description": "Structured source-qualified data for completeness, positional, thematic, temporal quality and lineage.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "completeness-positional-thematic-temporal-quality-and-lineage-record", "name": "Completeness, positional, thematic, temporal quality and lineage record", "description": "Versioned evidence-bearing record for completeness, positional, thematic, temporal quality and lineage with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical parcel record", "survey or administrative evidence reference" ], "serial": true, "identity_strategy": "Parcel identifier plus completeness-positional-thematic-temporal-quality-and-lineage assertion or event identifier; address, owner, geometry, date and hash never identify the parcel alone.", "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "lifecycle-change-and-lineage", "name": "Lifecycle, change and lineage", "description": "Preserves parcel creation, alteration and successor graph.", "rationale": "Subdivisions and consolidations change identity and legal effect; overwriting geometry destroys cited history.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-009" ], "layers": [ { "id": "state-version-and-effectivity", "name": "State, version and effectivity", "description": "Registration and legal-effect states with bitemporal history.", "source_refs": [ "SRC-001", "SRC-004", "SRC-009" ], "findings": [ { "id": "proposed-pending-registered-superseded-retired-and-cancelled-state", "name": "Proposed, pending, registered, superseded, retired and cancelled state", "description": "Profile-specific state, deciding authority, reason, legal-effect interval, record time and contest status.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "proposed-pending-registered-superseded-retired-and-cancelled-state-q01", "text": "What exact values, identifiers, geometry qualifiers and explicit unknowns must be recorded for proposed, pending, registered, superseded, retired and cancelled state?", "kind": "state", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "proposed-pending-registered-superseded-retired-and-cancelled-state-q02", "text": "Which register, surveyor, authority, source and evidence establishes proposed, pending, registered, superseded, retired and cancelled state, at what legal, observation and knowledge time, and with what accuracy?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "accuracy", "evidence" ] }, { "id": "proposed-pending-registered-superseded-retired-and-cancelled-state-q03", "text": "How may proposed, pending, registered, superseded, retired and cancelled state be validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring lifecycle?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "proposed-pending-registered-superseded-retired-and-cancelled-state-data", "name": "Proposed, pending, registered, superseded, retired and cancelled state data", "description": "Structured source-qualified data for proposed, pending, registered, superseded, retired and cancelled state.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "proposed-pending-registered-superseded-retired-and-cancelled-state-record", "name": "Proposed, pending, registered, superseded, retired and cancelled state record", "description": "Versioned evidence-bearing record for proposed, pending, registered, superseded, retired and cancelled state with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical parcel record", "survey or administrative evidence reference" ], "serial": true, "identity_strategy": "Parcel identifier plus proposed-pending-registered-superseded-retired-and-cancelled-state assertion or event identifier; address, owner, geometry, date and hash never identify the parcel alone.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null }, { "id": "survey-event-registration-legal-effect-observation-and-knowledge-time", "name": "Survey event, registration, legal-effect, observation and knowledge time", "description": "Distinct time axes, precision, timezone, retrospective effect and source revision.", "source_refs": [ "SRC-001", "SRC-004", "SRC-009" ], "questions": [ { "id": "survey-event-registration-legal-effect-observation-and-knowledge-time-q01", "text": "What exact values, identifiers, geometry qualifiers and explicit unknowns must be recorded for survey event, registration, legal-effect, observation and knowledge time?", "kind": "temporal", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "survey-event-registration-legal-effect-observation-and-knowledge-time-q02", "text": "Which register, surveyor, authority, source and evidence establishes survey event, registration, legal-effect, observation and knowledge time, at what legal, observation and knowledge time, and with what accuracy?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "accuracy", "evidence" ] }, { "id": "survey-event-registration-legal-effect-observation-and-knowledge-time-q03", "text": "How may survey event, registration, legal-effect, observation and knowledge time be validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring lifecycle?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "survey-event-registration-legal-effect-observation-and-knowledge-time-data", "name": "Survey event, registration, legal-effect, observation and knowledge time data", "description": "Structured source-qualified data for survey event, registration, legal-effect, observation and knowledge time.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-009" ] } ], "artifacts": [ { "id": "survey-event-registration-legal-effect-observation-and-knowledge-time-record", "name": "Survey event, registration, legal-effect, observation and knowledge time record", "description": "Versioned evidence-bearing record for survey event, registration, legal-effect, observation and knowledge time with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical parcel record", "survey or administrative evidence reference" ], "serial": true, "identity_strategy": "Parcel identifier plus survey-event-registration-legal-effect-observation-and-knowledge-time assertion or event identifier; address, owner, geometry, date and hash never identify the parcel alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "subdivision-consolidation-and-reparcellation", "name": "Subdivision, consolidation and reparcellation", "description": "Authorized predecessor-successor transformations.", "source_refs": [ "SRC-001", "SRC-002" ], "findings": [ { "id": "change-case-authority-purpose-plan-and-approval", "name": "Change case, authority, purpose, plan and approval", "description": "External case and instrument, initiating party, authority, proposed topology, validation, approval, appeal and effective date.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "change-case-authority-purpose-plan-and-approval-q01", "text": "What exact values, identifiers, geometry qualifiers and explicit unknowns must be recorded for change case, authority, purpose, plan and approval?", "kind": "decision", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "change-case-authority-purpose-plan-and-approval-q02", "text": "Which register, surveyor, authority, source and evidence establishes change case, authority, purpose, plan and approval, at what legal, observation and knowledge time, and with what accuracy?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "accuracy", "evidence" ] }, { "id": "change-case-authority-purpose-plan-and-approval-q03", "text": "How may change case, authority, purpose, plan and approval be validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring lifecycle?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "change-case-authority-purpose-plan-and-approval-data", "name": "Change case, authority, purpose, plan and approval data", "description": "Structured source-qualified data for change case, authority, purpose, plan and approval.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "change-case-authority-purpose-plan-and-approval-record", "name": "Change case, authority, purpose, plan and approval record", "description": "Versioned evidence-bearing record for change case, authority, purpose, plan and approval with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical parcel record", "survey or administrative evidence reference" ], "serial": true, "identity_strategy": "Parcel identifier plus change-case-authority-purpose-plan-and-approval assertion or event identifier; address, owner, geometry, date and hash never identify the parcel alone.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null }, { "id": "predecessor-successor-split-merge-area-balance-and-tombstone", "name": "Predecessor, successor, split, merge, area balance and tombstone", "description": "Lineage graph, proportions, residual units, identity allocation, area reconciliation and durable tombstones.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "questions": [ { "id": "predecessor-successor-split-merge-area-balance-and-tombstone-q01", "text": "What exact values, identifiers, geometry qualifiers and explicit unknowns must be recorded for predecessor, successor, split, merge, area balance and tombstone?", "kind": "lifecycle", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "predecessor-successor-split-merge-area-balance-and-tombstone-q02", "text": "Which register, surveyor, authority, source and evidence establishes predecessor, successor, split, merge, area balance and tombstone, at what legal, observation and knowledge time, and with what accuracy?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "accuracy", "evidence" ] }, { "id": "predecessor-successor-split-merge-area-balance-and-tombstone-q03", "text": "How may predecessor, successor, split, merge, area balance and tombstone be validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring lifecycle?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "predecessor-successor-split-merge-area-balance-and-tombstone-data", "name": "Predecessor, successor, split, merge, area balance and tombstone data", "description": "Structured source-qualified data for predecessor, successor, split, merge, area balance and tombstone.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "artifacts": [ { "id": "predecessor-successor-split-merge-area-balance-and-tombstone-record", "name": "Predecessor, successor, split, merge, area balance and tombstone record", "description": "Versioned evidence-bearing record for predecessor, successor, split, merge, area balance and tombstone with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical parcel record", "survey or administrative evidence reference" ], "serial": true, "identity_strategy": "Parcel identifier plus predecessor-successor-split-merge-area-balance-and-tombstone assertion or event identifier; address, owner, geometry, date and hash never identify the parcel alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "interests-land-context-and-administration", "name": "Interests, land context and administration", "description": "Links legal and operational context without importing neighboring masters.", "rationale": "Rights, land use, valuation and tax records describe relationships or uses and must not be mistaken for parcel identity or geometry authority.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004" ], "layers": [ { "id": "rights-restrictions-and-responsibilities", "name": "Rights, restrictions and responsibilities", "description": "External legal interests and party relations.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "findings": [ { "id": "party-title-right-restriction-responsibility-and-share-reference", "name": "Party, title, right, restriction, responsibility and share reference", "description": "Typed external interest, parties, share, rank, spatial extent, validity, source and registration status.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "questions": [ { "id": "party-title-right-restriction-responsibility-and-share-reference-q01", "text": "What exact values, identifiers, geometry qualifiers and explicit unknowns must be recorded for party, title, right, restriction, responsibility and share reference?", "kind": "relationship", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "party-title-right-restriction-responsibility-and-share-reference-q02", "text": "Which register, surveyor, authority, source and evidence establishes party, title, right, restriction, responsibility and share reference, at what legal, observation and knowledge time, and with what accuracy?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "accuracy", "evidence" ] }, { "id": "party-title-right-restriction-responsibility-and-share-reference-q03", "text": "How may party, title, right, restriction, responsibility and share reference be validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring lifecycle?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "party-title-right-restriction-responsibility-and-share-reference-data", "name": "Party, title, right, restriction, responsibility and share reference data", "description": "Structured source-qualified data for party, title, right, restriction, responsibility and share reference.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "party-title-right-restriction-responsibility-and-share-reference-record", "name": "Party, title, right, restriction, responsibility and share reference record", "description": "Versioned evidence-bearing record for party, title, right, restriction, responsibility and share reference with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical parcel record", "survey or administrative evidence reference" ], "serial": true, "identity_strategy": "Parcel identifier plus party-title-right-restriction-responsibility-and-share-reference assertion or event identifier; address, owner, geometry, date and hash never identify the parcel alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null }, { "id": "possession-occupation-easement-mortgage-and-dispute-reference", "name": "Possession, occupation, easement, mortgage and dispute reference", "description": "External factual or legal relationship references with authority, scope, time and non-ownership caveat.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "possession-occupation-easement-mortgage-and-dispute-reference-q01", "text": "What exact values, identifiers, geometry qualifiers and explicit unknowns must be recorded for possession, occupation, easement, mortgage and dispute reference?", "kind": "relationship", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "possession-occupation-easement-mortgage-and-dispute-reference-q02", "text": "Which register, surveyor, authority, source and evidence establishes possession, occupation, easement, mortgage and dispute reference, at what legal, observation and knowledge time, and with what accuracy?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "accuracy", "evidence" ] }, { "id": "possession-occupation-easement-mortgage-and-dispute-reference-q03", "text": "How may possession, occupation, easement, mortgage and dispute reference be validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring lifecycle?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "possession-occupation-easement-mortgage-and-dispute-reference-data", "name": "Possession, occupation, easement, mortgage and dispute reference data", "description": "Structured source-qualified data for possession, occupation, easement, mortgage and dispute reference.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "possession-occupation-easement-mortgage-and-dispute-reference-record", "name": "Possession, occupation, easement, mortgage and dispute reference record", "description": "Versioned evidence-bearing record for possession, occupation, easement, mortgage and dispute reference with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical parcel record", "survey or administrative evidence reference" ], "serial": true, "identity_strategy": "Parcel identifier plus possession-occupation-easement-mortgage-and-dispute-reference assertion or event identifier; address, owner, geometry, date and hash never identify the parcel alone.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null } ] }, { "id": "use-cover-planning-value-and-tax", "name": "Use, cover, planning, value and tax", "description": "Contextual projections owned by specialist systems.", "source_refs": [ "SRC-001", "SRC-004" ], "findings": [ { "id": "land-use-land-cover-zoning-permit-and-environmental-context", "name": "Land use, land cover, zoning, permit and environmental context", "description": "External classifications and regulated areas with version, authority, geometry relation, time and observed versus permitted distinction.", "source_refs": [ "SRC-004" ], "questions": [ { "id": "land-use-land-cover-zoning-permit-and-environmental-context-q01", "text": "What exact values, identifiers, geometry qualifiers and explicit unknowns must be recorded for land use, land cover, zoning, permit and environmental context?", "kind": "relationship", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "land-use-land-cover-zoning-permit-and-environmental-context-q02", "text": "Which register, surveyor, authority, source and evidence establishes land use, land cover, zoning, permit and environmental context, at what legal, observation and knowledge time, and with what accuracy?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "accuracy", "evidence" ] }, { "id": "land-use-land-cover-zoning-permit-and-environmental-context-q03", "text": "How may land use, land cover, zoning, permit and environmental context be validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring lifecycle?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "land-use-land-cover-zoning-permit-and-environmental-context-data", "name": "Land use, land cover, zoning, permit and environmental context data", "description": "Structured source-qualified data for land use, land cover, zoning, permit and environmental context.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004" ] } ], "artifacts": [ { "id": "land-use-land-cover-zoning-permit-and-environmental-context-record", "name": "Land use, land cover, zoning, permit and environmental context record", "description": "Versioned evidence-bearing record for land use, land cover, zoning, permit and environmental context with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical parcel record", "survey or administrative evidence reference" ], "serial": true, "identity_strategy": "Parcel identifier plus land-use-land-cover-zoning-permit-and-environmental-context assertion or event identifier; address, owner, geometry, date and hash never identify the parcel alone.", "source_refs": [ "SRC-004" ] } ], "inline_only_rationale": null }, { "id": "valuation-assessment-tax-charge-and-market-reference", "name": "Valuation, assessment, tax, charge and market reference", "description": "External valuation and fiscal records, basis, date, currency, assessed unit and appeal without treating value as intrinsic parcel identity.", "source_refs": [ "SRC-001" ], "questions": [ { "id": "valuation-assessment-tax-charge-and-market-reference-q01", "text": "What exact values, identifiers, geometry qualifiers and explicit unknowns must be recorded for valuation, assessment, tax, charge and market reference?", "kind": "relationship", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "valuation-assessment-tax-charge-and-market-reference-q02", "text": "Which register, surveyor, authority, source and evidence establishes valuation, assessment, tax, charge and market reference, at what legal, observation and knowledge time, and with what accuracy?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "accuracy", "evidence" ] }, { "id": "valuation-assessment-tax-charge-and-market-reference-q03", "text": "How may valuation, assessment, tax, charge and market reference be validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring lifecycle?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "valuation-assessment-tax-charge-and-market-reference-data", "name": "Valuation, assessment, tax, charge and market reference data", "description": "Structured source-qualified data for valuation, assessment, tax, charge and market reference.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001" ] } ], "artifacts": [ { "id": "valuation-assessment-tax-charge-and-market-reference-record", "name": "Valuation, assessment, tax, charge and market reference record", "description": "Versioned evidence-bearing record for valuation, assessment, tax, charge and market reference with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical parcel record", "survey or administrative evidence reference" ], "serial": true, "identity_strategy": "Parcel identifier plus valuation-assessment-tax-charge-and-market-reference assertion or event identifier; address, owner, geometry, date and hash never identify the parcel alone.", "source_refs": [ "SRC-001" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "interoperability-governance-and-agent-operations", "name": "Interoperability, governance and agent operations", "description": "Controls mappings, privacy and safe parcel maintenance.", "rationale": "Exchange must preserve CRS, topology, source authority, legal effect, lineage and mapping loss.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009" ], "layers": [ { "id": "profiles-projections-and-access", "name": "Profiles, projections and access", "description": "Versioned exchange and field-sensitive disclosure.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-008" ], "findings": [ { "id": "ladm-landinfra-inspire-gml-geosparql-and-geojson-projection", "name": "LADM, LandInfra, INSPIRE, GML, GeoSPARQL and GeoJSON projection", "description": "Pinned mappings, geometry roles, CRS treatment, omissions, transformed topology, validation and round-trip limits.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-008" ], "questions": [ { "id": "ladm-landinfra-inspire-gml-geosparql-and-geojson-projection-q01", "text": "What exact values, identifiers, geometry qualifiers and explicit unknowns must be recorded for ladm, landinfra, inspire, gml, geosparql and geojson projection?", "kind": "interoperability", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "ladm-landinfra-inspire-gml-geosparql-and-geojson-projection-q02", "text": "Which register, surveyor, authority, source and evidence establishes ladm, landinfra, inspire, gml, geosparql and geojson projection, at what legal, observation and knowledge time, and with what accuracy?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "accuracy", "evidence" ] }, { "id": "ladm-landinfra-inspire-gml-geosparql-and-geojson-projection-q03", "text": "How may ladm, landinfra, inspire, gml, geosparql and geojson projection be validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring lifecycle?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "ladm-landinfra-inspire-gml-geosparql-and-geojson-projection-data", "name": "LADM, LandInfra, INSPIRE, GML, GeoSPARQL and GeoJSON projection data", "description": "Structured source-qualified data for ladm, landinfra, 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-006", "SRC-008" ] } ], "artifacts": [ { "id": "ladm-landinfra-inspire-gml-geosparql-and-geojson-projection-record", "name": "LADM, LandInfra, INSPIRE, GML, GeoSPARQL and GeoJSON projection record", "description": "Versioned evidence-bearing record for ladm, landinfra, inspire, gml, geosparql and geojson projection with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical parcel record", "survey or administrative evidence reference" ], "serial": true, "identity_strategy": "Parcel identifier plus ladm-landinfra-inspire-gml-geosparql-and-geojson-projection assertion or event identifier; address, owner, geometry, date and hash never identify the parcel alone.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "public-map-owner-sensitive-source-and-restricted-boundary-view", "name": "Public map, owner-sensitive, source and restricted-boundary view", "description": "Purpose, audience, exposed identity and precision, masking, expiry, inference risk and legal authority.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "public-map-owner-sensitive-source-and-restricted-boundary-view-q01", "text": "What exact values, identifiers, geometry qualifiers and explicit unknowns must be recorded for public map, owner-sensitive, source and restricted-boundary view?", "kind": "access", "answer_data": [ "value or reference", "authority and version", "valid time", "unknowns" ] }, { "id": "public-map-owner-sensitive-source-and-restricted-boundary-view-q02", "text": "Which register, surveyor, authority, source and evidence establishes public map, owner-sensitive, source and restricted-boundary view, at what legal, observation and knowledge time, and with what accuracy?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "accuracy", "evidence" ] }, { "id": "public-map-owner-sensitive-source-and-restricted-boundary-view-q03", "text": "How may public map, owner-sensitive, source and restricted-boundary view be validated, contested, corrected, superseded, retained or disclosed without erasing history or importing a neighboring lifecycle?", "kind": "validation", "answer_data": [ "validation", "contest route", "successor", "access and retention" ] } ], "data_elements": [ { "id": "public-map-owner-sensitive-source-and-restricted-boundary-view-data", "name": "Public map, owner-sensitive, source and restricted-boundary view data", "description": "Structured source-qualified data for public map, owner-sensitive, source and restricted-boundary view.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "public-map-owner-sensitive-source-and-restricted-boundary-view-record", "name": "Public map, owner-sensitive, source and restricted-boundary view record", "description": "Versioned evidence-bearing record for public map, owner-sensitive, source and restricted-boundary view with authority, legal and knowledge time, provenance and access marking.", "media_or_form": [ "logical parcel record", "survey or administrative evidence reference" ], "serial": true, "identity_strategy": "Parcel identifier plus public-map-owner-sensitive-source-and-restricted-boundary-view assertion or event identifier; address, owner, geometry, date and hash never identify the parcel alone.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "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-001", "SRC-002", "SRC-005", "SRC-007", "SRC-009" ], "findings": [ { "id": "agent-operation-authority-purpose-preconditions-and-confirmation", "name": "Agent operation authority, purpose, preconditions and confirmation", "description": "Classifies create, survey-link, adjust, split, merge, register, disclose and retire actions as autonomous, propose, confirm or forbidden.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "agent-operation-authority-purpose-preconditions-and-confirmation-q01", "text": "What exact values, identifiers, 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, surveyor, authority, source and evidence establishes agent operation authority, purpose, preconditions and confirmation, at what legal, observation and knowledge time, and with what accuracy?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "accuracy", "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 importing a neighboring lifecycle?", "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-001", "SRC-002" ] } ], "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 parcel record", "survey or administrative evidence reference" ], "serial": true, "identity_strategy": "Parcel identifier plus agent-operation-authority-purpose-preconditions-and-confirmation assertion or event identifier; address, owner, geometry, date and hash never identify the parcel alone.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "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, authority, CRS, geometry, topology, area, time, lineage, interest, access and stale-head checks with rollback evidence.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-009" ], "questions": [ { "id": "prewrite-postwrite-validation-conflict-concurrency-and-recovery-q01", "text": "What exact values, identifiers, 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, surveyor, authority, source and evidence establishes pre-write and post-write validation, conflict, concurrency and recovery, at what legal, observation and knowledge time, and with what accuracy?", "kind": "evidence", "answer_data": [ "source", "authority", "times", "accuracy", "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 importing a neighboring lifecycle?", "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-001", "SRC-005", "SRC-007", "SRC-009" ] } ], "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 parcel record", "survey or administrative evidence reference" ], "serial": true, "identity_strategy": "Parcel identifier plus prewrite-postwrite-validation-conflict-concurrency-and-recovery assertion or event identifier; address, owner, geometry, date and hash never identify the parcel alone.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-009" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-parcel", "name": "Register parcel", "description": "Create authoritative parcel identity, class, jurisdiction and initial legal-effect state.", "inputs": [ "register", "identifier", "jurisdiction", "source" ], "outputs": [ "parcel revision" ], "preconditions": [ "authority and uniqueness validate" ], "effects": [ "parcel becomes resolvable" ], "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "attach-geometry", "name": "Attach parcel geometry", "description": "Append a role-qualified geometry with CRS, accuracy, source and time.", "inputs": [ "parcel", "geometry", "CRS", "source" ], "outputs": [ "geometry assertion" ], "preconditions": [ "CRS and authority validate" ], "effects": [ "geometry becomes queryable without overwriting alternatives" ], "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "id": "record-boundary-evidence", "name": "Record boundary evidence", "description": "Link points, segments, monuments, survey observations and instruments.", "inputs": [ "parcel", "boundary components", "survey" ], "outputs": [ "boundary evidence set" ], "preconditions": [ "survey and component identities resolve" ], "effects": [ "boundary reconstruction is attributable" ], "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "validate-topology-and-area", "name": "Validate topology and area", "description": "Check closure, validity, overlaps, gaps, adjacency and area reconciliation.", "inputs": [ "parcel revision", "profile", "tolerance" ], "outputs": [ "validation report" ], "preconditions": [ "CRS and geometry role known" ], "effects": [ "defects and uncertainty are explicit" ], "source_refs": [ "SRC-004", "SRC-005", "SRC-007" ] }, { "id": "propose-subdivision", "name": "Propose subdivision or consolidation", "description": "Create a change case with predecessor-successor topology and balance.", "inputs": [ "parcels", "change plan", "authority" ], "outputs": [ "proposed lineage graph" ], "preconditions": [ "current heads and rights references resolved" ], "effects": [ "proposal remains non-effective pending approval" ], "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "register-change", "name": "Register parcel change", "description": "Apply approved split, merge or reparcellation and preserve tombstones.", "inputs": [ "change case", "approval", "effective time" ], "outputs": [ "successor parcels and events" ], "preconditions": [ "topology, area and authority validate" ], "effects": [ "new identities become effective without erasing predecessors" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-009" ] }, { "id": "link-interest", "name": "Link external interest", "description": "Attach a title, right, restriction, responsibility or dispute reference.", "inputs": [ "parcel", "interest", "source" ], "outputs": [ "interest link" ], "preconditions": [ "external identity and scope resolve" ], "effects": [ "legal context is visible without ownership inference" ], "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "reconcile-geometry-assertions", "name": "Reconcile geometry assertions", "description": "Compare legal, surveyed, mapped and occupied boundaries and record disagreement.", "inputs": [ "geometry set", "evidence", "policy" ], "outputs": [ "reconciliation record" ], "preconditions": [ "sources and accuracy known" ], "effects": [ "no source is silently overwritten" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "issue-parcel-view", "name": "Issue parcel view", "description": "Create a purpose-bound cadastral, map or restricted projection with declared loss.", "inputs": [ "parcel revision", "target profile", "purpose" ], "outputs": [ "validated projection" ], "preconditions": [ "access, CRS and precision policy validate" ], "effects": [ "projection links source digest and omissions" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-008" ] }, { "id": "retire-parcel", "name": "Retire parcel", "description": "End a parcel through authorized lifecycle action while preserving lineage and tombstone.", "inputs": [ "parcel", "authority", "reason", "successors" ], "outputs": [ "retirement event" ], "preconditions": [ "holds and successor graph resolved" ], "effects": [ "future use is blocked while history remains citable" ], "source_refs": [ "SRC-001", "SRC-004" ] } ], "composition": [ { "target": "Party, Title, Right, Restriction, Responsibility, Address, Building, Survey, Planning, Valuation and Tax models", "relation": "REFERENCE", "purpose": "Link external legal, physical and administrative context without importing masters.", "required": true, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "ISO 19152 LADM", "relation": "ALIGN", "purpose": "Align spatial-unit, source, party and legal-interest references.", "required": true, "source_refs": [ "SRC-001" ] }, { "target": "OGC LandInfra and InfraGML", "relation": "ALIGN", "purpose": "Align land division, parcel, survey and interest projections.", "required": true, "source_refs": [ "SRC-002", "SRC-003" ] }, { "target": "INSPIRE Cadastral Parcels", "relation": "ALIGN", "purpose": "Project national cadastral reference, zoning, area, label, geometry and lifecycle metadata.", "required": false, "source_refs": [ "SRC-004" ] }, { "target": "GML, GeoSPARQL and GeoJSON", "relation": "ALIGN", "purpose": "Publish geometry and semantic-spatial views with CRS and mapping-loss declarations.", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-008" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Dimension identity, owner, cadastral authority, survey steward and namespace", "Parcel, spatial-source, administrative-source, point, interest, address, building, planning, valuation and lifecycle registries", "Master-system mappings for parcel, geometry, source, change-case and event identifiers", "Identity, CRS, survey, topology, registration, access, retention and agent-operation policies" ], "namespace_guidance": "Mint parcel and assertion identifiers only when no authoritative register identifier exists; keep parties, interests, addresses, buildings, surveys, planning and valuation as typed references.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md", "Dimension-local parcel, geometry, source, lineage and validation registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by authoritative parcel identifier, register and jurisdiction, never by address, owner, title, geometry, label, area, date or hash.", "Keep legal, surveyed, mapped and occupied geometry assertions distinct." ], "patch_rules": [ "Extensions declare parcel profile, target finding, source, authority, CRS, legal-effect and interoperability impact.", "Identity, legal boundary, lifecycle or rights semantics require successor version and migration lineage." ], "compatibility_rules": [ "Unknown additive fields may be ignored only when identity, CRS, geometry role, topology, source authority, legal effect and lineage remain intact.", "Every external projection pins versions and states loss and round-trip limits." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier for the parcel, qualified by register and jurisdiction.", "Governed globally resolvable parcel IRI with register binding.", "Dimension UUID or ULID when no external identifier exists." ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and offset or Z; separate survey, registration, legal-effect, observation and knowledge times.", "serial_naming_rule": "Use {parcel-id}--{artifact-kind}--{assertion-or-event-id}; never use address, owner, geometry, date or hash alone.", "integrity_rule": "Store digest, media type, issuer, source and profile versions, CRS, authority, valid and knowledge times, quality, licence and access marking." }, "policies": [ "Only competent authority may create legal-effect parcel identity or lifecycle state.", "Geometry, address, occupation, tax and title evidence never alone proves parcel identity or ownership.", "Source assertions remain attributable and disagreements remain visible.", "Agents may validate and propose; registration, legal change, interest mutation and wider disclosure require authority." ], "crud": { "read": [ "Resolve Dimension, register, jurisdiction, valid and knowledge time, geometry role, CRS and access purpose." ], "create": [ "Create identity, authority, class, source, status and explicit unknowns before geometry or interests." ], "update": [ "Append assertion or event with authority, reason, time, evidence and validation; never overwrite cited history." ], "delete": [ "Apply legal hold and retention; prefer retirement and tombstone and never cascade to sources or interests." ] }, "roles": [ { "name": "Cadastral authority", "responsibilities": [ "Own legal parcel identity, state and registration effect." ] }, { "name": "Licensed survey authority", "responsibilities": [ "Provide attributable boundary observations and quality." ] }, { "name": "Parcel registrar", "responsibilities": [ "Maintain identifiers, sources, geometry, state and lineage." ] }, { "name": "Rights registry steward", "responsibilities": [ "Master external title and interest records." ] }, { "name": "Geospatial quality steward", "responsibilities": [ "Validate CRS, topology, area and transformations." ] }, { "name": "Access and records steward", "responsibilities": [ "Apply disclosure, retention and audit policy." ] } ], "access": { "default_rule": "Deny mutation and sensitive disclosure unless register, role, purpose and field policy grant it; minimize identity and coordinate precision.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Statutory, judicial or emergency access cites authority and remains attributable and reviewable." ], "audit_requirements": [ "Log actor, agent, role, purpose, parcel, action, policy, RFC 3339 time, authority, affected scope and outcome." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read Dimension parcel, survey, CRS, registration, interest, access and retention policies.", "Read this model and linked party, interest, source, address, building, planning and valuation models before mutation." ] } }, "coverage": { "claim": "A source-grounded reviewable draft of a cadastral land parcel across ISO LADM, OGC LandInfra, InfraGML, GeoSPARQL and GML, INSPIRE Cadastral Parcels, EPSG, GeoJSON and RFC 3339, without universal legal-effect, jurisdictional-profile or certified crosswalk claims.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Register-qualified parcel identity, class, jurisdiction and aliases are explicit." }, { "dimension": "classification and definition", "status": "covered", "notes": "Spatial-unit level, dimensionality and neighboring concepts are separated." }, { "dimension": "direct properties", "status": "covered", "notes": "Geometry, boundary components, CRS, area and topology are first-class." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Survey points, monuments, observations, sources and accuracy support recognition." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Register, attach, validate, change, reconcile, project and retire operations are governed." }, { "dimension": "composition", "status": "covered", "notes": "Parties, interests, addresses, buildings, surveys, planning and valuation stay external." }, { "dimension": "lifecycle", "status": "covered", "notes": "Proposal, registration, split, merge, reparcellation, retirement and tombstone preserve lineage." }, { "dimension": "relationships", "status": "covered", "notes": "Neighbors, containment, interests, sources and successors are typed." }, { "dimension": "temporal", "status": "covered", "notes": "Survey, registration, legal-effect, observation and knowledge times remain distinct." }, { "dimension": "spatial", "status": "covered", "notes": "CRS, dimensionality, axis, epoch, precision, area and topology are covered." }, { "dimension": "provenance", "status": "covered", "notes": "Spatial and administrative sources, transformations and disagreements are attributable." }, { "dimension": "ownership and stewardship", "status": "covered", "notes": "Cadastral, survey, rights and context masters remain separate." }, { "dimension": "validation and quality", "status": "covered", "notes": "CRS, geometry, topology, area, authority, accuracy and stale-head checks are explicit." }, { "dimension": "access and privacy", "status": "covered", "notes": "Purpose views, owner-sensitive data and coordinate masking are covered." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Legal hold, predecessor history, source preservation and tombstones are explicit." }, { "dimension": "interoperability", "status": "covered", "notes": "LADM, LandInfra, InfraGML, INSPIRE, GML, GeoSPARQL and GeoJSON are loss-aware." } ], "known_omissions": [ "Claude and Grok provided no valid result; later cadastral review is required.", "Jurisdiction-specific legal effect, 3D parcels, strata, customary tenure, marine and informal tenure need profiles.", "Approved registry relations for WM-PLC-002 are absent and proposed composition remains draft.", "Certified crosswalks and conformance fixtures remain unverified." ], "conflicts": [ "Legal, surveyed, mapped and occupied boundaries can disagree.", "Parcel, title, ownership, address, site and land use are non-equivalent.", "GeoJSON cannot preserve every native CRS, topology or 3D cadastral semantic." ], "regional_assumptions": [ "INSPIRE is a European profile.", "LADM and LandInfra provide concepts but do not create jurisdictional legal effect.", "Register authority controls canonical state in each jurisdiction." ], "adversarial_checks": [ "Reject identity from address, owner or geometry alone.", "Reject geometry without CRS, role, source, time and quality.", "Reject split or merge without predecessor-successor lineage and authority.", "Reject ownership inferred from parcel or possession.", "Reject agent legal registration or interest mutation without confirmation authority." ] }, "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 land-administration spatial unit", "rationale": "The parcel owns register-qualified identity, geometry and boundary assertions, area, topology, source quality and lifecycle. Parties, titles, rights, addresses, buildings, surveys, planning, valuation and tax remain external masters." }, "decisions": [ { "concept": "Parcel identity", "disposition": "accepted as register and jurisdiction qualified", "rationale": "Address, owner, title, label, geometry, area and map reference are mutable or non-unique and cannot replace the authoritative parcel identifier." }, { "concept": "Parcel versus legal interest", "disposition": "accepted as separate models", "rationale": "A parcel is a spatial unit; title, ownership, possession, rights, restrictions, responsibilities and mortgages are external legal relationships." }, { "concept": "Competing boundaries", "disposition": "accepted as separately attributable assertions", "rationale": "Legal, surveyed, mapped and occupied boundaries may disagree and none may silently overwrite the others." }, { "concept": "Coordinate semantics", "disposition": "accepted as mandatory direct qualifiers", "rationale": "CRS, axis order, coordinate epoch, transformation, dimensionality, precision and accuracy are necessary to interpret geometry and area." }, { "concept": "Topology and area", "disposition": "accepted with profile-specific validation", "rationale": "Closure, overlaps, gaps, adjacency, containment and official versus calculated area require declared tolerances, methods and authority." }, { "concept": "Parcel lifecycle", "disposition": "accepted as successor graph", "rationale": "Subdivision, consolidation and reparcellation create or retire identities and preserve predecessor, successor, area-balance and legal-effect history." }, { "concept": "Geospatial projections", "disposition": "accepted as loss-aware views", "rationale": "LADM, LandInfra, InfraGML, INSPIRE, GML, GeoSPARQL and GeoJSON mappings pin versions and disclose CRS, topology, 3D and legal-semantic loss." }, { "concept": "Approved registry composition", "disposition": "held pending relation governance", "rationale": "The approved relation ledger contains no WM-PLC-002 rows, so proposed links to legal, physical and administrative models 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-002 rows, so all proposed sibling composition remains draft.", "Jurisdiction-specific legal effect, 3D and strata parcels, customary tenure, informal tenure, marine cadastre, adverse possession and boundary-dispute profiles require specialist review.", "Certified LADM, LandInfra, InfraGML, INSPIRE, GML, GeoSPARQL, EPSG 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 model identifiers and cardinalities for parties, interests, addresses, buildings, surveys, planning, valuation and tax.", "Develop jurisdiction and specialist profiles for 2D, 3D, strata, customary, informal and marine parcels.", "Create fixtures for wrong-CRS geometry, antimeridian, overlaps, gaps, area discrepancy, boundary conflict, split, merge and retroactive legal effect.", "Validate certified cadastral and geometry projections with CRS, topology, precision, loss and round-trip tests." ] }, "statistics": { "sources": 9, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }