{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-blt-005","code":"wm-blt-005-civil-works","url":"https://ver.cy/models/wm-blt-005-civil-works/","name":"Civil Works","alternateNames":["U1"],"kind":"world-model","status":"published","version":"0.1.0-reviewable","language":"en","classifiers":{"family":"World Models","category":"Physical world and living systems","entryKind":"entity","plane":"","domain":["PHY.BLT.CIV"],"industry":["Cross-industry"],"navPath":"NAV.PHY.BLT.CIV","tags":["civil","works","phy.blt.civ"],"facets":{}},"whatItIs":"One civil infrastructure asset or explicitly bounded work, including engineered ground and site works. A proposed asset can be recorded before it exists; existence, completion, acceptance and service state are separate assertions. The root persists across record revisions and interventions. Multiple parts do not turn the root into a project portfolio. This proposed Vercy boundary is narrower than the legacy U1 building-and-structure umbrella.","purpose":"Describe one enduring civil infrastructure work as an identifiable physical asset, with its extent, engineered fabric, intended function, observed condition and evidence-backed history.","scope":{"in":["Stable work identity, classification, responsibility references and correspondence to external asset records.","Asset extent, referenced survey or alignment, constituent parts and qualified physical properties.","Intended service capability and constraints, inspection evidence, maintenance needs and referenced interventions.","Evidence-backed lifecycle assertions, source lineage, exchange profiles and governed disclosure of this asset record."],"out":["Construction project scheduling, procurement, payment, contractor management or execution of works.","Generic building envelopes and structural calculations, operational facility management, site administration, network topology and route linear-referencing masters.","Land title, cadastral boundary adjudication, permit issuance, engineering certification, emergency command or physical actuation.","Detailed geotechnical, hydraulic, pavement, bridge, dam or tunnel design rules and autonomous safety decisions."],"boundaries":[{"neighbor":"WM-BLT-001 Building / Structure","distinction":"Generic structural fabric stays in the structural asset master. A bridge or retaining structure may have one master identity with two governed views, or a referenced component identity within a larger civil asset. Do not create duplicate real-world assets merely to populate both cards."},{"neighbor":"WM-BLT-007 Construction Work","distinction":"Projects create, modify or remove an asset. This record carries intervention and acceptance references but never owns work-package execution, contractual completion or certification."},{"neighbor":"WM-BLT-006 Facility and WM-BLT-008 Site / Campus","distinction":"Functional operations and site aggregation remain external. An IFC facility class is an exchange concept and is not proof that these Vercy boundaries are identical."},{"neighbor":"WM-BLT-003 Infrastructure Network, WM-BLT-009 Linear Infrastructure Asset and WM-BLT-010 Utility Network Topology","distinction":"Keep network membership, carried services and alignment references. Connectivity, routing, chainage calibration and topology state have external masters; a culvert or embankment is not automatically a network edge."},{"neighbor":"Land, ownership, survey and environmental records","distinction":"Record spatial association and responsible-party authority references, not title or an inferred right to alter land. Natural terrain is context unless an engineered intervention is evidenced; adjacent receptors and permit restrictions remain external evidence."}]},"distinguishingFeatures":["Unlike WM-BLT-001 Building / Structure: Generic structural fabric stays in the structural asset master. A bridge or retaining structure may have one master identity with two governed views, or a referenced component identity within a larger civil asset. Do not create duplicate real-world assets merely to populate both cards.","Unlike WM-BLT-007 Construction Work: Projects create, modify or remove an asset. This record carries intervention and acceptance references but never owns work-package execution, contractual completion or certification.","Unlike WM-BLT-006 Facility and WM-BLT-008 Site / Campus: Functional operations and site aggregation remain external. An IFC facility class is an exchange concept and is not proof that these Vercy boundaries are identical.","Unlike WM-BLT-003 Infrastructure Network, WM-BLT-009 Linear Infrastructure Asset and WM-BLT-010 Utility Network Topology: Keep network membership, carried services and alignment references. Connectivity, routing, chainage calibration and topology state have external masters; a culvert or embankment is not automatically a network edge.","Unlike Land, ownership, survey and environmental records: Record spatial association and responsible-party authority references, not title or an inferred right to alter land. Natural terrain is context unless an engineered intervention is evidenced; adjacent receptors and permit restrictions remain external evidence."],"structure":{"bundles":[{"id":"identity-stewardship","name":"Identity and stewardship","description":"Identify the asset and accountable roles without deriving ownership from a data export.","layers":[{"id":"identity-layer","name":"Work identity and class","description":"A proposed identity crosswalk distinguishes the physical work, its record revisions and any project that changes it.","findings":[{"id":"identity-finding","name":"Work identity and class","description":"A proposed identity crosswalk distinguishes the physical work, its record revisions and any project that changes it.","questions":[{"text":"Which master identifier denotes this civil work and which aliases refer to the same asset?","id":"identity-question-1","kind":"identity"},{"text":"Which civil asset class and inclusion boundary apply to this occurrence?","id":"identity-question-2","kind":"classification"},{"text":"How is a proposed, abandoned or partly built work distinguished from an existing accepted asset?","id":"identity-question-3","kind":"exception"}]}]},{"id":"responsibility-layer","name":"Responsibility and authority","description":"A proposed responsibility record separates title, maintenance duty, operation and data stewardship; holding a record grants no power to change the asset.","findings":[{"id":"responsibility-finding","name":"Responsibility and authority","description":"A proposed responsibility record separates title, maintenance duty, operation and data stewardship; holding a record grants no power to change the asset.","questions":[{"text":"Which parties hold title, operation, maintenance and record stewardship responsibilities for this work?","id":"responsibility-question-1","kind":"ownership"},{"text":"What evidence authorizes a party to approve a civil asset record change?","id":"responsibility-question-2","kind":"authority"},{"text":"When do responsibility transfers take effect and what obligations remain unresolved?","id":"responsibility-question-3","kind":"temporal"}]}]}]},{"id":"location-context","name":"Location and context","description":"Bound the work spatially and declare externally mastered interfaces.","layers":[{"id":"extent-layer","name":"Spatial extent and recognition","description":"A proposed spatial envelope records what a survey or model represents, retaining coordinate and accuracy context. Geometry helps recognize the work but is not its identity.","findings":[{"id":"extent-finding","name":"Spatial extent and recognition","description":"A proposed spatial envelope records what a survey or model represents, retaining coordinate and accuracy context. Geometry helps recognize the work but is not its identity.","questions":[{"text":"What horizontal and vertical extent identifies the surveyed civil asset?","id":"extent-question-1","kind":"spatial"},{"text":"Which survey method and accuracy qualify the location or dimensions?","id":"extent-question-2","kind":"measurement"},{"text":"How are design geometry, surveyed as-built geometry and later observations distinguished?","id":"extent-question-3","kind":"quality"}]}]},{"id":"interfaces-layer","name":"Context and external interfaces","description":"A proposed interface register locates the work among surrounding land, structures, services and receptors without copying their master records.","findings":[{"id":"interfaces-finding","name":"Context and external interfaces","description":"A proposed interface register locates the work among surrounding land, structures, services and receptors without copying their master records.","questions":[{"text":"Which parcels, structures, networks or adjacent assets intersect, support or are served by this work?","id":"interfaces-question-1","kind":"relationship"},{"text":"Which recorded land, environmental or public-access restrictions constrain use or maintenance?","id":"interfaces-question-2","kind":"constraint"},{"text":"Which external alignment or topology version locates a shared civil interface?","id":"interfaces-question-3","kind":"interoperability"}]}]}]},{"id":"physical-fabric","name":"Physical fabric","description":"Describe component references and qualified physical properties.","layers":[{"id":"parts-layer","name":"Engineered fabric and parts","description":"A proposed composition map includes engineered ground as well as constructed components. Spatial containment, load-bearing association and shared service are different relations.","findings":[{"id":"parts-finding","name":"Engineered fabric and parts","description":"A proposed composition map includes engineered ground as well as constructed components. Spatial containment, load-bearing association and shared service are different relations.","questions":[{"text":"Which maintainable components and engineered ground elements belong to this work?","id":"parts-question-1","kind":"composition"},{"text":"What evidence distinguishes engineered fill or stabilization from pre-existing ground?","id":"parts-question-2","kind":"definition"},{"text":"How are shared components assigned without duplicating asset identity or ownership?","id":"parts-question-3","kind":"exception"}]}]},{"id":"properties-layer","name":"Physical properties and materials","description":"A proposed property register separates specified, measured and inferred values. Missing test results are unknown; material labels do not certify capacity.","findings":[{"id":"properties-finding","name":"Physical properties and materials","description":"A proposed property register separates specified, measured and inferred values. Missing test results are unknown; material labels do not certify capacity.","questions":[{"text":"Which dimensions or material properties were measured for each relevant component?","id":"properties-question-1","kind":"measurement"},{"text":"Which design, sample or test record supports a physical property assertion?","id":"properties-question-2","kind":"provenance"},{"text":"Which material or location records require restricted handling under an adopted policy?","id":"properties-question-3","kind":"security"}]}]}]},{"id":"service-condition","name":"Service and condition","description":"Separate intended capability, permission and observed performance.","layers":[{"id":"capability-layer","name":"Intended function and service constraints","description":"A proposed capability record distinguishes intended service, qualified assessment and authorized operation. It neither calculates structural capacity nor authorizes access.","findings":[{"id":"capability-finding","name":"Intended function and service constraints","description":"A proposed capability record distinguishes intended service, qualified assessment and authorized operation. It neither calculates structural capacity nor authorizes access.","questions":[{"text":"Which intended service and acceptance criteria are assigned to the civil asset?","id":"capability-question-1","kind":"requirement"},{"text":"Which operating limits and hazard controls are supported by a qualified assessment?","id":"capability-question-2","kind":"constraint"},{"text":"What evidence distinguishes available, restricted, closed and unknown service states?","id":"capability-question-3","kind":"state"}]}]},{"id":"condition-layer","name":"Observation and condition","description":"A proposed condition record binds every result to its inspected extent, procedure and time. An uninspected part cannot inherit a favorable grade from its neighbor.","findings":[{"id":"condition-finding","name":"Observation and condition","description":"A proposed condition record binds every result to its inspected extent, procedure and time. An uninspected part cannot inherit a favorable grade from its neighbor.","questions":[{"text":"What inspection observations support the current condition assertion?","id":"condition-question-1","kind":"evidence"},{"text":"When was the condition observed and when was its result recorded or superseded?","id":"condition-question-2","kind":"temporal"},{"text":"Which defects, missing coverage or conflicting assessments require review?","id":"condition-question-3","kind":"quality"}]}]}]},{"id":"asset-lifecycle","name":"Asset lifecycle","description":"Connect origin, service entry and interventions while preserving identity decisions.","layers":[{"id":"acceptance-layer","name":"Origin and entry into service","description":"A proposed origin record keeps work completion, handover, acceptance and service entry as separately evidenced assertions; historic assets may lack some records.","findings":[{"id":"acceptance-finding","name":"Origin and entry into service","description":"A proposed origin record keeps work completion, handover, acceptance and service entry as separately evidenced assertions; historic assets may lack some records.","questions":[{"text":"Which evidence establishes the origin and current lifecycle stage of this work?","id":"acceptance-question-1","kind":"lifecycle"},{"text":"Who accepted which completed extent and under what conditions or reservations?","id":"acceptance-question-2","kind":"authority"},{"text":"Which recorded event permits an asserted entry into service?","id":"acceptance-question-3","kind":"event"}]}]},{"id":"intervention-layer","name":"Maintenance and asset continuity","description":"A proposed intervention history links work records to resulting asset assertions. Physical replacement, logical identity continuity and record retirement require explicit decisions.","findings":[{"id":"intervention-finding","name":"Maintenance and asset continuity","description":"A proposed intervention history links work records to resulting asset assertions. Physical replacement, logical identity continuity and record retirement require explicit decisions.","questions":[{"text":"Which inspection finding or policy triggers the next proposed maintenance intervention?","id":"intervention-question-1","kind":"process"},{"text":"Which asset parts changed after an intervention and what evidence supports the new state?","id":"intervention-question-2","kind":"lifecycle"},{"text":"How are replacement, abandonment or removal recorded while applying retention and disposal rules?","id":"intervention-question-3","kind":"retention"}]}]}]},{"id":"evidence-exchange","name":"Evidence and exchange","description":"Make record provenance and exchange limitations reviewable.","layers":[{"id":"lineage-layer","name":"Evidence and revision lineage","description":"A proposed evidence index retains the source of each assertion and records corrections without treating a digest or signature as proof of engineering truth.","findings":[{"id":"lineage-finding","name":"Evidence and revision lineage","description":"A proposed evidence index retains the source of each assertion and records corrections without treating a digest or signature as proof of engineering truth.","questions":[{"text":"Which source entity, activity and accountable party produced this asset assertion?","id":"lineage-question-1","kind":"provenance"},{"text":"What checks support acceptance of an imported report or survey into the evidence index?","id":"lineage-question-2","kind":"validation"},{"text":"How are contradictory evidence, retracted reports and corrected observations preserved?","id":"lineage-question-3","kind":"exception"}]}]},{"id":"exchange-layer","name":"Exchange and permitted views","description":"A proposed exchange manifest identifies scope, authorization and mapping loss. Reference to an external vocabulary is not a conformance result.","findings":[{"id":"exchange-finding","name":"Exchange and permitted views","description":"A proposed exchange manifest identifies scope, authorization and mapping loss. Reference to an external vocabulary is not a conformance result.","questions":[{"text":"Which pinned exchange profile maps the civil asset and what information cannot be represented?","id":"exchange-question-1","kind":"interoperability"},{"text":"Which recipient may receive each asset view and at what level of spatial detail?","id":"exchange-question-2","kind":"access"},{"text":"Which round-trip and identity checks must pass before an exchange is accepted?","id":"exchange-question-3","kind":"validation"}]}]}]}]},"agentConduct":{"may":["Register an asset draft: Proposed and unimplemented local function. Resolve identity before introducing a proposed local asset record.","Link a qualified observation: Proposed and unimplemented local function. Bind a report to the inspected asset extent and time.","Record an evidenced asset change: Proposed and unimplemented local function. Propose a revision from a referenced intervention or acceptance record.","Review maintenance evidence gaps: Proposed and unimplemented local function. Compare record completeness against an explicitly supplied maintenance profile.","Prepare an authorized asset view: Proposed and unimplemented local function. Apply an adopted disclosure and mapping policy to a local projection.","Propose record retirement: Proposed and unimplemented local function. Prepare a record continuity decision using physical-state evidence and retention policy."],"mustNot":["Referenced source records, permits, title and audit records have their own masters and disposition rules; local deletion cannot delete them.","Deny access until the adopting Dimension policy grants a purpose-specific view; enforce restrictions at bundle, layer, finding and artifact, including linked payloads."],"requiresHuman":[]},"ethics":{"considerations":[],"affectedParties":[]},"owners":{"steward":"Name the adopting public asset custodian, private asset owner or delegated record steward by role; no named company is the model owner.","roles":[{"name":"Asset record steward","responsibilities":["Maintains identity and scope; resolves correspondence and authorizes supported record revisions."]},{"name":"Qualified assessor","responsibilities":["Supplies scope-limited observations and assessments with method, uncertainty and time; competence is verified externally."]},{"name":"Maintenance custodian","responsibilities":["Provides responsibility and maintenance evidence; cannot turn task completion into safety certification."]},{"name":"Evidence reviewer","responsibilities":["Checks attribution, applicability, contradictions and revision lineage without silently discarding contrary evidence."]},{"name":"Access and records custodian","responsibilities":["Applies recipient-specific disclosure, retention, legal holds and lawful disposal."]}],"masterSystems":[]},"relations":[{"target":"WM-BLT-001","type":"references","note":"Proposed binding, not an approved registry relation. Optional structural asset reference or same-master correspondence. Detailed structural fabric, calculations and its lifecycle remain at that master."},{"target":"WM-BLT-007","type":"references","note":"Proposed binding, not an approved registry relation. Optional construction or maintenance work reference. Only the asset effect and supporting acceptance reference are local; project execution is external."},{"target":"WM-BLT-006","type":"references","note":"Proposed binding, not an approved registry relation. Optional operating facility reference; the facility operation and service-management lifecycle are external."},{"target":"WM-BLT-008","type":"references","note":"Proposed binding, not an approved registry relation. Optional site or campus membership; site administration is external."},{"target":"WM-BLT-003","type":"references","note":"Proposed binding, not an approved registry relation. Optional infrastructure network membership or carried-service reference; no local topology or route computation."},{"target":"WM-BLT-009","type":"references","note":"Proposed binding, not an approved registry relation. Optional linear asset and alignment reference with version and station convention; no local recalibration of chainage."},{"target":"WM-BLT-010","type":"references","note":"Proposed binding, not an approved registry relation. Optional utility topology interface reference; network connectivity and operation are external."},{"target":"Adopting Dimension land and authority masters","type":"references","note":"Proposed binding, not an approved registry relation. Profile must pin actual land, party, title, access, retention and audit bindings before operation; conceptual external target, not an invented registry ID."},{"target":"IFC 4.3.2.0","type":"aligned","note":"Map supported asset and element concepts through a pinned profile; no universal one-to-one mapping or certified exchange."},{"target":"InfraGML 1.0 Part 2","type":"aligned","note":"Map facility versus project concepts and explicitly declare core dependencies and unsupported domains."},{"target":"SOSA/SSN 2017 and PROV-O 2013","type":"aligned","note":"Align observation qualification and provenance, without inheriting operational safety, ownership or access powers."},{"target":"WM-BLT-001 Building / Structure","type":"neighbor","note":"Generic structural fabric stays in the structural asset master. A bridge or retaining structure may have one master identity with two governed views, or a referenced component identity within a larger civil asset. Do not create duplicate real-world assets merely to populate both cards."},{"target":"WM-BLT-007 Construction Work","type":"neighbor","note":"Projects create, modify or remove an asset. This record carries intervention and acceptance references but never owns work-package execution, contractual completion or certification."},{"target":"WM-BLT-006 Facility and WM-BLT-008 Site / Campus","type":"neighbor","note":"Functional operations and site aggregation remain external. An IFC facility class is an exchange concept and is not proof that these Vercy boundaries are identical."},{"target":"WM-BLT-003 Infrastructure Network, WM-BLT-009 Linear Infrastructure Asset and WM-BLT-010 Utility Network Topology","type":"neighbor","note":"Keep network membership, carried services and alignment references. Connectivity, routing, chainage calibration and topology state have external masters; a culvert or embankment is not automatically a network edge."},{"target":"Land, ownership, survey and environmental records","type":"neighbor","note":"Record spatial association and responsible-party authority references, not title or an inferred right to alter land. Natural terrain is context unless an engineered intervention is evidenced; adjacent receptors and permit restrictions remain external evidence."}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system identifier with issuer and scope","Governed global identifier or IRI","UUID or ULID assigned by the adopting Dimension"]},"properties":{"applicability":"required","items":[]},"recognition":{"applicability":"required","items":[]},"capabilities":{"applicability":"required","items":["Register an asset draft: Proposed and unimplemented local function. Resolve identity before introducing a proposed local asset record.","Link a qualified observation: Proposed and unimplemented local function. Bind a report to the inspected asset extent and time.","Record an evidenced asset change: Proposed and unimplemented local function. Propose a revision from a referenced intervention or acceptance record.","Review maintenance evidence gaps: Proposed and unimplemented local function. Compare record completeness against an explicitly supplied maintenance profile.","Prepare an authorized asset view: Proposed and unimplemented local function. Apply an adopted disclosure and mapping policy to a local projection.","Propose record retirement: Proposed and unimplemented local function. Prepare a record continuity decision using physical-state evidence and retention policy."]},"hazards":{"applicability":"required","items":[]},"interfaces":{"applicability":"required","items":["PROV-O: The PROV Ontology"]},"context":{"applicability":"required","items":["English descriptions; source terminology does not determine local legal meaning.","The US green-infrastructure guidance informs maintenance questions only; local statutory responsibilities, permits and engineering criteria require qualified review.","No globally mandatory inspection frequency, capacity threshold, energy certificate or single owner is assumed."]}},"sources":[{"title":"IFC 4.3.2.0 - IfcFacility","url":"https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/lexical/IfcFacility.htm","note":"buildingSMART International"},{"title":"InfraGML 1.0 Part 2 - Facilities and Projects","url":"https://docs.ogc.org/is/16-102r2/16-102r2.html","note":"Open Geospatial Consortium"},{"title":"IFC 4.3.2.0 - IfcEarthworksElement","url":"https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/lexical/IfcEarthworksElement.htm","note":"buildingSMART International"},{"title":"Green Infrastructure Installation, Operation, and Maintenance","url":"https://www.epa.gov/green-infrastructure/green-infrastructure-installation-operation-and-maintenance","note":"United States Environmental Protection Agency"},{"title":"Semantic Sensor Network Ontology","url":"https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/","note":"World Wide Web Consortium"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/2013/REC-prov-o-20130430/","note":"World Wide Web Consortium"},{"title":"LandInfra / InfraGML standards overview","url":"https://www.ogc.org/standards/infragml/","note":"Open Geospatial Consortium"}],"openQuestions":["Restore independent external review before canonical or publishable-draft promotion.","Verify source editions, availability, licensing and profile-specific claim support; HTTP success alone is insufficient.","Develop asset-class and jurisdiction profiles with competent reviewers, including historical assets, partial acceptance, engineered ground, shared structural identity and disputed responsibility.","Implement nested schemas and adversarial instance fixtures for coordinate changes, stale inspections, missing units, replacement, mapping loss, restricted views and lawful payload disposal.","No independent second-provider review; the required separate local self-audit cannot restore independent review.","Direct HTTP checks are not attempted under the owner-reported sandbox block; source versions, availability and licensing require coordinator verification.","Nested object schemas, quantity types, controlled vocabularies, coordinate transformations and executable conformance fixtures remain to be developed.","Detailed bridge, tunnel, dam, road, railway, coastal and geotechnical profiles, climate exposure and environmental assessment methods are outside this cross-asset draft.","Wet infrastructure has no claimed complete LandInfra 1.0 mapping; an adopting profile must supply suitable verified semantics.","Neighbor bindings and real instance migration from legacy U1 remain untested. Historic evidence gaps and contested identity need profile review."],"resources":{"spec":"/models/wm-blt-005-civil-works/spec.yaml","agents":"/models/wm-blt-005-civil-works/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-blt-005"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-blt-005-civil-works/spec.yaml"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-10-06T20:08:53Z","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}}