{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-blt-009","code":"wm-blt-009-linear-infrastructure-asset","url":"https://ver.cy/models/wm-blt-009-linear-infrastructure-asset/","name":"Linear Infrastructure Asset","alternateNames":[],"kind":"world-model","status":"published","version":"0.1.0","language":"en","classifiers":{"family":"World Models","category":"Physical world and living systems","entryKind":"entity","plane":"","domain":["PHY.BLT.NET"],"industry":["Cross-industry"],"navPath":"NAV.PHY.BLT.NET","tags":["linear","infrastructure","asset","phy.blt.net"],"facets":{}},"whatItIs":"A linear infrastructure asset is a road, railway, pipeline, cable or similar asset whose extent runs along a route and is managed as segments located by linear referencing. The network topology it belongs to, the nodes and point facilities on it, and the traffic or flow it carries are separate subjects.","purpose":"Describe one persistent linear physical asset and its managed spans, location, properties, condition and lifecycle evidence while preserving external master authority.","scope":{"in":["Stable asset identity and classification","Versioned segmentation, referencing and evidence-qualified geometry","Span-specific physical properties, responsibility, capability and condition claims","External work, rights, topology and lifecycle decision references"],"out":["Network-wide graph ownership, routing and flow simulation","Engineering design verification, safety certification and live equipment control","Land-title adjudication, granting rights or permits and work execution","Standalone point facilities and construction project lifecycle","Universal road, rail, pipeline or cable technical profiles"],"boundaries":[{"neighbor":"WM-BLT-003 Infrastructure Network","distinction":"Registry parent is a broader network context, not evidence that an individual asset owns the network. Use references, not inheritance or mandatory containment."},{"neighbor":"WM-BLT-010 Utility Network Topology","distinction":"Graph nodes, edges and connectivity are mastered separately. This asset carries versioned mappings and interface claims only."},{"neighbor":"WM-BLT-004 Utility Service Point","distinction":"A point service interface may reference this asset but has its own identity and lifecycle."},{"neighbor":"WM-BLT-001 Building / Structure and WM-BLT-006 Facility","distinction":"Bridges, tunnels and point facilities can intersect or support the asset without losing separate master identity."},{"neighbor":"WM-BLT-007 Construction Work","distinction":"Work plans and execution stay external; the asset carries affected-extent and acceptance evidence links."},{"neighbor":"Alignment, land parcel and observation records","distinction":"Positioning geometry, rights and observations are related information objects, not interchangeable physical asset identities."}]},"distinguishingFeatures":["Located by linear referencing along a route, not only by a footprint or a point.","Managed as segments whose condition and works vary along its length.","One asset of an infrastructure network; the network topology and its nodes are modelled separately.","The asset itself, distinct from the traffic, energy or fluid that flows through it."],"structure":{"bundles":[{"id":"BLT009-B1","name":"Route and segmentation","description":"Where the asset runs and how it is divided for management.","layers":[{"id":"BLT009-B1-L1","name":"Linear referencing","description":"Positions along the asset expressed by a referencing method.","findings":[{"id":"BLT009-F01","name":"Referencing method","description":"The linear referencing method, its origin and its measure units.","questions":[{"text":"Which linear referencing method locates positions on this asset?","id":"BLT009-Q01"},{"text":"Where are the start point and direction of measurement defined?","id":"BLT009-Q02"}]},{"id":"BLT009-F02","name":"Segment register","description":"The segments with from and to measures and their own identifiers.","questions":[{"text":"Which segments make up the asset, with their from and to measures?","id":"BLT009-Q03"},{"text":"Do adjacent segments meet without gaps or overlaps?","id":"BLT009-Q04"}]}]}]},{"id":"BLT009-B2","name":"Condition and works","description":"The physical state of each segment and the work done on it.","layers":[{"id":"BLT009-B2-L1","name":"Condition","description":"Inspected state of segments against a declared rating scheme.","findings":[{"id":"BLT009-F03","name":"Segment condition","description":"The latest condition rating per segment with inspection date and method.","questions":[{"text":"What condition rating does each segment have, under which scheme?","id":"BLT009-Q05"},{"text":"When and by which method was the segment last inspected?","id":"BLT009-Q06"}]},{"id":"BLT009-F04","name":"Defects along the route","description":"Defects located by measure with severity and status.","questions":[{"text":"Which defects are recorded on the segment, at which measures?","id":"BLT009-Q07"},{"text":"Which defects are open, and what severity do they carry?","id":"BLT009-Q08"}]}]}]},{"id":"BLT009-B3","name":"Ownership and access","description":"Who answers for the asset and under which rights it crosses land.","layers":[{"id":"BLT009-B3-L1","name":"Ownership and rights of way","description":"Owner, operator and land rights along the route.","findings":[{"id":"BLT009-F05","name":"Accountable owner","description":"The owner and operator for each segment.","questions":[{"text":"Who owns and who operates each segment of the asset?","id":"BLT009-Q09"},{"text":"Where does responsibility pass from one owner to another along the route?","id":"BLT009-Q10"}]},{"id":"BLT009-F06","name":"Right of way","description":"Easements, wayleaves or corridors that allow the asset to cross land.","questions":[{"text":"Under which rights does the asset cross each land parcel?","id":"BLT009-Q11"},{"text":"Which restrictions apply within the protected corridor?","id":"BLT009-Q12"}]}]}]}]},"agentConduct":{"may":["Locate positions, defects and works on the asset by linear reference and convert them to coordinates.","Report segment condition and open defects from inspection records.","Flag gaps, overlaps or inconsistent measures in the segment register.","Plan inspection routes from the segment register."],"mustNot":["Change measures or segment boundaries without a re-referencing record.","Authorize excavation or works near the asset without the owner's clearance.","Disclose the exact route of critical pipelines or cables to parties without a need to know.","Report a segment as safe when its inspection is overdue or missing.","Operate valves, signals or switches on the asset without operator authority."],"requiresHuman":["Closing or restricting a segment to use.","Accepting a condition rating that triggers or defers major works.","Granting a new right of way or crossing permission."]},"ethics":{"considerations":["Failures of roads, rails, pipelines and power lines can kill people and cut communities off.","Rights of way burden landowners and communities along the route, who need fair notice and compensation.","Exact routes of critical assets are security-sensitive and need controlled disclosure."],"affectedParties":["Users of the road, rail or service","Landowners along the route","Communities near pipelines and lines","Maintenance and construction workers"]},"owners":{"steward":"The infrastructure owner or operator that holds the asset register and answers for its safety.","roles":[{"name":"Asset steward","responsibilities":["Resolve identity and continuity decisions; maintain scoped role bindings."]},{"name":"Reference-system custodian","responsibilities":["Approve calibration and segmentation versions; review ambiguous mappings."]},{"name":"Qualified condition reviewer","responsibilities":["Assess inspection coverage and conflicting evidence; route safety decisions externally."]},{"name":"Evidence and access custodian","responsibilities":["Apply sensitivity and retention policy; preserve lineage and authorized disclosure."]},{"name":"Local model agent","responsibilities":["Perform only authorized local read, validation and proposed changes; refuse unresolved authority or stale pins."]}],"masterSystems":["Infrastructure asset register","Road or rail network database","Utility network geographic information system","Cadastre and easement register"]},"relations":[{"target":"WM-BLT-003","type":"references","note":"Candidate network context corresponding to the registry parent; versioned membership only, no network lifecycle."},{"target":"WM-BLT-010","type":"references","note":"Candidate utility graph binding where applicable; preserve separate topology authority and cardinality."},{"target":"WM-BLT-004","type":"references","note":"Optional service-point interface references; separate point master."},{"target":"WM-BLT-001","type":"references","note":"Optional supporting or intersected structure references; no copied structure specification."},{"target":"WM-BLT-007","type":"references","note":"Optional construction and renewal work evidence; execution stays with work master."},{"target":"ISO 19148:2021","type":"aligned","note":"Conceptual linear location alignment; complete normative mapping and conformance unverified."},{"target":"IFC 4.3.2.0 IfcAlignment","type":"aligned","note":"Positioning representation alignment only; the physical asset is not equated to IfcAlignment."},{"target":"INSPIRE Utility Networks Technical Guidelines 3.0","type":"aligned","note":"Utility spatial-object projection where applicable; no universal legal or telecom applicability claim."},{"target":"SSN/SOSA 2017 and PROV-O 2013","type":"aligned","note":"Conceptual observation and evidence lineage links, not implemented RDF conformance."},{"target":"WM-BLT-003 Infrastructure Network","type":"neighbor","note":"Registry parent is a broader network context, not evidence that an individual asset owns the network. Use references, not inheritance or mandatory containment."},{"target":"WM-BLT-010 Utility Network Topology","type":"neighbor","note":"Graph nodes, edges and connectivity are mastered separately. This asset carries versioned mappings and interface claims only."},{"target":"WM-BLT-004 Utility Service Point","type":"neighbor","note":"A point service interface may reference this asset but has its own identity and lifecycle."},{"target":"WM-BLT-001 Building / Structure and WM-BLT-006 Facility","type":"neighbor","note":"Bridges, tunnels and point facilities can intersect or support the asset without losing separate master identity."},{"target":"WM-BLT-007 Construction Work","type":"neighbor","note":"Work plans and execution stay external; the asset carries affected-extent and acceptance evidence links."},{"target":"Alignment, land parcel and observation records","type":"neighbor","note":"Positioning geometry, rights and observations are related information objects, not interchangeable physical asset identities."},{"target":"WM-BLT-003","type":"parent"}],"interaction":{"identity":{"applicability":"required","items":["An asset is identified by the owner's asset identifier, often a route number with a segment code.","Positions on it are given as a linear reference: route identifier plus measure under a stated method."]},"properties":{"applicability":"required","items":["Length along the route in metres or kilometres, measured under the stated referencing method.","Cross-section dimensions such as carriageway width or pipe diameter in millimetres or metres.","Gradient in per cent and curve radius in metres where the asset is a road or railway.","Design and operating limits such as axle load in tonnes, pressure in bar or voltage in kilovolts.","Depth of cover in metres for buried pipelines and cables, with the survey date."]},"recognition":{"applicability":"required","items":["Recognized in the field by its continuous alignment, route markers, chainage posts or warning markers.","Often confused with the network as a whole, with a single structure such as a bridge, or with the corridor of land it occupies."]},"capabilities":{"applicability":"required","items":["Carries traffic, energy, fluids or data along its route within design limits.","Can be closed, isolated or restricted segment by segment.","Can be inspected and renewed by stretch without replacing the whole asset."]},"hazards":{"applicability":"required","items":["Strikes on buried pipelines and cables during excavation.","Structural failure of degraded segments under load.","Leaks, fires or electrocution from damaged pipelines and power cables."]},"interfaces":{"applicability":"required","items":["ISO 19148 linear referencing for positions along the asset.","OGC CityGML for infrastructure geometry exchange.","buildingSMART IFC 4.3 for roads, railways and their alignments.","ISO 55000 series for asset management records."]},"context":{"applicability":"required","items":["Managed by road authorities, railway infrastructure managers, pipeline operators and grid companies.","Excavation near buried assets is usually governed by utility locating and notification regimes.","Safety regulators set inspection and condition reporting duties for many asset kinds."]}},"sources":[{"title":"ISO 19148:2021 - Geographic information - Linear referencing","url":"https://www.iso.org/standard/75150.html","note":"International Organization for Standardization"},{"title":"IFC 4.3.2.0 - IfcAlignment","url":"https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/lexical/IfcAlignment.htm","note":"buildingSMART International"},{"title":"INSPIRE Data Specification on Utility and Government Services - Technical Guidelines","url":"https://inspire-mif.github.io/technical-guidelines/data/us/dataspecification_us.html","note":"European Commission"},{"title":"Best Practices in Geographic Information Systems-based Transportation Asset Management","url":"https://www.gis.fhwa.dot.gov/documents/GIS_AssetMgmt.htm","note":"Federal Highway Administration"},{"title":"Semantic Sensor Network Ontology","url":"https://www.w3.org/TR/vocab-ssn-2017/","note":"World Wide Web Consortium"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"World Wide Web Consortium"},{"title":"ISO 55000:2024 - Asset management - Vocabulary, overview and principles","url":"https://www.iso.org/standard/83053.html","note":"International Organization for Standardization"},{"title":"ISO 19148 Geographic information - Linear referencing, ISO"},{"title":"ISO 55000 Asset management - Overview, principles and terminology, ISO"},{"title":"IFC 4.3 Industry Foundation Classes, buildingSMART International"}],"openQuestions":["Complete direct source retrieval and substantive version, licensing and applicability review; obtain the normative material needed for any claimed conformance.","Develop sector profiles and test repeated measures, branching, split/merge history, mixed segmentation, crossing without connection, stale inspection, partial removal and controlled disclosure.","Implement nested schemas and version-pinned mappings with refusal and information-loss reports before operational integration.","Restore independent external review before promotion beyond a noncanonical reviewable draft.","Independent external provider review is absent.","Direct source HTTP checks are unattempted under the owner-reported sandbox restriction; statuses and body hashes are unmeasured.","ISO normative full texts, current versions of all sources and historical report issue date remain unverified.","Nested instance schemas, coordinate transformations, topology mappings and acceptance fixtures remain unimplemented.","Sector-specific engineering thresholds, hazards, rights, licensing, privacy and retention profiles require qualified adoption review."],"resources":{"spec":"/models/wm-blt-009-linear-infrastructure-asset/spec.yaml","agents":"/models/wm-blt-009-linear-infrastructure-asset/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-blt-009"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-blt-009-linear-infrastructure-asset/spec.yaml","ver-cy/world-models/card-supplements/wm-blt-009-linear-infrastructure-asset.json"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-10-06T20:15:53Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"filled","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-06, unreviewed). Written from the card's existing content and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}