# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T20:04:41Z", "synthesisSha256": "b0f944ca2c0dd83d1334fa99dfa6e0f27f8b85b99c0896799084246416dd3ca9", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-BLT-003", "registryId": "vr.wm-blt-003", "name": "Infrastructure Network", "version": "0.3.0", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.BLT.NET" ], "tags": [ "infrastructure", "network", "phy.blt.net" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-blt-003-infrastructure-network/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-blt-003", "model": { "registry_id": "vr.wm-blt-003", "model_id": "WM-BLT-003", "name": "Infrastructure Network", "entry_kind": "entity", "purpose": "Describe one persistent physical infrastructure network through its identity, member references, qualified state and evidence, while preserving the masters of assets, topology and observations.", "scope_statement": "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" ], "boundary_notes": [ { "neighbor": "WM-BLT-009", "distinction": "Linear Infrastructure Asset masters physical segments, detailed properties, surveys and asset lifecycle. This model retains membership and evidence references.", "source_refs": [ "SRC-003", "SRC-008" ] }, { "neighbor": "WM-BLT-010", "distinction": "Utility Network Topology masters utility graph nodes, edges and operational connectivity snapshots. Bind a revision; do not duplicate switching or graph evaluation.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "WM-FLW-014", "distinction": "Network Flow / Telemetry Stream masters time-varying flow records. Retain only scoped observation and summary references.", "source_refs": [ "SRC-005" ] }, { "neighbor": "WM-BLT-001", "distinction": "Carrying buildings and structures keep distinct asset identities and maintenance records.", "source_refs": [ "SRC-003" ] }, { "neighbor": "WM-BLT-004", "distinction": "Utility Service Point owns end-user connection semantics; network membership does not own service delivery.", "source_refs": [ "SRC-002" ] }, { "neighbor": "WM-PLC-002", "distinction": "Land Parcel supplies spatial and parcel references; crossing an extent does not establish easement or title.", "source_refs": [ "SRC-003" ] }, { "neighbor": "WM-PLC-005", "distinction": "Settlement / Urban Form supplies geographic context without becoming network membership.", "source_refs": [ "SRC-001" ] }, { "neighbor": "WM-ACT-019", "distinction": "Incident / Emergency masters the incident; local status stores only referenced impact and restoration assertions.", "source_refs": [ "SRC-006", "SRC-007" ] } ] }, "sources": [ { "id": "SRC-001", "title": "INSPIRE Transport Networks Technical Guidelines", "organization": "European Commission INSPIRE Maintenance and Implementation Group", "url": "https://inspire-mif.github.io/technical-guidelines/data/tn/dataspecification_tn.html", "version_or_date": "Header v3.3.0, 2024-01-31; introduction retains 3.2rc1/3.2 labels", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:02:14Z", "relevance": "Network membership, connections, spatial representations and distinct dataset lifespans; transport profile only." }, { "id": "SRC-002", "title": "INSPIRE Utility and Government Services Technical Guidelines", "organization": "European Commission INSPIRE Maintenance and Implementation Group", "url": "https://inspire-mif.github.io/technical-guidelines/data/us/dataspecification_us.html", "version_or_date": "Header v3.2.0, 2024-01-31; introduction retains v3.0 label", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:02:14Z", "relevance": "Utility network classification, authority roles and real-world versus dataset time; not a control graph implementation." }, { "id": "SRC-003", "title": "InfraGML 1.0 Part 2 - LandInfra Facilities and Projects", "organization": "Open Geospatial Consortium", "url": "https://docs.ogc.org/is/16-102r2/16-102r2.html", "version_or_date": "16-102r2, 1.0, 2017-08-16", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:02:14Z", "relevance": "Facility, facility part and physical element distinctions support references to separately mastered assets." }, { "id": "SRC-004", "title": "InfraGML 1.0 Part 3 - Alignments", "organization": "Open Geospatial Consortium", "url": "https://docs.ogc.org/is/16-103r2/16-103r2.html", "version_or_date": "16-103r2, 1.0, 2017-08-16", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:02:14Z", "relevance": "Versioned alignment and linear location references; no assumed coordinate transformation accuracy." }, { "id": "SRC-005", "title": "Semantic Sensor Network Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/", "version_or_date": "Recommendation, 2017-10-19", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:02:14Z", "relevance": "Observation subject, property, procedure, result and phenomenon/result time; sensor capability is not infrastructure capacity." }, { "id": "SRC-006", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "Recommendation, 2013-04-30", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:02:14Z", "relevance": "Attribution, revision and derivation of network views and evidence; not truth certification." }, { "id": "SRC-007", "title": "Guide to Operational Technology Security", "organization": "National Institute of Standards and Technology", "url": "https://doi.org/10.6028/NIST.SP.800-82r3", "version_or_date": "SP 800-82 Revision 3, September 2023", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:02:14Z", "relevance": "Least privilege, separate duties and policy-level protection for sensitive infrastructure records; no device operations." }, { "id": "SRC-008", "title": "Using a Life Cycle Planning Process to Support Transportation Asset Management", "organization": "Federal Highway Administration", "url": "https://www.fhwa.dot.gov/asset/guidance/hif19006.pdf", "version_or_date": "FHWA-HIF-19-006, January 2019", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:02:14Z", "relevance": "Network-level condition and maintenance planning context; transport example, not universal utility engineering rules." } ], "structure": { "bundles": [ { "id": "b-identity", "name": "Identity and stewardship", "description": "One persistent network and the authority for its records.", "rationale": "Proposed local concern derived from the cited concepts; this hierarchy and its questions are design choices, not a standard-mandated schema.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ], "layers": [ { "id": "l-network-key", "name": "Network identity and class", "description": "A named infrastructure network retains identity across membership and operator changes. Disconnected or planned elements can belong to it under an explicit inclusion rule.", "source_refs": [ "SRC-001", "SRC-002" ], "findings": [ { "id": "f-network-key", "name": "Network identity and class", "description": "A named infrastructure network retains identity across membership and operator changes. Disconnected or planned elements can belong to it under an explicit inclusion rule.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "q-network-key-1", "text": "Which master identifier distinguishes this network from a route, dataset or operator?", "kind": "identity", "answer_data": [ "master_namespace", "network_id", "aliases", "matching_evidence" ] }, { "id": "q-network-key-2", "text": "Which transport or utility class and versioned profile describe the network?", "kind": "classification", "answer_data": [ "mode", "profile_ref", "profile_version", "mixed_mode_reason" ] }, { "id": "q-network-key-3", "text": "What inclusion rule defines this network when elements are disconnected or not yet operational?", "kind": "definition", "answer_data": [ "membership_rule", "boundary_basis", "exceptions", "unknowns" ] } ], "data_elements": [ { "id": "d-network-key-1", "name": "Network identity and class 1", "description": "Candidate group: master_namespace, network_id, aliases, matching_evidence. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "d-network-key-2", "name": "Network identity and class 2", "description": "Candidate group: mode, profile_ref, profile_version, mixed_mode_reason. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "d-network-key-3", "name": "Network identity and class 3", "description": "Candidate group: membership_rule, boundary_basis, exceptions, unknowns. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "a-network-key", "name": "Network identity and class record", "description": "Versioned evidence or reference summary for this finding; external source payloads retain their own master identities and access controls.", "media_or_form": [ "structured record", "evidence reference manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; adopting Dimension UUID or ULID third. Revision and time are separate from stable identity.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null } ] }, { "id": "l-stewardship", "name": "Stewardship and authority", "description": "Record stewardship, operation and legal ownership are separate roles with scoped validity; transfer of an operator does not automatically create a new network.", "source_refs": [ "SRC-002", "SRC-006", "SRC-007" ], "findings": [ { "id": "f-stewardship", "name": "Stewardship and authority", "description": "Record stewardship, operation and legal ownership are separate roles with scoped validity; transfer of an operator does not automatically create a new network.", "source_refs": [ "SRC-002", "SRC-006", "SRC-007" ], "questions": [ { "id": "q-stewardship-1", "text": "Which accountable role stewards the network record and which separate roles operate or own its members?", "kind": "ownership", "answer_data": [ "custodian_ref", "operator_refs", "owner_refs", "role_scope" ] }, { "id": "q-stewardship-2", "text": "What evidence and effective interval authorize each stewardship assignment?", "kind": "authority", "answer_data": [ "authority_ref", "delegation_scope", "valid_from", "valid_to", "recorded_at" ] }, { "id": "q-stewardship-3", "text": "How is disputed or overlapping responsibility recorded without merging masters?", "kind": "exception", "answer_data": [ "dispute_ref", "claimants", "affected_members", "resolution_state" ] } ], "data_elements": [ { "id": "d-stewardship-1", "name": "Stewardship and authority 1", "description": "Candidate group: custodian_ref, operator_refs, owner_refs, role_scope. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-006", "SRC-007" ] }, { "id": "d-stewardship-2", "name": "Stewardship and authority 2", "description": "Candidate group: authority_ref, delegation_scope, valid_from, valid_to, recorded_at. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-006", "SRC-007" ] }, { "id": "d-stewardship-3", "name": "Stewardship and authority 3", "description": "Candidate group: dispute_ref, claimants, affected_members, resolution_state. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "a-stewardship", "name": "Stewardship and authority record", "description": "Versioned evidence or reference summary for this finding; external source payloads retain their own master identities and access controls.", "media_or_form": [ "structured record", "evidence reference manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; adopting Dimension UUID or ULID third. Revision and time are separate from stable identity.", "source_refs": [ "SRC-002", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-membership", "name": "Membership and external structure", "description": "Membership is local; assets and topology retain their own authoritative records.", "rationale": "Proposed local concern derived from the cited concepts; this hierarchy and its questions are design choices, not a standard-mandated schema.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "layers": [ { "id": "l-member-set", "name": "Versioned member set", "description": "A membership revision links nodes, segments and other eligible elements with roles and effective intervals. Geometry overlap is insufficient for identity or membership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "findings": [ { "id": "f-member-set", "name": "Versioned member set", "description": "A membership revision links nodes, segments and other eligible elements with roles and effective intervals. Geometry overlap is insufficient for identity or membership.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "questions": [ { "id": "q-member-set-1", "text": "Which asset and element references belong to this membership revision and in what roles?", "kind": "composition", "answer_data": [ "membership_revision", "member_refs", "member_roles", "source_revisions" ] }, { "id": "q-member-set-2", "text": "When does each membership assertion apply and when was it recorded?", "kind": "temporal", "answer_data": [ "effective_from", "effective_to", "recorded_at", "assertion_status" ] }, { "id": "q-member-set-3", "text": "Which unresolved, duplicate or retired member references prevent a complete view?", "kind": "validation", "answer_data": [ "unresolved_refs", "duplicate_candidates", "retired_refs", "completeness_state" ] } ], "data_elements": [ { "id": "d-member-set-1", "name": "Versioned member set 1", "description": "Candidate group: membership_revision, member_refs, member_roles, source_revisions. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "d-member-set-2", "name": "Versioned member set 2", "description": "Candidate group: effective_from, effective_to, recorded_at, assertion_status. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "d-member-set-3", "name": "Versioned member set 3", "description": "Candidate group: unresolved_refs, duplicate_candidates, retired_refs, completeness_state. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "a-member-set", "name": "Versioned member set record", "description": "Versioned evidence or reference summary for this finding; external source payloads retain their own master identities and access controls.", "media_or_form": [ "structured record", "evidence reference manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; adopting Dimension UUID or ULID third. Revision and time are separate from stable identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "l-connection-binding", "name": "Topology and interconnection bindings", "description": "The network references a topology snapshot and external interconnection evidence. It does not master switching state, infer junctions from crossings or implement routing.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "findings": [ { "id": "f-connection-binding", "name": "Topology and interconnection bindings", "description": "The network references a topology snapshot and external interconnection evidence. It does not master switching state, infer junctions from crossings or implement routing.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "questions": [ { "id": "q-connection-binding-1", "text": "Which topology snapshot and cross-network agreements explain the declared connections?", "kind": "relationship", "answer_data": [ "topology_ref", "topology_revision", "neighbor_network_refs", "agreement_refs" ] }, { "id": "q-connection-binding-2", "text": "What connection, direction and transfer restrictions are asserted by the source profile?", "kind": "constraint", "answer_data": [ "connection_refs", "restriction_refs", "profile_version", "valid_interval" ] }, { "id": "q-connection-binding-3", "text": "Which connectivity claims are unknown, stale or inconsistent across the participating masters?", "kind": "quality", "answer_data": [ "conflict_refs", "freshness_limit", "source_times", "qualification" ] } ], "data_elements": [ { "id": "d-connection-binding-1", "name": "Topology and interconnection bindings 1", "description": "Candidate group: topology_ref, topology_revision, neighbor_network_refs, agreement_refs. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "id": "d-connection-binding-2", "name": "Topology and interconnection bindings 2", "description": "Candidate group: connection_refs, restriction_refs, profile_version, valid_interval. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "id": "d-connection-binding-3", "name": "Topology and interconnection bindings 3", "description": "Candidate group: conflict_refs, freshness_limit, source_times, qualification. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] } ], "artifacts": [ { "id": "a-connection-binding", "name": "Topology and interconnection bindings record", "description": "Versioned evidence or reference summary for this finding; external source payloads retain their own master identities and access controls.", "media_or_form": [ "structured record", "evidence reference manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; adopting Dimension UUID or ULID third. Revision and time are separate from stable identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-location", "name": "Spatial context and recognition", "description": "Geographic and linear locations carry representation and observation limits.", "rationale": "Proposed local concern derived from the cited concepts; this hierarchy and its questions are design choices, not a standard-mandated schema.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-005" ], "layers": [ { "id": "l-extent", "name": "Network extent and representation", "description": "Extent is a qualified network view, not proof of land rights, actual connectivity or safe excavation. Preserve reference system, dimensionality, accuracy and derivation.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ], "findings": [ { "id": "f-extent", "name": "Network extent and representation", "description": "Extent is a qualified network view, not proof of land rights, actual connectivity or safe excavation. Preserve reference system, dimensionality, accuracy and derivation.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ], "questions": [ { "id": "q-extent-1", "text": "Which geometry and coordinate reference system represent this network view?", "kind": "spatial", "answer_data": [ "geometry_ref", "crs", "vertical_datum", "dimensionality", "representation_scale" ] }, { "id": "q-extent-2", "text": "What units, method, observation time and uncertainty qualify its extent or length?", "kind": "measurement", "answer_data": [ "quantity", "unit", "method", "observed_at", "uncertainty", "aggregation_rule" ] }, { "id": "q-extent-3", "text": "What survey or record evidence distinguishes this network from colocated infrastructure?", "kind": "evidence", "answer_data": [ "survey_refs", "marker_evidence", "asset_refs", "confidence", "unresolved_matches" ] } ], "data_elements": [ { "id": "d-extent-1", "name": "Network extent and representation 1", "description": "Candidate group: geometry_ref, crs, vertical_datum, dimensionality, representation_scale. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "id": "d-extent-2", "name": "Network extent and representation 2", "description": "Candidate group: quantity, unit, method, observed_at, uncertainty, aggregation_rule. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "id": "d-extent-3", "name": "Network extent and representation 3", "description": "Candidate group: survey_refs, marker_evidence, asset_refs, confidence, unresolved_matches. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "a-extent", "name": "Network extent and representation record", "description": "Versioned evidence or reference summary for this finding; external source payloads retain their own master identities and access controls.", "media_or_form": [ "structured record", "evidence reference manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; adopting Dimension UUID or ULID third. Revision and time are separate from stable identity.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "l-linear-location", "name": "Linear location binding", "description": "Offsets reference a governed route or alignment revision and measurement method. A recalibration can change addresses without changing the underlying member identity.", "source_refs": [ "SRC-004", "SRC-006" ], "findings": [ { "id": "f-linear-location", "name": "Linear location binding", "description": "Offsets reference a governed route or alignment revision and measurement method. A recalibration can change addresses without changing the underlying member identity.", "source_refs": [ "SRC-004", "SRC-006" ], "questions": [ { "id": "q-linear-location-1", "text": "Which alignment revision and linear referencing method locate the referenced member?", "kind": "spatial", "answer_data": [ "alignment_ref", "alignment_revision", "lrm_ref", "datum", "direction" ] }, { "id": "q-linear-location-2", "text": "What offset or interval and units identify the position within that reference?", "kind": "measurement", "answer_data": [ "start_measure", "end_measure", "unit", "offset_type", "tolerance" ] }, { "id": "q-linear-location-3", "text": "How are recalibration and coordinate conversions evidenced without silently moving the asset?", "kind": "interoperability", "answer_data": [ "old_reference", "new_reference", "transformation_ref", "accuracy", "unmapped_status" ] } ], "data_elements": [ { "id": "d-linear-location-1", "name": "Linear location binding 1", "description": "Candidate group: alignment_ref, alignment_revision, lrm_ref, datum, direction. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "d-linear-location-2", "name": "Linear location binding 2", "description": "Candidate group: start_measure, end_measure, unit, offset_type, tolerance. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "d-linear-location-3", "name": "Linear location binding 3", "description": "Candidate group: old_reference, new_reference, transformation_ref, accuracy, unmapped_status. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "a-linear-location", "name": "Linear location binding record", "description": "Versioned evidence or reference summary for this finding; external source payloads retain their own master identities and access controls.", "media_or_form": [ "structured record", "evidence reference manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; adopting Dimension UUID or ULID third. Revision and time are separate from stable identity.", "source_refs": [ "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-performance", "name": "Capability and observation context", "description": "Qualified statements of capability and performance refer to underlying engineering and observation records.", "rationale": "Proposed local concern derived from the cited concepts; this hierarchy and its questions are design choices, not a standard-mandated schema.", "source_refs": [ "SRC-005", "SRC-006", "SRC-008" ], "layers": [ { "id": "l-capacity-basis", "name": "Capacity statement binding", "description": "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.", "source_refs": [ "SRC-006", "SRC-008" ], "findings": [ { "id": "f-capacity-basis", "name": "Capacity statement binding", "description": "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.", "source_refs": [ "SRC-006", "SRC-008" ], "questions": [ { "id": "q-capacity-basis-1", "text": "Which approved capability statement applies to this network boundary and scenario?", "kind": "requirement", "answer_data": [ "rating_ref", "subject_scope", "scenario", "issuing_role", "approval_evidence" ] }, { "id": "q-capacity-basis-2", "text": "What value, unit, conditions, tolerance and validity qualify the stated capability?", "kind": "measurement", "answer_data": [ "rated_value", "unit", "conditions", "tolerance", "valid_interval" ] }, { "id": "q-capacity-basis-3", "text": "Which aggregation assumptions and exclusions prevent interpreting component ratings as universal network capacity?", "kind": "constraint", "answer_data": [ "aggregation_method_ref", "excluded_members", "bottleneck_assumptions", "unknowns" ] } ], "data_elements": [ { "id": "d-capacity-basis-1", "name": "Capacity statement binding 1", "description": "Candidate group: rating_ref, subject_scope, scenario, issuing_role, approval_evidence. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006", "SRC-008" ] }, { "id": "d-capacity-basis-2", "name": "Capacity statement binding 2", "description": "Candidate group: rated_value, unit, conditions, tolerance, valid_interval. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006", "SRC-008" ] }, { "id": "d-capacity-basis-3", "name": "Capacity statement binding 3", "description": "Candidate group: aggregation_method_ref, excluded_members, bottleneck_assumptions, unknowns. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006", "SRC-008" ] } ], "artifacts": [ { "id": "a-capacity-basis", "name": "Capacity statement binding record", "description": "Versioned evidence or reference summary for this finding; external source payloads retain their own master identities and access controls.", "media_or_form": [ "structured record", "evidence reference manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; adopting Dimension UUID or ULID third. Revision and time are separate from stable identity.", "source_refs": [ "SRC-006", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "l-observation-binding", "name": "Observed utilization and freshness", "description": "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.", "source_refs": [ "SRC-005", "SRC-006" ], "findings": [ { "id": "f-observation-binding", "name": "Observed utilization and freshness", "description": "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.", "source_refs": [ "SRC-005", "SRC-006" ], "questions": [ { "id": "q-observation-binding-1", "text": "Which observations support the load or utilization summary and what exactly was observed?", "kind": "provenance", "answer_data": [ "observation_refs", "feature_of_interest", "observed_property", "procedure_ref" ] }, { "id": "q-observation-binding-2", "text": "Which phenomenon period, result time and ingestion time qualify the reported load?", "kind": "temporal", "answer_data": [ "phenomenon_interval", "result_time", "ingested_at", "freshness_state" ] }, { "id": "q-observation-binding-3", "text": "Are load and rating comparable in units, scope and period before any utilization conclusion is retained?", "kind": "quality", "answer_data": [ "rating_revision", "comparison_basis", "unit_conversion", "missingness", "uncertainty" ] } ], "data_elements": [ { "id": "d-observation-binding-1", "name": "Observed utilization and freshness 1", "description": "Candidate group: observation_refs, feature_of_interest, observed_property, procedure_ref. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-006" ] }, { "id": "d-observation-binding-2", "name": "Observed utilization and freshness 2", "description": "Candidate group: phenomenon_interval, result_time, ingested_at, freshness_state. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-006" ] }, { "id": "d-observation-binding-3", "name": "Observed utilization and freshness 3", "description": "Candidate group: rating_revision, comparison_basis, unit_conversion, missingness, uncertainty. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "a-observation-binding", "name": "Observed utilization and freshness record", "description": "Versioned evidence or reference summary for this finding; external source payloads retain their own master identities and access controls.", "media_or_form": [ "structured record", "evidence reference manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; adopting Dimension UUID or ULID third. Revision and time are separate from stable identity.", "source_refs": [ "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-continuity", "name": "Lifecycle and condition context", "description": "Network continuity is recorded separately from asset work and operational commands.", "rationale": "Proposed local concern derived from the cited concepts; this hierarchy and its questions are design choices, not a standard-mandated schema.", "source_refs": [ "SRC-002", "SRC-006", "SRC-008" ], "layers": [ { "id": "l-status-assertion", "name": "Lifecycle and availability assertions", "description": "Retain attributed network status with scope, event and record times. Commissioning, closure and restoration are source assertions, not side effects of editing a record.", "source_refs": [ "SRC-002", "SRC-006", "SRC-007" ], "findings": [ { "id": "f-status-assertion", "name": "Lifecycle and availability assertions", "description": "Retain attributed network status with scope, event and record times. Commissioning, closure and restoration are source assertions, not side effects of editing a record.", "source_refs": [ "SRC-002", "SRC-006", "SRC-007" ], "questions": [ { "id": "q-status-assertion-1", "text": "What status applies to the network or stated subset according to the responsible authority?", "kind": "state", "answer_data": [ "status_code", "affected_scope", "authority_ref", "source_event_ref" ] }, { "id": "q-status-assertion-2", "text": "Which evidence explains commissioning, retirement, split, merge or succession without reusing an old identifier?", "kind": "lifecycle", "answer_data": [ "transition_ref", "predecessor_refs", "successor_refs", "effective_at", "evidence_refs" ] }, { "id": "q-status-assertion-3", "text": "How are partial closure, stale availability and conflicting restoration notices represented?", "kind": "exception", "answer_data": [ "affected_member_refs", "conflict_refs", "freshness_rule", "unknown_state" ] } ], "data_elements": [ { "id": "d-status-assertion-1", "name": "Lifecycle and availability assertions 1", "description": "Candidate group: status_code, affected_scope, authority_ref, source_event_ref. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-006", "SRC-007" ] }, { "id": "d-status-assertion-2", "name": "Lifecycle and availability assertions 2", "description": "Candidate group: transition_ref, predecessor_refs, successor_refs, effective_at, evidence_refs. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-006", "SRC-007" ] }, { "id": "d-status-assertion-3", "name": "Lifecycle and availability assertions 3", "description": "Candidate group: affected_member_refs, conflict_refs, freshness_rule, unknown_state. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "a-status-assertion", "name": "Lifecycle and availability assertions record", "description": "Versioned evidence or reference summary for this finding; external source payloads retain their own master identities and access controls.", "media_or_form": [ "structured record", "evidence reference manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; adopting Dimension UUID or ULID third. Revision and time are separate from stable identity.", "source_refs": [ "SRC-002", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "l-condition-summary", "name": "Condition and maintenance context", "description": "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.", "source_refs": [ "SRC-005", "SRC-008" ], "findings": [ { "id": "f-condition-summary", "name": "Condition and maintenance context", "description": "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.", "source_refs": [ "SRC-005", "SRC-008" ], "questions": [ { "id": "q-condition-summary-1", "text": "Which surveys and grading scales support the stated condition of the included members?", "kind": "evidence", "answer_data": [ "survey_refs", "scale_ref", "survey_times", "covered_population" ] }, { "id": "q-condition-summary-2", "text": "Which external maintenance plan or completed work records explain the network condition context?", "kind": "process", "answer_data": [ "maintenance_plan_refs", "work_record_refs", "affected_members", "inspection_refs" ] }, { "id": "q-condition-summary-3", "text": "What sampling gaps or incompatible grades limit the network condition summary?", "kind": "quality", "answer_data": [ "uninspected_members", "sampling_method", "grade_mapping", "aggregation_limits" ] } ], "data_elements": [ { "id": "d-condition-summary-1", "name": "Condition and maintenance context 1", "description": "Candidate group: survey_refs, scale_ref, survey_times, covered_population. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-008" ] }, { "id": "d-condition-summary-2", "name": "Condition and maintenance context 2", "description": "Candidate group: maintenance_plan_refs, work_record_refs, affected_members, inspection_refs. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-008" ] }, { "id": "d-condition-summary-3", "name": "Condition and maintenance context 3", "description": "Candidate group: uninspected_members, sampling_method, grade_mapping, aggregation_limits. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005", "SRC-008" ] } ], "artifacts": [ { "id": "a-condition-summary", "name": "Condition and maintenance context record", "description": "Versioned evidence or reference summary for this finding; external source payloads retain their own master identities and access controls.", "media_or_form": [ "structured record", "evidence reference manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; adopting Dimension UUID or ULID third. Revision and time are separate from stable identity.", "source_refs": [ "SRC-005", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "b-assurance", "name": "Evidence and controlled exchange", "description": "Trace the network view and qualify every export.", "rationale": "Proposed local concern derived from the cited concepts; this hierarchy and its questions are design choices, not a standard-mandated schema.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007" ], "layers": [ { "id": "l-revision-lineage", "name": "Evidence and revision lineage", "description": "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.", "source_refs": [ "SRC-006" ], "findings": [ { "id": "f-revision-lineage", "name": "Evidence and revision lineage", "description": "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.", "source_refs": [ "SRC-006" ], "questions": [ { "id": "q-revision-lineage-1", "text": "Which source revisions, actors and transformations produced this network view?", "kind": "provenance", "answer_data": [ "source_refs", "source_revisions", "actor_refs", "transformation_refs" ] }, { "id": "q-revision-lineage-2", "text": "What evidence supports each correction and which conflicting assertions remain unresolved?", "kind": "validation", "answer_data": [ "correction_reason", "superseded_revision", "contrary_evidence", "disposition" ] }, { "id": "q-revision-lineage-3", "text": "Which retention rule and hold govern evidence payload disposal and minimal continuity records?", "kind": "retention", "answer_data": [ "schedule_ref", "hold_refs", "disposal_authority", "tombstone_policy" ] } ], "data_elements": [ { "id": "d-revision-lineage-1", "name": "Evidence and revision lineage 1", "description": "Candidate group: source_refs, source_revisions, actor_refs, transformation_refs. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006" ] }, { "id": "d-revision-lineage-2", "name": "Evidence and revision lineage 2", "description": "Candidate group: correction_reason, superseded_revision, contrary_evidence, disposition. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006" ] }, { "id": "d-revision-lineage-3", "name": "Evidence and revision lineage 3", "description": "Candidate group: schedule_ref, hold_refs, disposal_authority, tombstone_policy. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006" ] } ], "artifacts": [ { "id": "a-revision-lineage", "name": "Evidence and revision lineage record", "description": "Versioned evidence or reference summary for this finding; external source payloads retain their own master identities and access controls.", "media_or_form": [ "structured record", "evidence reference manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; adopting Dimension UUID or ULID third. Revision and time are separate from stable identity.", "source_refs": [ "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "l-exchange-view", "name": "Access and interoperability view", "description": "A recipient-specific projection carries its purpose, license, profile version and documented omissions. Map publication does not authorize release of sensitive underlying records.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "findings": [ { "id": "f-exchange-view", "name": "Access and interoperability view", "description": "A recipient-specific projection carries its purpose, license, profile version and documented omissions. Map publication does not authorize release of sensitive underlying records.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "questions": [ { "id": "q-exchange-view-1", "text": "Which recipient, purpose and scope authorize the proposed network projection?", "kind": "access", "answer_data": [ "recipient_role", "purpose", "authorized_scope", "approval_ref" ] }, { "id": "q-exchange-view-2", "text": "Which sensitive locations, dependencies or condition details must be withheld or generalized?", "kind": "security", "answer_data": [ "classification", "redaction_policy", "generalization_rule", "release_review" ] }, { "id": "q-exchange-view-3", "text": "Which versioned exchange profile and loss report accompany the exported representation?", "kind": "interoperability", "answer_data": [ "profile_ref", "profile_version", "mapping_ref", "loss_report", "validation_result" ] } ], "data_elements": [ { "id": "d-exchange-view-1", "name": "Access and interoperability view 1", "description": "Candidate group: recipient_role, purpose, authorized_scope, approval_ref. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "id": "d-exchange-view-2", "name": "Access and interoperability view 2", "description": "Candidate group: classification, redaction_policy, generalization_rule, release_review. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "id": "d-exchange-view-3", "name": "Access and interoperability view 3", "description": "Candidate group: profile_ref, profile_version, mapping_ref, loss_report, validation_result. Preserve explicit unknown and not-applicable values; nested schemas remain a profile task.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] } ], "artifacts": [ { "id": "a-exchange-view", "name": "Access and interoperability view record", "description": "Versioned evidence or reference summary for this finding; external source payloads retain their own master identities and access controls.", "media_or_form": [ "structured record", "evidence reference manifest" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first; governed IRI second; adopting Dimension UUID or ULID third. Revision and time are separate from stable identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "fn-register-network", "name": "Register network record", "description": "Proposed, unimplemented operation. Create a local identity and scope record.", "inputs": [ "master identity", "network class", "membership rule", "custodian authority" ], "outputs": [ "Local draft identity or duplicate/refusal report" ], "preconditions": [ "Authenticated authorized role, adopting policy and expected local revision are required; refuse missing authority or stale concurrent writes.", "No unresolved identity collision" ], "effects": [ "A local record is created; no asset or operator master is changed", "Corrections require a new revision; deletion and access expansion follow separate policy." ], "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "fn-revise-membership", "name": "Revise membership references", "description": "Proposed, unimplemented operation. Record evidenced membership changes against a fixed previous revision.", "inputs": [ "expected revision", "member references", "effective intervals", "change evidence" ], "outputs": [ "New membership revision or reference conflict report" ], "preconditions": [ "Authenticated authorized role, adopting policy and expected local revision are required; refuse missing authority or stale concurrent writes.", "Every reference has a master namespace and known resolution status" ], "effects": [ "Appends membership assertions; does not transfer assets or rewrite topology", "Corrections require a new revision; deletion and access expansion follow separate policy." ], "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "fn-bind-network-context", "name": "Bind external network context", "description": "Proposed, unimplemented operation. Attach qualified topology, location, rating, observation or condition references.", "inputs": [ "network revision", "external record identifiers and revisions", "subject scope", "evidence qualifiers" ], "outputs": [ "Reference binding or incompatibility report" ], "preconditions": [ "Authenticated authorized role, adopting policy and expected local revision are required; refuse missing authority or stale concurrent writes.", "Role may read all referenced records; units and scope assessed where relevant" ], "effects": [ "Retains qualified local references; no telemetry ingestion service or control command is created", "Corrections require a new revision; deletion and access expansion follow separate policy." ], "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-008" ] }, { "id": "fn-record-status", "name": "Record status evidence", "description": "Proposed, unimplemented operation. Record an authority-issued lifecycle or availability assertion.", "inputs": [ "source event", "effective time", "affected scope", "authority evidence" ], "outputs": [ "Local status revision or unresolved conflict" ], "preconditions": [ "Authenticated authorized role, adopting policy and expected local revision are required; refuse missing authority or stale concurrent writes.", "Issuing role and freshness assessed; contrary notices retained" ], "effects": [ "Changes only the local assertion; does not commission, close, restore or retire equipment", "Corrections require a new revision; deletion and access expansion follow separate policy." ], "source_refs": [ "SRC-002", "SRC-006", "SRC-007" ] }, { "id": "fn-validate-network-view", "name": "Validate network view", "description": "Proposed, unimplemented operation. Check local identity, reference completeness and comparison qualifiers.", "inputs": [ "frozen local revision", "profile rules", "referenced revisions" ], "outputs": [ "Validation findings with indeterminate outcomes" ], "preconditions": [ "Authenticated authorized role, adopting policy and expected local revision are required; refuse missing authority or stale concurrent writes.", "Read authority for each inspected binding" ], "effects": [ "Produces a diagnostic report; does not prove engineering safety or calculate operational routes", "Corrections require a new revision; deletion and access expansion follow separate policy." ], "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006" ] }, { "id": "fn-prepare-projection", "name": "Prepare governed projection", "description": "Proposed, unimplemented operation. Prepare a local recipient-specific exchange view and loss manifest.", "inputs": [ "authorized recipient and purpose", "scope policy", "network revision", "exchange profile" ], "outputs": [ "Local projection draft or denial with reasons" ], "preconditions": [ "Authenticated authorized role, adopting policy and expected local revision are required; refuse missing authority or stale concurrent writes.", "Release scope approved; sensitive aggregation and disclosure assessed" ], "effects": [ "Writes a local artifact only; external delivery or publication is outside this operation", "Corrections require a new revision; deletion and access expansion follow separate policy." ], "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007" ] } ], "composition": [ { "target": "WM-BLT-009", "relation": "REFERENCE", "purpose": "Linear Infrastructure Asset masters physical segments, detailed properties, surveys and asset lifecycle. This model retains membership and evidence references.", "required": false, "source_refs": [ "SRC-003", "SRC-008" ] }, { "target": "WM-BLT-010", "relation": "REFERENCE", "purpose": "Utility Network Topology masters utility graph nodes, edges and operational connectivity snapshots. Bind a revision; do not duplicate switching or graph evaluation.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "WM-FLW-014", "relation": "REFERENCE", "purpose": "Network Flow / Telemetry Stream masters time-varying flow records. Retain only scoped observation and summary references.", "required": false, "source_refs": [ "SRC-005" ] }, { "target": "WM-BLT-001", "relation": "REFERENCE", "purpose": "Carrying buildings and structures keep distinct asset identities and maintenance records.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "WM-BLT-004", "relation": "REFERENCE", "purpose": "Utility Service Point owns end-user connection semantics; network membership does not own service delivery.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "WM-PLC-002", "relation": "REFERENCE", "purpose": "Land Parcel supplies spatial and parcel references; crossing an extent does not establish easement or title.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "WM-PLC-005", "relation": "REFERENCE", "purpose": "Settlement / Urban Form supplies geographic context without becoming network membership.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "WM-ACT-019", "relation": "REFERENCE", "purpose": "Incident / Emergency masters the incident; local status stores only referenced impact and restoration assertions.", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] }, { "target": "INSPIRE transport and utility profiles", "relation": "ALIGN", "purpose": "Conceptual alignment only; pin the adopted version and qualify header/body discrepancies before implementation.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "InfraGML 1.0 Parts 2 and 3", "relation": "ALIGN", "purpose": "Facility and alignment exchange concepts; no encoding conformance or ISO 19148 certification is asserted.", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "target": "SOSA/SSN 2017 and PROV-O 2013", "relation": "ALIGN", "purpose": "Observation and provenance mappings require implementation profiles and tests; this does not import actuation.", "required": false, "source_refs": [ "SRC-005", "SRC-006" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "An accountable network custodian role and evidence of record stewardship; operator and legal owner roles remain separate.", "A master namespace, versioned membership policy, sector profile and referenced model bindings.", "An access, sensitivity, evidence retention and correction policy including responsibility during stewardship transfers." ], "namespace_guidance": "Keep network identity separate from asset, topology snapshot and dataset IDs. Preserve master namespaces; never match solely by name, map intersection or operator. Use the adopting Dimension namespace for local assertions.", "registry_links": [ "vr.wm-blt-003", "WM-BLT-009", "WM-BLT-010", "WM-FLW-014" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize only identifiers and codes under explicit namespace/profile rules. Preserve original values, units, coordinate systems, unknowns and conflicting assertions.", "Separate stable network ID from immutable record revisions and real-world effective intervals. Record lineage for splits and merges." ], "patch_rules": [ "Require expected revision, authorized role, evidence and affected scope; append corrections rather than silently replacing assertions.", "Do not alter engineering ratings, equipment state or child master records through local patches." ], "compatibility_rules": [ "Pin schema, vocabulary, coordinate and neighbor revisions; report lossy mapping and unresolved references.", "A representation or operator change does not alone establish a new physical network. Define succession with documented authority." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier", "Governed global identifier or IRI", "UUID or ULID assigned by the adopting Dimension" ], "timestamp_rule": "Use RFC 3339 with seconds and explicit offset or Z for known instants. Distinguish event/effective time, phenomenon time, result time and ingestion time. Preserve date-only values and uncertainty without inventing midnight.", "serial_naming_rule": "Use opaque network key, artifact kind and immutable sequence or revision; avoid sensitive locations or personal identifiers in filenames.", "integrity_rule": "Record source revision and available content digest plus algorithm, transformation and access scope. Hash equality does not establish accuracy, authority or current physical state." }, "policies": [ "This is a noncanonical reviewable draft under the single-provider waiver; independent external review remains absent.", "Network records do not authorize field work, excavation, rerating, routing decisions or control commands. Hazard and security treatment stays at policy level.", "Protect sensitive dependencies, precise locations and condition records through purpose-bound least privilege, including derived summaries.", "No universal capacity aggregation, condition threshold or retention period is defined; adopt qualified sector and jurisdiction profiles." ], "crud": { "read": [ "Apply recipient and purpose scope at bundle, layer, finding and artifact levels; preserve freshness and unknown-state qualifiers." ], "create": [ "Require unique namespace-qualified identity, boundary, custodian role and evidence; draft membership may be explicitly incomplete." ], "update": [ "Validate expected revision and authority; retain corrections and contrary evidence with effective versus recorded time." ], "delete": [ "Apply adopting-Dimension retention schedules, lawful holds and authorized disposal to local payloads, replicas and cached projections; retain only permitted minimal tombstones.", "Record retirement is not physical decommissioning. The source master and its policy own deletion of referenced records; never cascade local deletion into them." ] }, "roles": [ { "name": "Network custodian", "responsibilities": [ "Maintains network identity, membership authority and stewardship continuity." ] }, { "name": "Domain engineer", "responsibilities": [ "Reviews capability, condition and spatial qualifications within a documented discipline and mandate." ] }, { "name": "Data steward", "responsibilities": [ "Resolves identifiers, source revisions and interoperability loss." ] }, { "name": "Access and records officer", "responsibilities": [ "Approves release scopes, sensitivity, retention and disposal." ] }, { "name": "Read-only analyst", "responsibilities": [ "Inspects permitted views and reports uncertainty without field or control authority." ] } ], "access": { "default_rule": "Deny disclosure or modification unless recipient, purpose and scope are authorized. Infrastructure ownership does not itself authorize all third-party source records.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Emergency disclosure requires an evidenced role, limited purpose and recorded approval; it is not a general bypass.", "Public generalized geometry does not grant access to source topology, detailed condition, personal records or dependency analysis." ], "audit_requirements": [ "Record actor, purpose, scope, revision and outcome of reads, exports, corrections and disposal in the adopting audit service; minimize retained payloads." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "AGENTS.md and adopting owner/access policies", "spec.yaml and publication holds", "Pinned membership profile, neighbor contracts and permitted source evidence" ] } }, "coverage": { "claim": "Source-grounded proposed structure for one persistent infrastructure network, with versioned membership and qualified external evidence bindings. Separate local no-tools self-audit found no critical conflict. Source/version verification, adoption profiles, executable conformance and independent external review remain holds; this is a noncanonical reviewable draft.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Network versus dataset, operator, route and member identities." }, { "dimension": "lifecycle", "status": "covered", "notes": "Status assertions and split/merge succession; no physical lifecycle execution." }, { "dimension": "relationships", "status": "covered", "notes": "Member links and separate asset, topology, flow and incident masters." }, { "dimension": "temporal", "status": "covered", "notes": "Effective, observed, result and recorded times with explicit uncertainty." }, { "dimension": "provenance", "status": "covered", "notes": "Source revisions, attribution, derivation and correction evidence." }, { "dimension": "ownership", "status": "covered", "notes": "Custodian, operator and legal owner roles separated." }, { "dimension": "validation", "status": "gap", "notes": "Research structure validated; nested instance profiles and conformance fixtures pending." }, { "dimension": "access", "status": "covered", "notes": "Recipient-specific scopes, sensitivity and release review." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Local disposal policy and minimal tombstones; no deletion of referenced masters." }, { "dimension": "interoperability", "status": "gap", "notes": "Conceptual alignments with version/loss reporting; no implemented standard mappings." }, { "dimension": "direct properties", "status": "covered", "notes": "Mode, boundary, extent, qualified length and network-level capability references." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Survey/marker evidence and scoped observation bindings; overlap is not identity." }, { "dimension": "capabilities and behavior", "status": "covered", "notes": "Proposed local operations with authority, effects and refusal conditions; no actuation." }, { "dimension": "context and hazards", "status": "covered", "notes": "External incidents, rights and sensitive dependencies referenced at policy level." } ], "known_omissions": [ "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." ], "conflicts": [], "regional_assumptions": [ "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." ], "adversarial_checks": [ "Do not infer physical connectivity from intersecting geometry or mandatory connectedness from membership.", "Do not treat unknown, closed, uninspected or absent telemetry as available, safe or zero load.", "Do not sum incompatible ratings or grades across modes, periods and source revisions.", "Do not turn a local status edit into a field action, or inherit legacy wildcard conformance claims.", "Do not duplicate the newer asset, utility topology and telemetry model boundaries." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "entity", "status": "accepted", "rationale": "The subject is one persistent physical network with governed membership and continuity across operator or member change. Record collections are contextual views, not ownership of asset, topology or flow masters. The registry standalone-mm designation is a catalogue category, not a research subject-kind enum." }, "decisions": [ { "concept": "Persistent network identity", "disposition": "accepted", "rationale": "A physical network remains identifiable across member and operator changes. The local member set and contextual bindings do not transfer child lifecycle ownership; entity is defensible despite collection-like membership." }, { "concept": "Connectedness and geometry", "disposition": "qualified", "rationale": "Planned or disconnected members and incomplete drafts are explicitly allowed. Geometry crossings and shared names cannot establish joins or identity; connectivity belongs to an external scoped snapshot." }, { "concept": "Legacy topology and sibling boundaries", "disposition": "narrowed", "rationale": "The old U3 segment, node and live utilization surface is narrowed to references. Asset detail, utility graph behavior and telemetry stream lifecycle remain in the respective sibling masters; transport may use an external sector graph." }, { "concept": "Stewardship and ownership", "disposition": "separated", "rationale": "Custodian, operator and legal owner roles are independent scoped assertions. Operator transfer alone does not replace network identity, and overlapping claims remain visible." }, { "concept": "Location and recognition", "disposition": "qualified", "rationale": "Survey and marker evidence can support recognition but do not automatically overrule contrary records. Geometry and linear offsets require reference-system and alignment versions; neither grants land rights or field safety." }, { "concept": "Network capacity", "disposition": "qualified", "rationale": "The result retains an external engineering statement with scope, units, conditions and validity. It does not derive capacity from sensor capabilities or sum member ratings. Source support is for context and provenance, not a universal rating algorithm." }, { "concept": "Observation and utilization", "disposition": "accepted with comparison gate", "rationale": "Observation subject, time and method are distinct from ratings. Comparability and missingness are explicit, so absent or stale data cannot become zero load or current availability." }, { "concept": "Lifecycle and local actions", "disposition": "separated", "rationale": "Status recording does not commission, close, restore or retire equipment. All six functions are proposed local operations with authority and revision checks; no control or routing implementation is implied." }, { "concept": "Condition and maintenance", "disposition": "qualified", "rationale": "The summary preserves survey scale, population coverage and work references. It neither owns maintenance execution nor treats completed work as automatic defect closure or service restoration." }, { "concept": "Provenance, access and disposal", "disposition": "accepted with policy dependency", "rationale": "Lineage and hashes do not certify truth. Recipient views, derived sensitivity and local payload disposal are governed explicitly; referenced masters and physical retirement remain external." }, { "concept": "Source review and version claims", "disposition": "limited", "rationale": "Browser content access is recorded separately from unattempted direct HTTP checks. The INSPIRE header/body label discrepancies and selected-section review remain open, and no current-version or engineering conformance claim is admitted." }, { "concept": "Instance and exchange conformance", "disposition": "deferred", "rationale": "Candidate grouped fields, optional composition links and conceptual alignments do not form executable instance schemas. Required bindings and conformance tests must be pinned by an adopting profile before operational reliance." }, { "concept": "Independent review", "disposition": "waived and held", "rationale": "This is a separate local Codex no-tools self-audit of frozen evidence, not an external provider pass. Skipped providers supplied no facts, agreement or additional nodes." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped with zero attempts; this separate local Codex no-tools self-audit is not independent external review.", "Source/version verification remains incomplete. Direct HTTP checks were not attempted under the owner-reported sandbox restriction; no response status was measured. Browser selected-section content review does not resolve current versions, content pins or INSPIRE header/body version discrepancies. The coordinator must run check_sources.py and review claims.", "Sector and jurisdiction adoption profiles require qualified engineering and governance review for network inclusion, stewardship, capability, condition scales, location accuracy, confidentiality, rights and retention. No field-safety or operational authority is conferred.", "Nested instance schemas, revision-pinned neighbor bindings, standard mappings and executable conformance fixtures remain incomplete. Proposed local functions are unimplemented; no routing, flow solver, control operation or certification is provided.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "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." ] }, "statistics": { "sources": 8, "bundles": 6, "layers": 12, "findings": 12, "questions": 36, "artifacts": 12, "functions": 6 } }