{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-plc-001","code":"wm-plc-001-terrain-landform","url":"https://ver.cy/models/wm-plc-001-terrain-landform/","name":"Terrain / Landform","alternateNames":["P1"],"kind":"world-model","status":"published","version":"1.0.0-reviewable-draft","language":"en","classifiers":{"family":"World Models","category":"Physical world and living systems","entryKind":"aggregate","plane":"","domain":["PHY.PLC.REL"],"industry":["Cross-industry"],"navPath":"NAV.PHY.PLC.REL","tags":["terrain","landform","phy.plc.rel"],"facets":{}},"whatItIs":"A terrain context aggregate for one explicitly bounded area and adopting stewardship scope. It groups independently identified surface products, observations and landform assertions; it is not a land parcel, survey campaign, global gazetteer or a claim that a dataset is the physical ground. Root membership and revisions are local, while referenced products and features retain their master identities. All operations and field groups are proposed design, not an executable implementation.","purpose":"Describe the physical relief of a bounded territory through qualified elevation representations, derived terrain measures and delineated landforms.","scope":{"in":["Terrain context identity, coverage footprints and explicit reference frames","Ground relief representations, observation lineage, morphometry, uncertainty and qualified change assertions","Natural and anthropogenic landform delineation, classification assertions, external names and scale-dependent relationships","Local revisions, artifact integrity and controlled exchange with neighboring models"],"out":["Land rights, cadastral boundaries, water dynamics, soil profiles, geological volumes, settlements, infrastructure assets and hazard evaluation","Raw survey instrument control, geodetic datum administration, official naming decisions and classifier governance","Operational engineering certification, earthworks, automatic causal attribution and safety decisions","Detailed marine hydrography, submerged relief validation, glacier mass balance and volumetric cave or overhang modelling; these require explicit extensions"],"boundaries":[{"neighbor":"WM-PLC-002 Land Parcel","distinction":"A terrain footprint may cross or intersect parcels. Terrain stewardship does not confer land ownership, cadastral authority or survey access rights."},{"neighbor":"WM-PLC-003 Water Body","distinction":"Ground geometry and water-related masks may be linked; water level, flow, catchment simulation and hydrological enforcement rules are externally mastered. A water surface is not automatically the ground below it."},{"neighbor":"WM-EAR-003 Soil and WM-EAR-005 Natural Hazard","distinction":"Terrain properties may inform these subjects without absorbing soil profiles, geotechnical stability, causal hazard assessment or consequence decisions."},{"neighbor":"WM-PLC-005 Settlement / Urban Form and WM-BLT-003 Infrastructure Network","distinction":"Anthropogenic relief may be described without owning buildings, works, networks or their operation. Above-ground surfaces remain explicitly labelled contextual observations."},{"neighbor":"WM-XCT-010 Location Referencing / Address","distinction":"Reference frame and location bindings are external references; local terrain records preserve CRS identifiers and transformation evidence, without governing addresses or geodetic registries."},{"neighbor":"External surveys, elevation products, landform vocabularies and gazetteers","distinction":"This aggregate owns membership and terrain assertions only. No requirement that every product has one campaign, every feature has one class, every spot height is monumented, or every landform is officially named."}]},"distinguishingFeatures":["Unlike WM-PLC-002 Land Parcel: A terrain footprint may cross or intersect parcels. Terrain stewardship does not confer land ownership, cadastral authority or survey access rights.","Unlike WM-PLC-003 Water Body: Ground geometry and water-related masks may be linked; water level, flow, catchment simulation and hydrological enforcement rules are externally mastered. A water surface is not automatically the ground below it.","Unlike WM-EAR-003 Soil and WM-EAR-005 Natural Hazard: Terrain properties may inform these subjects without absorbing soil profiles, geotechnical stability, causal hazard assessment or consequence decisions.","Unlike WM-PLC-005 Settlement / Urban Form and WM-BLT-003 Infrastructure Network: Anthropogenic relief may be described without owning buildings, works, networks or their operation. Above-ground surfaces remain explicitly labelled contextual observations.","Unlike WM-XCT-010 Location Referencing / Address: Reference frame and location bindings are external references; local terrain records preserve CRS identifiers and transformation evidence, without governing addresses or geodetic registries.","Unlike External surveys, elevation products, landform vocabularies and gazetteers: This aggregate owns membership and terrain assertions only. No requirement that every product has one campaign, every feature has one class, every spot height is monumented, or every landform is officially named."],"structure":{"bundles":[{"id":"terrain-context","name":"Terrain identity and extent","description":"Local terrain context and its spatial scope.","layers":[{"id":"terrain-context-identity","name":"Context identity","description":"Proposed root identity binds an area and stewardship purpose. Surface products and physical features keep distinct identifiers; a renamed area does not silently replace them.","findings":[{"id":"terrain-terrain-subject","name":"Bounded terrain subject","description":"Proposed root identity binds an area and stewardship purpose. Surface products and physical features keep distinct identifiers; a renamed area does not silently replace them.","questions":[{"text":"Which master identifier and subject boundary distinguish this terrain context from its component datasets?","id":"terrain-terrain-subject-q01","kind":"identity"},{"text":"Which steward maintains this context and what authority is explicitly excluded?","id":"terrain-terrain-subject-q02","kind":"ownership"},{"text":"Which surface and landform versions are members of this context?","id":"terrain-terrain-subject-q03","kind":"composition"}]}]},{"id":"terrain-context-extent","name":"Spatial extent","description":"Proposed extent records distinguish study area, dataset envelope, valid observation support and landform geometry. Holes, tile overlap, clipping and scale remain explicit.","findings":[{"id":"terrain-coverage-footprint","name":"Coverage and spatial support","description":"Proposed extent records distinguish study area, dataset envelope, valid observation support and landform geometry. Holes, tile overlap, clipping and scale remain explicit.","questions":[{"text":"What exact area and coordinate reference system define the terrain context footprint?","id":"terrain-coverage-footprint-q01","kind":"spatial"},{"text":"Where do nodata areas, excluded regions or overlapping tiles limit actual terrain coverage?","id":"terrain-coverage-footprint-q02","kind":"constraint"},{"text":"At what scale and tolerance are containment or adjacency assertions evaluated?","id":"terrain-coverage-footprint-q03","kind":"relationship"}]}]}]},{"id":"terrain-observations","name":"Reference frames and observations","description":"The frame and evidence through which terrain is observed.","layers":[{"id":"terrain-observations-reference-frame","name":"Coordinate and height frame","description":"Proposed height assertions preserve horizontal and vertical semantics, units and applicable epochs. Transformation records are evidence-bearing derivations, not unexplained changes to coordinates.","findings":[{"id":"terrain-qualified-height","name":"Qualified height reference","description":"Proposed height assertions preserve horizontal and vertical semantics, units and applicable epochs. Transformation records are evidence-bearing derivations, not unexplained changes to coordinates.","questions":[{"text":"Which height or depth quantity, unit, vertical reference and axis convention apply?","id":"terrain-qualified-height-q01","kind":"measurement"},{"text":"Which coordinate epoch or reference realization applies, and which time values are unknown?","id":"terrain-qualified-height-q02","kind":"temporal"},{"text":"What authorized transformation connects the input and output frames and where is it valid?","id":"terrain-qualified-height-q03","kind":"interoperability"}]}]},{"id":"terrain-observations-acquisition","name":"Observation lineage","description":"Proposed recognition evidence connects surfaces to surveys, interpreted imagery, measured points or prior products. Mosaics can involve several acquisitions; missing lineage is explicit. An observation is distinct from an inference about bare ground.","findings":[{"id":"terrain-observation-support","name":"Acquisition and recognition evidence","description":"Proposed recognition evidence connects surfaces to surveys, interpreted imagery, measured points or prior products. Mosaics can involve several acquisitions; missing lineage is explicit. An observation is distinct from an inference about bare ground.","questions":[{"text":"Which observations and processing activities support this surface revision?","id":"terrain-observation-support-q01","kind":"provenance"},{"text":"When was each area observed and when was its evidence ingested?","id":"terrain-observation-support-q02","kind":"temporal"},{"text":"What evidence supports treating the observed surface as ground rather than canopy, structure, snow or water?","id":"terrain-observation-support-q03","kind":"evidence"}]}]}]},{"id":"terrain-surface","name":"Elevation representation and quality","description":"Terrain representation and the limits of its use.","layers":[{"id":"terrain-surface-representation","name":"Surface representation","description":"Proposed product descriptors distinguish grid, TIN, point, contour and breakline representations. Terrain, surface and mixed interpretations must be stated explicitly; a single-valued height field cannot describe every physical shape.","findings":[{"id":"terrain-surface-kind","name":"Representation and surface meaning","description":"Proposed product descriptors distinguish grid, TIN, point, contour and breakline representations. Terrain, surface and mixed interpretations must be stated explicitly; a single-valued height field cannot describe every physical shape.","questions":[{"text":"What representation and surface interpretation does the product actually provide?","id":"terrain-surface-kind-q01","kind":"definition"},{"text":"What sampling, grid registration, interpolation and unit rules define its values?","id":"terrain-surface-kind-q02","kind":"measurement"},{"text":"Which areas or shapes cannot be represented faithfully by the selected surface form?","id":"terrain-surface-kind-q03","kind":"exception"}]}]},{"id":"terrain-surface-quality","name":"Quality and fitness","description":"Proposed fitness assessment records tested accuracy, completeness and intended use separately from sample spacing. Acceptance criteria must be supplied by the adopting profile; no universal engineering threshold is inferred.","findings":[{"id":"terrain-accuracy-support","name":"Accuracy and fitness evidence","description":"Proposed fitness assessment records tested accuracy, completeness and intended use separately from sample spacing. Acceptance criteria must be supplied by the adopting profile; no universal engineering threshold is inferred.","questions":[{"text":"What horizontal and vertical accuracy evidence was measured and over which terrain conditions?","id":"terrain-accuracy-support-q01","kind":"quality"},{"text":"Which completeness, seam and consistency checks pass or fail for this revision?","id":"terrain-accuracy-support-q02","kind":"validation"},{"text":"Which intended uses are supported, restricted or unassessed by that evidence?","id":"terrain-accuracy-support-q03","kind":"requirement"}]}]}]},{"id":"terrain-analysis","name":"Morphometry and change","description":"Derived shape measures and qualified differences through time.","layers":[{"id":"terrain-analysis-morphometry","name":"Terrain derivatives","description":"Proposed derived measures retain source versions and algorithm conventions. Slope, aspect, curvature, roughness and relative relief require named definitions and spatial support; parameters from one method are not universal.","findings":[{"id":"terrain-derived-measure","name":"Reproducible morphometry","description":"Proposed derived measures retain source versions and algorithm conventions. Slope, aspect, curvature, roughness and relative relief require named definitions and spatial support; parameters from one method are not universal.","questions":[{"text":"What quantity, unit and convention define this terrain derivative?","id":"terrain-derived-measure-q01","kind":"measurement"},{"text":"Which input version, algorithm, neighborhood and resolution produced the measure?","id":"terrain-derived-measure-q02","kind":"process"},{"text":"How are edges, nodata, vertical scaling and unstable estimates handled?","id":"terrain-derived-measure-q03","kind":"constraint"}]}]},{"id":"terrain-analysis-change","name":"Surface comparison","description":"Proposed change assertions separate observed differences from physical change and inferred cause. Co-registration, comparable surface meaning, uncertainty and temporal support precede interpretation; a lack of detectable difference is not proof of no change.","findings":[{"id":"terrain-qualified-change","name":"Qualified terrain change","description":"Proposed change assertions separate observed differences from physical change and inferred cause. Co-registration, comparable surface meaning, uncertainty and temporal support precede interpretation; a lack of detectable difference is not proof of no change.","questions":[{"text":"Which two spatially qualified observation epochs and surface revisions are compared?","id":"terrain-qualified-change-q01","kind":"temporal"},{"text":"How do alignment, bias and correlated errors affect the change detection criterion?","id":"terrain-qualified-change-q02","kind":"quality"},{"text":"Is the result a supported change, an unresolved difference or insufficient evidence, and is any cause separately supported?","id":"terrain-qualified-change-q03","kind":"decision"}]}]}]},{"id":"terrain-landforms","name":"Landform inventory","description":"Delineated features, their interpretations and qualified names.","layers":[{"id":"terrain-landforms-classification","name":"Geomorphic classification","description":"Proposed assertions link a persistent feature to a versioned vocabulary and diagnostic evidence. Natural or anthropogenic origin is qualified; multiple schemes and disputed interpretations may coexist without forcing one global class.","findings":[{"id":"terrain-landform-interpretation","name":"Landform classification assertion","description":"Proposed assertions link a persistent feature to a versioned vocabulary and diagnostic evidence. Natural or anthropogenic origin is qualified; multiple schemes and disputed interpretations may coexist without forcing one global class.","questions":[{"text":"Which vocabulary revision and diagnostic criteria support each landform class assertion?","id":"terrain-landform-interpretation-q01","kind":"classification"},{"text":"What confidence and review status distinguish accepted, provisional and disputed interpretations?","id":"terrain-landform-interpretation-q02","kind":"state"},{"text":"Which scale, mixed origin or local terminology prevents a direct class mapping?","id":"terrain-landform-interpretation-q03","kind":"exception"}]}]},{"id":"terrain-landforms-feature","name":"Feature identity and delineation","description":"Proposed feature records separate persistent feature identity, geometry revisions and names. A summit point, a bounding box and a full landform extent have different roles. Local names do not acquire official status through inclusion.","findings":[{"id":"terrain-landform-extent","name":"Feature extent and names","description":"Proposed feature records separate persistent feature identity, geometry revisions and names. A summit point, a bounding box and a full landform extent have different roles. Local names do not acquire official status through inclusion.","questions":[{"text":"Which master feature identity persists across alternative names and revised outlines?","id":"terrain-landform-extent-q01","kind":"identity"},{"text":"What geometry role, delineation method and scale define the landform extent?","id":"terrain-landform-extent-q02","kind":"spatial"},{"text":"Which name source, language, community attribution and approval status apply to each name?","id":"terrain-landform-extent-q03","kind":"authority"}]}]}]},{"id":"terrain-continuity","name":"Continuity and exchange","description":"Controlled revision and reuse of the terrain context.","layers":[{"id":"terrain-continuity-revision","name":"Revision and retirement","description":"Proposed local lifecycle separates an amended record from altered physical terrain. Supersession, feature split or merge and withdrawn evidence preserve directed lineage and do not mutate externally mastered products.","findings":[{"id":"terrain-revision-continuity","name":"Terrain record continuity","description":"Proposed local lifecycle separates an amended record from altered physical terrain. Supersession, feature split or merge and withdrawn evidence preserve directed lineage and do not mutate externally mastered products.","questions":[{"text":"What change created this context revision and how does it supersede or relate to earlier records?","id":"terrain-revision-continuity-q01","kind":"lifecycle"},{"text":"Which retention policy governs retired terrain artifacts and what may be deleted?","id":"terrain-revision-continuity-q02","kind":"retention"},{"text":"How are the exact bytes, producer and interpretation history of a terrain artifact preserved?","id":"terrain-revision-continuity-q03","kind":"provenance"}]}]},{"id":"terrain-continuity-exchange","name":"Neighbor bindings and access","description":"Proposed exports bind terrain versions to consumers with explicit limitations. They preserve uncertainty and lineage, enforce the adopting policy and report mapping loss. Publishing a terrain extract neither grants land access nor validates a downstream hazard decision.","findings":[{"id":"terrain-qualified-exchange","name":"Qualified reuse and access","description":"Proposed exports bind terrain versions to consumers with explicit limitations. They preserve uncertainty and lineage, enforce the adopting policy and report mapping loss. Publishing a terrain extract neither grants land access nor validates a downstream hazard decision.","questions":[{"text":"Which neighboring model instances consume this terrain revision and for which bounded purpose?","id":"terrain-qualified-exchange-q01","kind":"relationship"},{"text":"Which audience, license and resolution limits apply to the requested terrain extract?","id":"terrain-qualified-exchange-q02","kind":"access"},{"text":"Which target profile, CRS mapping and lost semantics accompany the exported representation?","id":"terrain-qualified-exchange-q03","kind":"interoperability"}]}]}]}]},"agentConduct":{"may":["Register terrain context: Create a proposed local context revision and membership bindings. Proposed operation only; no runtime implementation is claimed.","Assess surface admission: Check a supplied product descriptor for terrain interpretation and evidence completeness. Proposed operation only; no runtime implementation is claimed.","Propose morphometry derivation: Prepare a reproducible local derivation specification and record a separately supplied result. Proposed operation only; no runtime implementation is claimed.","Assess terrain difference evidence: Evaluate supplied comparison evidence against an explicit detection rule. Proposed operation only; no runtime implementation is claimed.","Revise landform assertion: Propose a new delineation, classification or name assertion against the same feature identity. Proposed operation only; no runtime implementation is claimed.","Prepare governed terrain extract: Specify a permitted view with versioned dependencies and mapping losses. Proposed operation only; no runtime implementation is claimed."],"mustNot":["Never erase disputed local names or classifications merely to make an export appear definitive.","Deny access unless the adopting policy permits the subject, audience, purpose and requested resolution."],"requiresHuman":[]},"ethics":{"considerations":[],"affectedParties":[]},"owners":{"steward":"A role-based terrain steward with a bounded maintenance mandate, distinct from land ownership.","roles":[{"name":"Terrain steward","responsibilities":["Maintains scope, memberships, namespace and accountable review routes without owning land rights."]},{"name":"Survey evidence custodian","responsibilities":["Provides acquisition references and explains known measurement limits; does not approve every downstream use."]},{"name":"Geomorphology reviewer","responsibilities":["Reviews delineations, criteria and disputed landform interpretations at a stated scale."]},{"name":"Geospatial quality reviewer","responsibilities":["Assesses frames, transformations, uncertainty, method compatibility and fitness evidence."]},{"name":"Access and records custodian","responsibilities":["Applies licenses, release limits, retention and authorized disposal with audit references."]},{"name":"Consumer","responsibilities":["Uses only qualified, permitted views and preserves limitations in downstream bindings."]}],"masterSystems":[]},"relations":[{"target":"WM-PLC-002","type":"references","note":"Optional parcel binding for spatial context; rights and cadastral lifecycle remain external."},{"target":"WM-PLC-003","type":"references","note":"Optional water-body context and masks; no ownership of hydrological simulation or water level."},{"target":"WM-EAR-003","type":"references","note":"Optional soil consumer or contextual feature; only terrain metrics and version bindings are local."},{"target":"WM-EAR-005","type":"references","note":"Optional hazard assessment consumer; terrain evidence is not a hazard determination."},{"target":"WM-PLC-005","type":"references","note":"Optional settlement context; settlement identity and built form remain external."},{"target":"WM-BLT-003","type":"references","note":"Optional infrastructure context and terrain version binding; no network lifecycle or actuation."},{"target":"WM-XCT-010","type":"references","note":"Optional location binding; addresses and location master administration are external."},{"target":"INSPIRE Elevation D2.8.II.1 2024-01-31","type":"aligned","note":"Conceptual elevation representation and reference frame mapping only; no conformance certification."},{"target":"OGC GeoSPARQL 1.1","type":"aligned","note":"Conceptual feature, geometry and spatial predicate mapping; executable binding remains deferred."},{"target":"PROV-O 2013-04-30","type":"aligned","note":"Conceptual derivation and revision mapping; provenance does not establish measurement truth."},{"target":"WM-PLC-002 Land Parcel","type":"neighbor","note":"A terrain footprint may cross or intersect parcels. Terrain stewardship does not confer land ownership, cadastral authority or survey access rights."},{"target":"WM-PLC-003 Water Body","type":"neighbor","note":"Ground geometry and water-related masks may be linked; water level, flow, catchment simulation and hydrological enforcement rules are externally mastered. A water surface is not automatically the ground below it."},{"target":"WM-EAR-003 Soil and WM-EAR-005 Natural Hazard","type":"neighbor","note":"Terrain properties may inform these subjects without absorbing soil profiles, geotechnical stability, causal hazard assessment or consequence decisions."},{"target":"WM-PLC-005 Settlement / Urban Form and WM-BLT-003 Infrastructure Network","type":"neighbor","note":"Anthropogenic relief may be described without owning buildings, works, networks or their operation. Above-ground surfaces remain explicitly labelled contextual observations."},{"target":"WM-XCT-010 Location Referencing / Address","type":"neighbor","note":"Reference frame and location bindings are external references; local terrain records preserve CRS identifiers and transformation evidence, without governing addresses or geodetic registries."},{"target":"External surveys, elevation products, landform vocabularies and gazetteers","type":"neighbor","note":"This aggregate owns membership and terrain assertions only. No requirement that every product has one campaign, every feature has one class, every spot height is monumented, or every landform is officially named."}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system identifier","Governed global identifier or IRI","UUID or ULID issued by the adopting Dimension"]},"properties":{"applicability":"required","items":[]},"recognition":{"applicability":"required","items":[]},"capabilities":{"applicability":"required","items":["Register terrain context: Create a proposed local context revision and membership bindings. Proposed operation only; no runtime implementation is claimed.","Assess surface admission: Check a supplied product descriptor for terrain interpretation and evidence completeness. Proposed operation only; no runtime implementation is claimed.","Propose morphometry derivation: Prepare a reproducible local derivation specification and record a separately supplied result. Proposed operation only; no runtime implementation is claimed.","Assess terrain difference evidence: Evaluate supplied comparison evidence against an explicit detection rule. Proposed operation only; no runtime implementation is claimed.","Revise landform assertion: Propose a new delineation, classification or name assertion against the same feature identity. Proposed operation only; no runtime implementation is claimed.","Prepare governed terrain extract: Specify a permitted view with versioned dependencies and mapping losses. Proposed operation only; no runtime implementation is claimed."]},"hazards":{"applicability":"required","items":[]},"interfaces":{"applicability":"required","items":["OGC GeoSPARQL - A Geographic Query Language for RDF Data","PROV-O: The PROV Ontology"]},"context":{"applicability":"required","items":["INSPIRE is a European interoperability example; its regional reference frames and thresholds are not universal requirements.","The soil field book and domestic naming page are United States examples. Local vocabularies and naming authority must be supplied elsewhere.","The glacier change paper supplies methodological cautions; transferring its technique to another terrain or sensor requires validation."]}},"sources":[{"title":"INSPIRE Data Specification on Elevation - Technical Guidelines","url":"https://knowledge-base.inspire.ec.europa.eu/document/download/02a50782-5cb5-4c51-a7d9-b38791b0ef51_en","note":"European Commission, INSPIRE Maintenance and Implementation Group"},{"title":"Field Book for Describing and Sampling Soils, Version 4.0","url":"https://www.nrcs.usda.gov/sites/default/files/2025-05/Field-Book-for-Describing-and-Sampling-Soils-Ver4.pdf","note":"USDA Natural Resources Conservation Service"},{"title":"r.slope.aspect manual","url":"https://grass.osgeo.org/grass-stable/manuals/r.slope.aspect.html","note":"GRASS development team"},{"title":"OGC GeoSPARQL - A Geographic Query Language for RDF Data","url":"https://docs.ogc.org/is/22-047r1/22-047r1.html","note":"Open Geospatial Consortium"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"World Wide Web Consortium"},{"title":"Co-registration and bias corrections of satellite elevation data sets for quantifying glacier thickness change","url":"https://tc.copernicus.org/articles/5/271/2011/","note":"University of Oslo, Department of Geosciences"},{"title":"Domestic Names","url":"https://www.usgs.gov/us-board-on-geographic-names/domestic-names","note":"U.S. Board on Geographic Names"}],"openQuestions":["Complete source HTTP, document-version, license and independent claim checks without equating a successful response to substantive verification.","Develop and validate regional CRS, classification, name and use profiles, with explicit decisions about submerged, ice and volumetric extensions.","Build executable nested schemas and fixtures covering unknown frames, mixed surfaces, mosaics, nodata, correlated errors, geometry revisions, disputed names and restricted exports.","Restore independent external review before any canonical or publishable-draft promotion.","No executable nested data schema, terrain calculation, coordinate transformation engine or numerical acceptance fixtures.","No exhaustive global landform vocabulary, disputed-name adjudication or tested cross-cultural naming profile.","Detailed bathymetry, dynamic ice surfaces and volumetric overhangs or caves require separate extensions and evidence.","No direct HTTP source status was measured in this run; no assertion of complete source currency or independent review."],"resources":{"spec":"/models/wm-plc-001-terrain-landform/spec.yaml","agents":"/models/wm-plc-001-terrain-landform/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-plc-001"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-plc-001-terrain-landform/spec.yaml"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-10-06T22:50:49Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"derived","structure":"filled","agentConduct":"derived","ethics":"missing","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"missing","interaction.recognition":"missing","interaction.capabilities":"filled","interaction.hazards":"missing","interaction.interfaces":"derived","interaction.context":"filled","sources":"filled"},"notes":{"distinguishingFeatures":"Derived from boundary notes against neighbouring models.","agentConduct":"Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such."},"score":0.676}}