Infrastructure Network
Describe one persistent physical infrastructure network through its identity, member references, qualified state and evidence, while preserving the masters of assets, topology and observations.
Bundle → Layer → Finding → Questions Filled
6 bundles · 12 layers · 12 findings · 36 questions
Identity and stewardship One persistent network and the authority for its records.
Network identity and class
A named infrastructure network retains identity across membership and operator changes. Disconnected or planned elements can belong to it under an explicit inclusion rule.
Network identity and class
A named infrastructure network retains identity across membership and operator changes. Disconnected or planned elements can belong to it under an explicit inclusion rule.
- Which master identifier distinguishes this network from a route, dataset or operator? identity
- Which transport or utility class and versioned profile describe the network? classification
- What inclusion rule defines this network when elements are disconnected or not yet operational? definition
Stewardship and authority
Record stewardship, operation and legal ownership are separate roles with scoped validity; transfer of an operator does not automatically create a new network.
Stewardship and authority
Record stewardship, operation and legal ownership are separate roles with scoped validity; transfer of an operator does not automatically create a new network.
- Which accountable role stewards the network record and which separate roles operate or own its members? ownership
- What evidence and effective interval authorize each stewardship assignment? authority
- How is disputed or overlapping responsibility recorded without merging masters? exception
Membership and external structure Membership is local; assets and topology retain their own authoritative records.
Versioned member set
A membership revision links nodes, segments and other eligible elements with roles and effective intervals. Geometry overlap is insufficient for identity or membership.
Versioned member set
A membership revision links nodes, segments and other eligible elements with roles and effective intervals. Geometry overlap is insufficient for identity or membership.
- Which asset and element references belong to this membership revision and in what roles? composition
- When does each membership assertion apply and when was it recorded? temporal
- Which unresolved, duplicate or retired member references prevent a complete view? validation
Topology and interconnection bindings
The network references a topology snapshot and external interconnection evidence. It does not master switching state, infer junctions from crossings or implement routing.
Topology and interconnection bindings
The network references a topology snapshot and external interconnection evidence. It does not master switching state, infer junctions from crossings or implement routing.
- Which topology snapshot and cross-network agreements explain the declared connections? relationship
- What connection, direction and transfer restrictions are asserted by the source profile? constraint
- Which connectivity claims are unknown, stale or inconsistent across the participating masters? quality
Spatial context and recognition Geographic and linear locations carry representation and observation limits.
Network extent and representation
Extent is a qualified network view, not proof of land rights, actual connectivity or safe excavation. Preserve reference system, dimensionality, accuracy and derivation.
Network extent and representation
Extent is a qualified network view, not proof of land rights, actual connectivity or safe excavation. Preserve reference system, dimensionality, accuracy and derivation.
- Which geometry and coordinate reference system represent this network view? spatial
- What units, method, observation time and uncertainty qualify its extent or length? measurement
- What survey or record evidence distinguishes this network from colocated infrastructure? evidence
Linear location binding
Offsets reference a governed route or alignment revision and measurement method. A recalibration can change addresses without changing the underlying member identity.
Linear location binding
Offsets reference a governed route or alignment revision and measurement method. A recalibration can change addresses without changing the underlying member identity.
- Which alignment revision and linear referencing method locate the referenced member? spatial
- What offset or interval and units identify the position within that reference? measurement
- How are recalibration and coordinate conversions evidenced without silently moving the asset? interoperability
Capability and observation context Qualified statements of capability and performance refer to underlying engineering and observation records.
Capacity statement binding
Network-level capability is an attributed engineering assertion for a defined boundary and scenario. Component ratings cannot be added indiscriminately; units or limits may be incommensurate.
Capacity statement binding
Network-level capability is an attributed engineering assertion for a defined boundary and scenario. Component ratings cannot be added indiscriminately; units or limits may be incommensurate.
- Which approved capability statement applies to this network boundary and scenario? requirement
- What value, unit, conditions, tolerance and validity qualify the stated capability? measurement
- Which aggregation assumptions and exclusions prevent interpreting component ratings as universal network capacity? constraint
Observed utilization and freshness
Reference observations or telemetry summaries with their subject, period and method. A measurement is not a rating, and a missing value is not zero or proof of availability.
Observed utilization and freshness
Reference observations or telemetry summaries with their subject, period and method. A measurement is not a rating, and a missing value is not zero or proof of availability.
- Which observations support the load or utilization summary and what exactly was observed? provenance
- Which phenomenon period, result time and ingestion time qualify the reported load? temporal
- Are load and rating comparable in units, scope and period before any utilization conclusion is retained? quality
Lifecycle and condition context Network continuity is recorded separately from asset work and operational commands.
Lifecycle and availability assertions
Retain attributed network status with scope, event and record times. Commissioning, closure and restoration are source assertions, not side effects of editing a record.
Lifecycle and availability assertions
Retain attributed network status with scope, event and record times. Commissioning, closure and restoration are source assertions, not side effects of editing a record.
- What status applies to the network or stated subset according to the responsible authority? state
- Which evidence explains commissioning, retirement, split, merge or succession without reusing an old identifier? lifecycle
- How are partial closure, stale availability and conflicting restoration notices represented? exception
Condition and maintenance context
A network summary references asset condition surveys and work evidence with scale and population coverage. Completed maintenance does not itself prove defect closure or service restoration.
Condition and maintenance context
A network summary references asset condition surveys and work evidence with scale and population coverage. Completed maintenance does not itself prove defect closure or service restoration.
- Which surveys and grading scales support the stated condition of the included members? evidence
- Which external maintenance plan or completed work records explain the network condition context? process
- What sampling gaps or incompatible grades limit the network condition summary? quality
Evidence and controlled exchange Trace the network view and qualify every export.
Evidence and revision lineage
Preserve what each local assertion was derived from, who supplied it and which revision it supersedes. Attribution and hashes establish lineage or integrity, not field truth.
Evidence and revision lineage
Preserve what each local assertion was derived from, who supplied it and which revision it supersedes. Attribution and hashes establish lineage or integrity, not field truth.
- Which source revisions, actors and transformations produced this network view? provenance
- What evidence supports each correction and which conflicting assertions remain unresolved? validation
- Which retention rule and hold govern evidence payload disposal and minimal continuity records? retention
Access and interoperability view
A recipient-specific projection carries its purpose, license, profile version and documented omissions. Map publication does not authorize release of sensitive underlying records.
Access and interoperability view
A recipient-specific projection carries its purpose, license, profile version and documented omissions. Map publication does not authorize release of sensitive underlying records.
- Which recipient, purpose and scope authorize the proposed network projection? access
- Which sensitive locations, dependencies or condition details must be withheld or generalized? security
- Which versioned exchange profile and loss report accompany the exported representation? interoperability
Classifiers Filled
- Family
- World Models
- Category
- Physical world and living systems
- Entry kind
- entity
- Navigation path
- NAV.PHY.BLT.NET
- Domain
- PHY.BLT.NET
- Industry
- Cross-industry
- Tags
- infrastructurenetworkphy.blt.net
- Also called
- U3
What it is Filled
A governed network entity with revisioned membership and contextual views for roads, rail, pipes, grids and cable infrastructure. It is neither an asset register nor a live control graph. All structure and functions are proposed research design.
In scope
- Network identity, class, stewardship, boundary and membership assertions
- Revision-pinned topology, asset, alignment, capability, observation and condition bindings
- Network status evidence, succession, provenance and controlled projections
Out of scope
- Detailed asset, service-point, topology, telemetry, incident and work-order master lifecycles
- Physical control, field operations, engineering certification, route optimization and flow simulation
- Title, easement adjudication, tariff/service contracts and universal capacity calculations
Why it exists Filled
Describe one persistent physical infrastructure network through its identity, member references, qualified state and evidence, while preserving the masters of assets, topology and observations.
Distinguishing features Derived, awaiting review
- Unlike WM-BLT-009: Linear Infrastructure Asset masters physical segments, detailed properties, surveys and asset lifecycle. This model retains membership and evidence references.
- Unlike WM-BLT-010: Utility Network Topology masters utility graph nodes, edges and operational connectivity snapshots. Bind a revision; do not duplicate switching or graph evaluation.
- Unlike WM-FLW-014: Network Flow / Telemetry Stream masters time-varying flow records. Retain only scoped observation and summary references.
- Unlike WM-BLT-001: Carrying buildings and structures keep distinct asset identities and maintenance records.
- Unlike WM-BLT-004: Utility Service Point owns end-user connection semantics; network membership does not own service delivery.
- Unlike WM-PLC-002: Land Parcel supplies spatial and parcel references; crossing an extent does not establish easement or title.
- Unlike WM-PLC-005: Settlement / Urban Form supplies geographic context without becoming network membership.
- Unlike WM-ACT-019: Incident / Emergency masters the incident; local status stores only referenced impact and restoration assertions.
Note: Derived from boundary notes against neighbouring models.
What robots and AI may and may not do Derived, awaiting review
Must not
- The source master and its policy own deletion of referenced records; never cascade local deletion into them.
- Deny disclosure or modification unless recipient, purpose and scope are authorized.
May
- Register network record: Proposed, unimplemented operation. Create a local identity and scope record.
- Revise membership references: Proposed, unimplemented operation. Record evidenced membership changes against a fixed previous revision.
- Bind external network context: Proposed, unimplemented operation. Attach qualified topology, location, rating, observation or condition references.
- Record status evidence: Proposed, unimplemented operation. Record an authority-issued lifecycle or availability assertion.
- Validate network view: Proposed, unimplemented operation. Check local identity, reference completeness and comparison qualifiers.
- Prepare governed projection: Proposed, unimplemented operation. Prepare a local recipient-specific exchange view and loss manifest.
Note: Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.
Moral aspects Derived, awaiting review
- Do not alter engineering ratings, equipment state or child master records through local patches.
Note: Sentences mentioning harm, privacy, consent or similar, collected from the specification.
Owners Filled
Steward
An accountable network custodian role and evidence of record stewardship; operator and legal owner roles remain separate.
Roles
- Network custodian
- Maintains network identity, membership authority and stewardship continuity.
- Domain engineer
- Reviews capability, condition and spatial qualifications within a documented discipline and mandate.
- Data steward
- Resolves identifiers, source revisions and interoperability loss.
- Access and records officer
- Approves release scopes, sensitivity, retention and disposal.
- Read-only analyst
- Inspects permitted views and reports uncertainty without field or control authority.
Links to other meta-models Filled
references
- WM-BLT-009 - Linear Infrastructure Asset masters physical segments, detailed properties, surveys and asset lifecycle. This model retains membership and evidence references.
- WM-BLT-010 - Utility Network Topology masters utility graph nodes, edges and operational connectivity snapshots. Bind a revision; do not duplicate switching or graph evaluation.
- WM-FLW-014 - Network Flow / Telemetry Stream masters time-varying flow records. Retain only scoped observation and summary references.
- WM-BLT-001 - Carrying buildings and structures keep distinct asset identities and maintenance records.
- WM-BLT-004 - Utility Service Point owns end-user connection semantics; network membership does not own service delivery.
- WM-PLC-002 - Land Parcel supplies spatial and parcel references; crossing an extent does not establish easement or title.
- WM-PLC-005 - Settlement / Urban Form supplies geographic context without becoming network membership.
- WM-ACT-019 - Incident / Emergency masters the incident; local status stores only referenced impact and restoration assertions.
aligned
- INSPIRE transport and utility profiles - Conceptual alignment only; pin the adopted version and qualify header/body discrepancies before implementation.
- InfraGML 1.0 Parts 2 and 3 - Facility and alignment exchange concepts; no encoding conformance or ISO 19148 certification is asserted.
- SOSA/SSN 2017 and PROV-O 2013 - Observation and provenance mappings require implementation profiles and tests; this does not import actuation.
neighbor
- WM-BLT-009 - Linear Infrastructure Asset masters physical segments, detailed properties, surveys and asset lifecycle. This model retains membership and evidence references.
- WM-BLT-010 - Utility Network Topology masters utility graph nodes, edges and operational connectivity snapshots. Bind a revision; do not duplicate switching or graph evaluation.
- WM-FLW-014 - Network Flow / Telemetry Stream masters time-varying flow records. Retain only scoped observation and summary references.
- WM-BLT-001 - Carrying buildings and structures keep distinct asset identities and maintenance records.
- WM-BLT-004 - Utility Service Point owns end-user connection semantics; network membership does not own service delivery.
- WM-PLC-002 - Land Parcel supplies spatial and parcel references; crossing an extent does not establish easement or title.
- WM-PLC-005 - Settlement / Urban Form supplies geographic context without becoming network membership.
- WM-ACT-019 - Incident / Emergency masters the incident; local status stores only referenced impact and restoration assertions.
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Filled
- Authoritative master-system identifier
- Governed global identifier or IRI
- UUID or ULID assigned by the adopting Dimension
Direct properties required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Recognition required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Filled
- Register network record: Proposed, unimplemented operation. Create a local identity and scope record.
- Revise membership references: Proposed, unimplemented operation. Record evidenced membership changes against a fixed previous revision.
- Bind external network context: Proposed, unimplemented operation. Attach qualified topology, location, rating, observation or condition references.
- Record status evidence: Proposed, unimplemented operation. Record an authority-issued lifecycle or availability assertion.
- Validate network view: Proposed, unimplemented operation. Check local identity, reference completeness and comparison qualifiers.
- Prepare governed projection: Proposed, unimplemented operation. Prepare a local recipient-specific exchange view and loss manifest.
Hazards and failure modes required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Derived, awaiting review
- PROV-O: The PROV Ontology
Context of use required Filled
- INSPIRE is a European spatial exchange reference, not a universal operational graph or current-law claim.
- The highway life-cycle handbook and OT guide are selected US guidance examples; local engineering, disclosure and retention obligations require qualified profiles.
Sources Filled
- INSPIRE Transport Networks Technical Guidelines - European Commission INSPIRE Maintenance and Implementation Group
- INSPIRE Utility and Government Services Technical Guidelines - European Commission INSPIRE Maintenance and Implementation Group
- InfraGML 1.0 Part 2 - LandInfra Facilities and Projects - Open Geospatial Consortium
- InfraGML 1.0 Part 3 - Alignments - Open Geospatial Consortium
- Semantic Sensor Network Ontology - World Wide Web Consortium
- PROV-O: The PROV Ontology - World Wide Web Consortium
- Guide to Operational Technology Security - National Institute of Standards and Technology
- Using a Life Cycle Planning Process to Support Transportation Asset Management - Federal Highway Administration
Open questions
- Verify all admitted source URLs, content digests, adopted editions, licensing and claim support; reconcile INSPIRE metadata versus narrative version labels.
- Develop sector-specific membership, capability and observation profiles with engineering review and explicit transport-versus-utility topology masters.
- Test nested schemas and exchange mappings with disconnected members, mixed namespaces, crossings without junctions, recalibrations, stale observations, partial closures, incompatible ratings, disputed roles and lawful disposal.
- Restore independent external review before canonical or publishable-draft promotion.
- Independent second-provider review is absent; a separate local self-audit cannot replace it.
- Direct HTTP verification is not attempted under the owner-reported sandbox restriction; source currency and exact content/version pins require coordinator review.
- Nested instance schemas, resolved neighbor version pins, conformance mappings and adversarial fixtures remain incomplete.
- Sector-specific ratings, utility flow solvers, routing, cyber operations, maintenance execution and legal rights are outside the core.
- Non-European network profiles, detailed electrical semantics and telecom network boundaries require further research; legacy wildcard imports are not admitted as conformance.
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-blt-003-infrastructure-network/spec.yaml