# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T20:15:53Z", "synthesisSha256": "31bb0377d7183f8e1fc4986acc6a07b2523eaf4a9f88afebb45cc42882d34e29", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-BLT-009", "registryId": "vr.wm-blt-009", "name": "Linear Infrastructure Asset", "version": "0.1.0", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.BLT.NET" ], "tags": [ "linear", "infrastructure", "asset", "phy.blt.net" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-blt-009-linear-infrastructure-asset/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-blt-009", "model": { "registry_id": "vr.wm-blt-009", "model_id": "WM-BLT-009", "name": "Linear Infrastructure Asset", "entry_kind": "entity", "purpose": "Describe one persistent linear physical asset and its managed spans, location, properties, condition and lifecycle evidence while preserving external master authority.", "scope_statement": "A road, railway, pipeline, cable or comparable owner-governed physical asset represented by versioned spans. The asset is neither its reference alignment nor the whole network. Segments may be records or referenced child assets according to an explicit continuity policy.", "in_scope": [ "Stable asset identity and classification", "Versioned segmentation, referencing and evidence-qualified geometry", "Span-specific physical properties, responsibility, capability and condition claims", "External work, rights, topology and lifecycle decision references" ], "out_of_scope": [ "Network-wide graph ownership, routing and flow simulation", "Engineering design verification, safety certification and live equipment control", "Land-title adjudication, granting rights or permits and work execution", "Standalone point facilities and construction project lifecycle", "Universal road, rail, pipeline or cable technical profiles" ], "boundary_notes": [ { "neighbor": "WM-BLT-003 Infrastructure Network", "distinction": "Registry parent is a broader network context, not evidence that an individual asset owns the network. Use references, not inheritance or mandatory containment.", "source_refs": [ "SRC-003", "SRC-004" ] }, { "neighbor": "WM-BLT-010 Utility Network Topology", "distinction": "Graph nodes, edges and connectivity are mastered separately. This asset carries versioned mappings and interface claims only.", "source_refs": [ "SRC-003" ] }, { "neighbor": "WM-BLT-004 Utility Service Point", "distinction": "A point service interface may reference this asset but has its own identity and lifecycle.", "source_refs": [ "SRC-003" ] }, { "neighbor": "WM-BLT-001 Building / Structure and WM-BLT-006 Facility", "distinction": "Bridges, tunnels and point facilities can intersect or support the asset without losing separate master identity.", "source_refs": [ "SRC-002", "SRC-003" ] }, { "neighbor": "WM-BLT-007 Construction Work", "distinction": "Work plans and execution stay external; the asset carries affected-extent and acceptance evidence links.", "source_refs": [ "SRC-004", "SRC-006" ] }, { "neighbor": "Alignment, land parcel and observation records", "distinction": "Positioning geometry, rights and observations are related information objects, not interchangeable physical asset identities.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] } ] }, "sources": [ { "id": "SRC-001", "title": "ISO 19148:2021 - Geographic information - Linear referencing", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/75150.html", "version_or_date": "Edition 2, 2021-04; public abstract only", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:14:25Z", "relevance": "Conceptual location along and optionally offset from a one-dimensional object; not access to the paid normative text." }, { "id": "SRC-002", "title": "IFC 4.3.2.0 - IfcAlignment", "organization": "buildingSMART International", "url": "https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/lexical/IfcAlignment.htm", "version_or_date": "IFC4X3_ADD2, 4.3.2.0", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:14:25Z", "relevance": "Alignment as a positioning reference and distinction between business layout and geometry; conceptual alignment only." }, { "id": "SRC-003", "title": "INSPIRE Data Specification on Utility and Government Services - Technical Guidelines", "organization": "European Commission", "url": "https://inspire-mif.github.io/technical-guidelines/data/us/dataspecification_us.html", "version_or_date": "Technical Guidelines 3.0; maintained HTML rendering, retrieved 2026-10-06", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:14:25Z", "relevance": "Core pipe and cable spatial objects, validity and utility network references; linked application records stay separate. Guidance is not itself a universal legal mandate." }, { "id": "SRC-004", "title": "Best Practices in Geographic Information Systems-based Transportation Asset Management", "organization": "Federal Highway Administration", "url": "https://www.gis.fhwa.dot.gov/documents/GIS_AssetMgmt.htm", "version_or_date": "Historical report; retrieved 2026-10-06, exact issue date not pinned", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:14:25Z", "relevance": "Inventory, condition, authoritative source systems and location integration; historical case studies, not a current operational rulebook." }, { "id": "SRC-005", "title": "Semantic Sensor Network Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-ssn-2017/", "version_or_date": "2017 edition, selected observation terms; not a latest-edition claim", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:14:25Z", "relevance": "Observation, feature of interest, procedure, result and phenomenon time distinguish measured condition from the asset itself." }, { "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": "W3C Recommendation 30 April 2013", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:14:25Z", "relevance": "Attribution, derivation, revision and invalidation support evidence links; provenance does not certify truth." }, { "id": "SRC-007", "title": "ISO 55000:2024 - Asset management - Vocabulary, overview and principles", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/83053.html", "version_or_date": "Edition 2, 2024-07; public overview only", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:14:25Z", "relevance": "Lifecycle, value, risk and accountability principles; not clause-level requirements or certification evidence." } ], "structure": { "bundles": [ { "id": "bundle-identity", "name": "Asset identity", "description": "Asset-specific asset identity with explicit evidence and external master boundaries.", "rationale": "Groups independently answerable concerns needed to interpret a managed physical extent; proposed structure grounded in the cited conceptual evidence.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ], "layers": [ { "id": "layer-identity", "name": "Persistent physical asset", "description": "An owner-governed physical extent retains identity across record updates. Route names, alignment IDs, inventory rows and network links are separate identifiers; replacement can create a successor.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ], "findings": [ { "id": "finding-identity", "name": "Persistent physical asset", "description": "An owner-governed physical extent retains identity across record updates. Route names, alignment IDs, inventory rows and network links are separate identifiers; replacement can create a successor.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ], "questions": [ { "id": "q-identity-1", "kind": "identity", "text": "Which master asset identifier and namespace distinguish this physical asset from route aliases and duplicate records?", "answer_data": [ "master_asset_id", "namespace", "aliases", "duplicate_resolution" ] }, { "id": "q-identity-2", "kind": "classification", "text": "Which road, rail, pipe, cable or other governed asset class and profile apply?", "answer_data": [ "class_code", "vocabulary_version", "profile_reference" ] }, { "id": "q-identity-3", "kind": "definition", "text": "What physical extent and management boundary make this one asset rather than a network or land corridor?", "answer_data": [ "extent_statement", "boundary_basis", "included_components" ] }, { "id": "q-identity-4", "kind": "lifecycle", "text": "Under what continuity rule does renewal retain identity or create a successor asset?", "answer_data": [ "continuity_rule", "successor_references", "decision_evidence" ] } ], "data_elements": [ { "id": "data-asset-key", "name": "Asset key", "description": "Authoritative namespace-qualified identifier, immutable within the declared continuity policy.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] }, { "id": "data-class-profile", "name": "Class profile", "description": "Pinned classification vocabulary and adopting profile with boundary statement.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-identity", "name": "Asset identity register", "description": "Versioned evidence projection for persistent physical asset. Preserve source and master references, unknowns, recipient scope and revision history.", "media_or_form": [ "Logical record set", "Human-readable evidence view" ], "serial": true, "identity_strategy": "Authoritative master-system artifact ID first; governed IRI second; Dimension UUID third. Asset ID and artifact ID remain distinct; immutable revision and content digest identify a rendition, never the physical asset. Dates are attributes only.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-accountability", "name": "Responsibility and rights references", "description": "Owner, operator, maintainer and data steward are distinct role bindings that may vary by span and effective period. Land rights and permissions are referenced claims, never inferred from an asset map.", "source_refs": [ "SRC-004", "SRC-007" ], "findings": [ { "id": "finding-accountability", "name": "Responsibility and rights references", "description": "Owner, operator, maintainer and data steward are distinct role bindings that may vary by span and effective period. Land rights and permissions are referenced claims, never inferred from an asset map.", "source_refs": [ "SRC-004", "SRC-007" ], "questions": [ { "id": "q-accountability-1", "kind": "ownership", "text": "Which accountable roles apply to each span and during which effective interval?", "answer_data": [ "role", "party_reference", "span", "valid_interval", "evidence" ] }, { "id": "q-accountability-2", "kind": "authority", "text": "Which authoritative right or agreement supports the asset presence and access across each affected parcel?", "answer_data": [ "parcel_reference", "rights_record", "authority", "applicability", "unknown_reason" ] }, { "id": "q-accountability-3", "kind": "exception", "text": "Where are responsibility boundaries disputed, shared or not yet established?", "answer_data": [ "disputed_span", "competing_assertions", "escalation_owner" ] }, { "id": "q-accountability-4", "kind": "access", "text": "Which recipient may view precise location, rights evidence and contact details for this asset?", "answer_data": [ "recipient_role", "purpose", "field_scope", "disclosure_policy" ] } ], "data_elements": [ { "id": "data-responsibility-spans", "name": "Responsibility spans", "description": "Role and party references qualified by extent, time and supporting evidence.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-007" ] }, { "id": "data-rights-links", "name": "Rights links", "description": "External parcel and rights masters plus applicability and unresolved claims; no local grant of rights.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-accountability", "name": "Responsibility and rights index", "description": "Versioned evidence projection for responsibility and rights references. Preserve source and master references, unknowns, recipient scope and revision history.", "media_or_form": [ "Logical record set", "Human-readable evidence view" ], "serial": true, "identity_strategy": "Authoritative master-system artifact ID first; governed IRI second; Dimension UUID third. Asset ID and artifact ID remain distinct; immutable revision and content digest identify a rendition, never the physical asset. Dates are attributes only.", "source_refs": [ "SRC-004", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-location", "name": "Location and segmentation", "description": "Asset-specific location and segmentation with explicit evidence and external master boundaries.", "rationale": "Groups independently answerable concerns needed to interpret a managed physical extent; proposed structure grounded in the cited conceptual evidence.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-006" ], "layers": [ { "id": "layer-referencing", "name": "Versioned linear location", "description": "A linear position is interpreted only against its route or alignment version, method, origin, direction and units. Repeated measures, discontinuities and branching require explicit disambiguation; geometry is not an identifier.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "findings": [ { "id": "finding-referencing", "name": "Versioned linear location", "description": "A linear position is interpreted only against its route or alignment version, method, origin, direction and units. Repeated measures, discontinuities and branching require explicit disambiguation; geometry is not an identifier.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "questions": [ { "id": "q-referencing-1", "kind": "spatial", "text": "Which versioned reference object, origin, direction and measurement method locate this asset?", "answer_data": [ "reference_id", "reference_version", "origin", "direction", "method", "units" ] }, { "id": "q-referencing-2", "kind": "measurement", "text": "What start, end and offset values delimit the span under that referencing method?", "answer_data": [ "start_measure", "end_measure", "offset", "offset_convention", "tolerance" ] }, { "id": "q-referencing-3", "kind": "exception", "text": "How are repeated measures, station equations, reversals and branches distinguished?", "answer_data": [ "referent", "branch_id", "equation_set", "ambiguity_state" ] }, { "id": "q-referencing-4", "kind": "validation", "text": "What evidence makes a coordinate conversion reproducible or requires it to be refused?", "answer_data": [ "calibration_version", "CRS", "transform", "validity", "residual", "refusal_reason" ] } ], "data_elements": [ { "id": "data-linear-location", "name": "Linear location", "description": "Route and version, method, referent, measures and units, direction and offsets; unknown values are explicit.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "data-conversion-evidence", "name": "Conversion evidence", "description": "Pinned transformation and calibration evidence; no unconditional automatic conversion.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "artifacts": [ { "id": "artifact-referencing", "name": "Linear location and calibration record", "description": "Versioned evidence projection for versioned linear location. Preserve source and master references, unknowns, recipient scope and revision history.", "media_or_form": [ "Logical record set", "Human-readable evidence view" ], "serial": true, "identity_strategy": "Authoritative master-system artifact ID first; governed IRI second; Dimension UUID third. Asset ID and artifact ID remain distinct; immutable revision and content digest identify a rendition, never the physical asset. Dates are attributes only.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-segmentation", "name": "Segmentation and change lineage", "description": "Physical components, management sections and observation spans may use different segmentations. Overlap checks are scoped to a declared partition and time, not applied indiscriminately to all records.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006" ], "findings": [ { "id": "finding-segmentation", "name": "Segmentation and change lineage", "description": "Physical components, management sections and observation spans may use different segmentations. Overlap checks are scoped to a declared partition and time, not applied indiscriminately to all records.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006" ], "questions": [ { "id": "q-segmentation-1", "kind": "composition", "text": "Which versioned segmentation partitions the asset for the declared management purpose?", "answer_data": [ "segmentation_id", "version", "purpose", "segment_ids", "parent_asset" ] }, { "id": "q-segmentation-2", "kind": "constraint", "text": "Where are gaps or overlaps permitted, unknown or prohibited by that partition rule?", "answer_data": [ "partition_rule", "interval_convention", "tolerance", "exception_spans" ] }, { "id": "q-segmentation-3", "kind": "temporal", "text": "When did a split, merge or re-referencing take effect and when was it recorded?", "answer_data": [ "effective_time", "recorded_time", "predecessors", "successors", "mapping" ] }, { "id": "q-segmentation-4", "kind": "provenance", "text": "Which lineage preserves historical observations when segment boundaries or measures change?", "answer_data": [ "old_span", "new_span", "mapping_method", "ambiguous_remainder", "evidence" ] } ], "data_elements": [ { "id": "data-segment-membership", "name": "Segment membership", "description": "Versioned segment IDs and extents with purpose and valid period.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "data-segment-lineage", "name": "Segment lineage", "description": "Many-to-many predecessor and successor span mappings; unresolved mappings are not silently reassigned.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-segmentation", "name": "Segmentation revision ledger", "description": "Versioned evidence projection for segmentation and change lineage. Preserve source and master references, unknowns, recipient scope and revision history.", "media_or_form": [ "Logical record set", "Human-readable evidence view" ], "serial": true, "identity_strategy": "Authoritative master-system artifact ID first; governed IRI second; Dimension UUID third. Asset ID and artifact ID remain distinct; immutable revision and content digest identify a rendition, never the physical asset. Dates are attributes only.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-physical", "name": "Physical form and context", "description": "Asset-specific physical form and context with explicit evidence and external master boundaries.", "rationale": "Groups independently answerable concerns needed to interpret a managed physical extent; proposed structure grounded in the cited conceptual evidence.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ], "layers": [ { "id": "layer-geometry", "name": "Surveyed geometry and recognition", "description": "Design, as-built and observed geometry are separate representations. Survey uncertainty and field recognition cues do not prove identity or the absence of buried assets.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ], "findings": [ { "id": "finding-geometry", "name": "Surveyed geometry and recognition", "description": "Design, as-built and observed geometry are separate representations. Survey uncertainty and field recognition cues do not prove identity or the absence of buried assets.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ], "questions": [ { "id": "q-geometry-1", "kind": "spatial", "text": "Which geometry represents design, as-built or surveyed location in which coordinate and vertical reference systems?", "answer_data": [ "geometry_role", "geometry_reference", "horizontal_CRS", "vertical_datum", "epoch" ] }, { "id": "q-geometry-2", "kind": "measurement", "text": "What uncertainty, survey method and observation conditions qualify the position and burial or clearance measurement?", "answer_data": [ "uncertainty", "units", "procedure", "observation_time", "conditions" ] }, { "id": "q-geometry-3", "kind": "evidence", "text": "Which markers, records or observations corroborate recognition of the asset in the field?", "answer_data": [ "marker_reference", "observation_reference", "confidence", "conflicting_evidence" ] }, { "id": "q-geometry-4", "kind": "quality", "text": "Where do representations disagree or leave the physical location unknown?", "answer_data": [ "discrepancy_extent", "competing_geometries", "quality_state", "review_action" ] } ], "data_elements": [ { "id": "data-geometry-claims", "name": "Geometry claims", "description": "Versioned geometry references with representation role, CRS, datum and observation provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] }, { "id": "data-recognition-evidence", "name": "Recognition evidence", "description": "Field cue and survey references with uncertainty; absence of a marker is not absence of an asset.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-geometry", "name": "Geometry and recognition dossier", "description": "Versioned evidence projection for surveyed geometry and recognition. Preserve source and master references, unknowns, recipient scope and revision history.", "media_or_form": [ "Logical record set", "Human-readable evidence view" ], "serial": true, "identity_strategy": "Authoritative master-system artifact ID first; governed IRI second; Dimension UUID third. Asset ID and artifact ID remain distinct; immutable revision and content digest identify a rendition, never the physical asset. Dates are attributes only.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-properties", "name": "Material and dimensional properties", "description": "Direct properties vary by span and class. Material, width, diameter, gauge, cover, gradient or section composition are qualified measurements or design assertions; irrelevant properties are not forced onto every class.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ], "findings": [ { "id": "finding-properties", "name": "Material and dimensional properties", "description": "Direct properties vary by span and class. Material, width, diameter, gauge, cover, gradient or section composition are qualified measurements or design assertions; irrelevant properties are not forced onto every class.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ], "questions": [ { "id": "q-properties-1", "kind": "classification", "text": "Which physical property set is applicable to the selected asset class and which fields are inapplicable?", "answer_data": [ "property_profile", "applicable_fields", "inapplicable_reason" ] }, { "id": "q-properties-2", "kind": "measurement", "text": "What values and units describe the material and dimensions at the stated spans?", "answer_data": [ "property_code", "value", "unit", "span", "tolerance", "method" ] }, { "id": "q-properties-3", "kind": "provenance", "text": "Which values are designed, installed, measured or inferred and what supports them?", "answer_data": [ "assertion_type", "source_revision", "observer", "observation_time", "confidence" ] }, { "id": "q-properties-4", "kind": "validation", "text": "Which incompatible units, missing tolerances or conflicting property claims prevent using a value?", "answer_data": [ "unit_check", "tolerance_status", "conflict_set", "use_restriction" ] } ], "data_elements": [ { "id": "data-physical-properties", "name": "Physical properties", "description": "Typed property assertions with span, units, tolerance, method, conditions, time and provenance.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] }, { "id": "data-material-component-links", "name": "Material and component links", "description": "Class-specific material or component references; detailed component masters stay external.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-properties", "name": "Span property schedule", "description": "Versioned evidence projection for material and dimensional properties. Preserve source and master references, unknowns, recipient scope and revision history.", "media_or_form": [ "Logical record set", "Human-readable evidence view" ], "serial": true, "identity_strategy": "Authoritative master-system artifact ID first; governed IRI second; Dimension UUID third. Asset ID and artifact ID remain distinct; immutable revision and content digest identify a rendition, never the physical asset. Dates are attributes only.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-interfaces", "name": "Interfaces and operating envelope", "description": "Asset-specific interfaces and operating envelope with explicit evidence and external master boundaries.", "rationale": "Groups independently answerable concerns needed to interpret a managed physical extent; proposed structure grounded in the cited conceptual evidence.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-007" ], "layers": [ { "id": "layer-network", "name": "Network and neighboring assets", "description": "Asset membership and interface references connect to externally mastered topology. A geometric crossing is not evidence of physical connection; a graph link is not automatically the same thing as an asset segment.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ], "findings": [ { "id": "finding-network", "name": "Network and neighboring assets", "description": "Asset membership and interface references connect to externally mastered topology. A geometric crossing is not evidence of physical connection; a graph link is not automatically the same thing as an asset segment.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ], "questions": [ { "id": "q-network-1", "kind": "relationship", "text": "Which versioned infrastructure network and topology elements reference this asset?", "answer_data": [ "network_reference", "topology_version", "link_mapping", "mapping_cardinality" ] }, { "id": "q-network-2", "kind": "composition", "text": "Which point facilities, joints, structures or parallel assets have separate identities at its interfaces?", "answer_data": [ "related_asset_id", "interface_id", "role", "span" ] }, { "id": "q-network-3", "kind": "constraint", "text": "Which connection, separation or crossing assertion is evidenced at each interface?", "answer_data": [ "interface_type", "evidence", "directionality", "uncertainty" ] }, { "id": "q-network-4", "kind": "interoperability", "text": "How are one-to-many mappings between network links and management segments represented without copying graph authority?", "answer_data": [ "mapping_table", "version_pins", "loss_report", "graph_master" ] } ], "data_elements": [ { "id": "data-network-bindings", "name": "Network bindings", "description": "Network and graph element references with versioned many-to-many asset mappings.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] }, { "id": "data-interface-claims", "name": "Interface claims", "description": "Evidence-qualified connections, crossings and adjacent assets; no network traversal implementation.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "artifact-network", "name": "Interface and network binding map", "description": "Versioned evidence projection for network and neighboring assets. Preserve source and master references, unknowns, recipient scope and revision history.", "media_or_form": [ "Logical record set", "Human-readable evidence view" ], "serial": true, "identity_strategy": "Authoritative master-system artifact ID first; governed IRI second; Dimension UUID third. Asset ID and artifact ID remain distinct; immutable revision and content digest identify a rendition, never the physical asset. Dates are attributes only.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-capability", "name": "Capability, restrictions and hazards", "description": "Intended service and declared design capability differ from observed behavior, present availability and authorized operating limits. Hazard and failure information stays at policy and evidence level; this model does not control equipment.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ], "findings": [ { "id": "finding-capability", "name": "Capability, restrictions and hazards", "description": "Intended service and declared design capability differ from observed behavior, present availability and authorized operating limits. Hazard and failure information stays at policy and evidence level; this model does not control equipment.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ], "questions": [ { "id": "q-capability-1", "kind": "definition", "text": "What transport, conveyance or communication service is the asset intended to support?", "answer_data": [ "service_role", "class_profile", "service_master_reference" ] }, { "id": "q-capability-2", "kind": "constraint", "text": "Which evidenced design limits and authorized operating restrictions apply to which spans and periods?", "answer_data": [ "limit_type", "value", "unit", "design_or_operational", "authority", "valid_interval" ] }, { "id": "q-capability-3", "kind": "state", "text": "What observed behavior or availability report differs from the declared capability?", "answer_data": [ "observation_reference", "availability_state", "discrepancy", "assessed_at" ] }, { "id": "q-capability-4", "kind": "requirement", "text": "Which hazard categories, failure modes and escalation policies govern use of incomplete or adverse evidence?", "answer_data": [ "hazard_category", "failure_mode", "policy_reference", "escalation_role", "uncertainty" ] } ], "data_elements": [ { "id": "data-capability-claims", "name": "Capability claims", "description": "Profile-scoped declared capacity and limits; no universal engineering threshold.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] }, { "id": "data-restriction-evidence", "name": "Restriction evidence", "description": "External operational decision and hazard-policy references with extent and expiry.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-capability", "name": "Capability and restriction register", "description": "Versioned evidence projection for capability, restrictions and hazards. Preserve source and master references, unknowns, recipient scope and revision history.", "media_or_form": [ "Logical record set", "Human-readable evidence view" ], "serial": true, "identity_strategy": "Authoritative master-system artifact ID first; governed IRI second; Dimension UUID third. Asset ID and artifact ID remain distinct; immutable revision and content digest identify a rendition, never the physical asset. Dates are attributes only.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-condition", "name": "Condition and intervention evidence", "description": "Asset-specific condition and intervention evidence with explicit evidence and external master boundaries.", "rationale": "Groups independently answerable concerns needed to interpret a managed physical extent; proposed structure grounded in the cited conceptual evidence.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "layers": [ { "id": "layer-observations", "name": "Inspection and condition evidence", "description": "Condition is an assessment under a named scheme over a sampled extent and time. Missing or stale inspection evidence is unknown, not a healthy rating; an aggregate must disclose uninspected portions.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "findings": [ { "id": "finding-observations", "name": "Inspection and condition evidence", "description": "Condition is an assessment under a named scheme over a sampled extent and time. Missing or stale inspection evidence is unknown, not a healthy rating; an aggregate must disclose uninspected portions.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "q-observations-1", "kind": "evidence", "text": "Which inspection or observation assessed which property and exact asset span?", "answer_data": [ "inspection_reference", "feature_of_interest", "observed_property", "sampled_span" ] }, { "id": "q-observations-2", "kind": "measurement", "text": "What result, rating scheme, procedure and uncertainty qualify the assessment?", "answer_data": [ "result", "unit_or_code", "scheme_version", "procedure", "uncertainty" ] }, { "id": "q-observations-3", "kind": "temporal", "text": "When did the observed condition apply, when was its result issued and when was it ingested?", "answer_data": [ "phenomenon_time", "result_time", "ingestion_time", "freshness_policy" ] }, { "id": "q-observations-4", "kind": "quality", "text": "Which inaccessible or uninspected portions and conflicting ratings limit a condition summary?", "answer_data": [ "coverage_mask", "unknown_spans", "conflict_set", "aggregation_rule", "denominator" ] } ], "data_elements": [ { "id": "data-condition-claims", "name": "Condition claims", "description": "Observation references, rating scheme and sampled extent, with separate phenomenon and result times.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "data-coverage-quality", "name": "Coverage quality", "description": "Coverage masks, unknowns, freshness and aggregation caveats.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-observations", "name": "Condition evidence index", "description": "Versioned evidence projection for inspection and condition evidence. Preserve source and master references, unknowns, recipient scope and revision history.", "media_or_form": [ "Logical record set", "Human-readable evidence view" ], "serial": true, "identity_strategy": "Authoritative master-system artifact ID first; governed IRI second; Dimension UUID third. Asset ID and artifact ID remain distinct; immutable revision and content digest identify a rendition, never the physical asset. Dates are attributes only.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-interventions", "name": "Defects and work references", "description": "Defect assertions preserve their observed location and severity scheme. Work orders, permits and engineering acceptance remain external records; a completed work order alone cannot close a defect or establish safety.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "findings": [ { "id": "finding-interventions", "name": "Defects and work references", "description": "Defect assertions preserve their observed location and severity scheme. Work orders, permits and engineering acceptance remain external records; a completed work order alone cannot close a defect or establish safety.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "q-interventions-1", "kind": "state", "text": "Which defect assertions remain open, disputed, superseded or supported as resolved?", "answer_data": [ "defect_reference", "span", "severity_scheme", "assertion_status", "evidence" ] }, { "id": "q-interventions-2", "kind": "process", "text": "Which inspection, repair or renewal work record addresses the affected extent?", "answer_data": [ "work_record_reference", "affected_span", "proposed_action", "responsible_role" ] }, { "id": "q-interventions-3", "kind": "authority", "text": "Which qualified acceptance evidence supports a resolution or release from restriction?", "answer_data": [ "acceptance_reference", "authority", "assessed_scope", "effective_time" ] }, { "id": "q-interventions-4", "kind": "exception", "text": "What happens when reported work completion conflicts with subsequent observations?", "answer_data": [ "contrary_observation", "conflict_owner", "retained_restriction", "next_review" ] } ], "data_elements": [ { "id": "data-defect-links", "name": "Defect links", "description": "Defect master references with located assertions and scheme-scoped severity.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "data-work-acceptance-links", "name": "Work and acceptance links", "description": "External work, permit and acceptance references; local linking has no physical or operational effect.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-interventions", "name": "Defect and intervention evidence register", "description": "Versioned evidence projection for defects and work references. Preserve source and master references, unknowns, recipient scope and revision history.", "media_or_form": [ "Logical record set", "Human-readable evidence view" ], "serial": true, "identity_strategy": "Authoritative master-system artifact ID first; governed IRI second; Dimension UUID third. Asset ID and artifact ID remain distinct; immutable revision and content digest identify a rendition, never the physical asset. Dates are attributes only.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-continuity", "name": "Lifecycle and information continuity", "description": "Asset-specific lifecycle and information continuity with explicit evidence and external master boundaries.", "rationale": "Groups independently answerable concerns needed to interpret a managed physical extent; proposed structure grounded in the cited conceptual evidence.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007" ], "layers": [ { "id": "layer-lifecycle", "name": "Status and retirement history", "description": "Proposed, installed, in-service, restricted, out-of-service, abandoned and removed are profile states, not interchangeable facts. Local record status is distinct from physical existence and operational authority.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ], "findings": [ { "id": "finding-lifecycle", "name": "Status and retirement history", "description": "Proposed, installed, in-service, restricted, out-of-service, abandoned and removed are profile states, not interchangeable facts. Local record status is distinct from physical existence and operational authority.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ], "questions": [ { "id": "q-lifecycle-1", "kind": "lifecycle", "text": "Which evidenced lifecycle state applies to each span under the chosen state vocabulary?", "answer_data": [ "state_code", "vocabulary_version", "span", "evidence" ] }, { "id": "q-lifecycle-2", "kind": "event", "text": "Which commissioning, renewal, transfer or retirement event supports the state transition?", "answer_data": [ "event_reference", "prior_state", "new_state", "authority", "valid_time" ] }, { "id": "q-lifecycle-3", "kind": "constraint", "text": "How is a planned or recorded change kept distinct from confirmed physical change and operating permission?", "answer_data": [ "claim_stage", "confirmation_evidence", "external_authorization", "unresolved_condition" ] }, { "id": "q-lifecycle-4", "kind": "retention", "text": "Which residual location evidence and references must remain after retirement under the adopted retention policy?", "answer_data": [ "retention_basis", "disposition_due", "residual_hazard_reference", "tombstone", "access_scope" ] } ], "data_elements": [ { "id": "data-lifecycle-claims", "name": "Lifecycle claims", "description": "Versioned state assertions over spans with event evidence and effective periods.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] }, { "id": "data-retirement-links", "name": "Retirement links", "description": "Retirement, removal and successor references with retention and residual uncertainty.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-lifecycle", "name": "Lifecycle evidence timeline", "description": "Versioned evidence projection for status and retirement history. Preserve source and master references, unknowns, recipient scope and revision history.", "media_or_form": [ "Logical record set", "Human-readable evidence view" ], "serial": true, "identity_strategy": "Authoritative master-system artifact ID first; governed IRI second; Dimension UUID third. Asset ID and artifact ID remain distinct; immutable revision and content digest identify a rendition, never the physical asset. Dates are attributes only.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-exchange", "name": "Exchange and evidence lineage", "description": "Exchange projections retain subject and record identity separately. Conceptual mappings to external schemas do not constitute conformance; precision loss, withheld fields and unresolved links must remain visible.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006" ], "findings": [ { "id": "finding-exchange", "name": "Exchange and evidence lineage", "description": "Exchange projections retain subject and record identity separately. Conceptual mappings to external schemas do not constitute conformance; precision loss, withheld fields and unresolved links must remain visible.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006" ], "questions": [ { "id": "q-exchange-1", "kind": "interoperability", "text": "Which versioned target schema and mapping profile project the asset without equating it to an alignment or graph edge?", "answer_data": [ "target_schema", "version", "profile", "mapping", "semantic_loss" ] }, { "id": "q-exchange-2", "kind": "provenance", "text": "Which source revisions, transformations and responsible roles generated this record?", "answer_data": [ "source_ids", "source_revisions", "derivation_activity", "attribution", "digest" ] }, { "id": "q-exchange-3", "kind": "security", "text": "Which sensitive geometry or operational details are suppressed for the intended recipient and purpose?", "answer_data": [ "recipient_scope", "withheld_fields", "generalization_method", "policy" ] }, { "id": "q-exchange-4", "kind": "validation", "text": "What unresolved references, stale pins or failed acceptance fixtures block an exchange?", "answer_data": [ "reference_report", "pin_status", "fixture_result", "refusal_reason" ] } ], "data_elements": [ { "id": "data-exchange-bindings", "name": "Exchange bindings", "description": "Explicit schema versions, mappings and information loss; implementation remains a hold.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006" ] }, { "id": "data-evidence-lineage", "name": "Evidence lineage", "description": "Derivation and attribution references with revision pins and integrity digests; not a truth guarantee.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-exchange", "name": "Exchange and provenance manifest", "description": "Versioned evidence projection for exchange and evidence lineage. Preserve source and master references, unknowns, recipient scope and revision history.", "media_or_form": [ "Logical record set", "Human-readable evidence view" ], "serial": true, "identity_strategy": "Authoritative master-system artifact ID first; governed IRI second; Dimension UUID third. Asset ID and artifact ID remain distinct; immutable revision and content digest identify a rendition, never the physical asset. Dates are attributes only.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "function-resolve-identity", "name": "Resolve asset identity", "description": "Proposed, unimplemented local function. Resolve an asset key and class against declared masters without merging ambiguous records.", "inputs": [ "asset key", "namespace", "candidate aliases" ], "outputs": [ "resolved master reference or ambiguity report" ], "preconditions": [ "Read permission and declared master binding" ], "effects": [ "Read-only identity resolution; no asset creation" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "function-check-locations", "name": "Check location and segmentation", "description": "Proposed, unimplemented local function. Assess a proposed reference or partition revision using a supplied rule and calibration.", "inputs": [ "reference revision", "segment intervals", "partition rules", "calibration evidence" ], "outputs": [ "location and interval diagnostics or refused conversion" ], "preconditions": [ "Pinned method, units, direction, branch and time; coordinate transformations require a validated binding" ], "effects": [ "Local diagnostics only; no geometry correction or network edit" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "function-propose-resegmentation", "name": "Propose segment lineage", "description": "Proposed, unimplemented local function. Prepare a versioned local mapping for splits, merges or re-referencing.", "inputs": [ "current segment revision", "proposed spans", "lineage evidence" ], "outputs": [ "reviewable change set and unmapped observation spans" ], "preconditions": [ "Authorized steward; expected revision matches; mapping ambiguity retained" ], "effects": [ "Creates proposed local revision only; no automatic reassignment or external write" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "function-link-condition", "name": "Link condition evidence", "description": "Proposed, unimplemented local function. Attach an existing observation reference to the correct asset and historical extent.", "inputs": [ "observation reference", "span revision", "scheme and time metadata" ], "outputs": [ "local evidence link or mismatch report" ], "preconditions": [ "Evidence permission; resolvable identity; compatible units and observation extent" ], "effects": [ "Adds a local evidence assertion; does not certify condition or clear a restriction" ], "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "function-record-status-evidence", "name": "Record status evidence", "description": "Proposed, unimplemented local function. Record an externally authorized lifecycle or restriction decision as a local assertion.", "inputs": [ "decision reference", "affected span", "effective interval", "expected revision" ], "outputs": [ "new assertion revision or authority conflict" ], "preconditions": [ "Authorized role; validated decision scope; concurrency check; conflicting claims preserved" ], "effects": [ "Updates local claims only; does not commission, close, isolate, excavate or operate physical infrastructure" ], "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] }, { "id": "function-prepare-exchange", "name": "Prepare scoped exchange", "description": "Proposed, unimplemented local function. Project a recipient-authorized view under a supplied mapping profile.", "inputs": [ "record revision", "mapping version", "recipient purpose and scope" ], "outputs": [ "scoped export and loss report or refusal" ], "preconditions": [ "Read/export authority; target schema and reference pins known; sensitivity policy applied" ], "effects": [ "Creates a local artifact only; no external transmission, compliance certification or automated field work" ], "source_refs": [ "SRC-002", "SRC-003", "SRC-006" ] } ], "composition": [ { "target": "WM-BLT-003", "relation": "REFERENCE", "purpose": "Candidate network context corresponding to the registry parent; versioned membership only, no network lifecycle.", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "target": "WM-BLT-010", "relation": "REFERENCE", "purpose": "Candidate utility graph binding where applicable; preserve separate topology authority and cardinality.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "WM-BLT-004", "relation": "REFERENCE", "purpose": "Optional service-point interface references; separate point master.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "WM-BLT-001", "relation": "REFERENCE", "purpose": "Optional supporting or intersected structure references; no copied structure specification.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "WM-BLT-007", "relation": "REFERENCE", "purpose": "Optional construction and renewal work evidence; execution stays with work master.", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] }, { "target": "ISO 19148:2021", "relation": "ALIGN", "purpose": "Conceptual linear location alignment; complete normative mapping and conformance unverified.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "IFC 4.3.2.0 IfcAlignment", "relation": "ALIGN", "purpose": "Positioning representation alignment only; the physical asset is not equated to IfcAlignment.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "INSPIRE Utility Networks Technical Guidelines 3.0", "relation": "ALIGN", "purpose": "Utility spatial-object projection where applicable; no universal legal or telecom applicability claim.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "SSN/SOSA 2017 and PROV-O 2013", "relation": "ALIGN", "purpose": "Conceptual observation and evidence lineage links, not implemented RDF conformance.", "required": false, "source_refs": [ "SRC-005", "SRC-006" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Role-based asset steward and authoritative asset register binding", "Sector and jurisdiction profile, segmentation continuity policy and reference-system stewardship", "Permission, sensitivity, retention and evidence-review policy with accountable roles" ], "namespace_guidance": "Use an adopting Dimension namespace for local IDs. Asset, route, graph, observation and artifact namespaces stay distinct. Master IDs take priority over labels or dates.", "registry_links": [ "vr.wm-blt-009", "WM-BLT-003 candidate network context", "WM-BLT-010 candidate topology binding" ] }, "canon_and_patch": { "canonicalization_rules": [ "Retain the master identifier and immutable revision pins; preserve asserted, measured, inferred and unknown states.", "Normalize units only through explicit, loss-reported conversions; never silently rebase historical measures." ], "patch_rules": [ "Require authorized role, expected revision, reason, affected span and source evidence.", "Keep prior claims and contradictory evidence; propose schema extensions rather than expanding the subject boundary." ], "compatibility_rules": [ "Changing referencing origin, segmentation semantics, class vocabulary or state meaning requires a versioned migration and loss report.", "Optional candidate fields are research design, not an executable instance schema." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier", "Governed global identifier or IRI", "Dimension-assigned UUID or ULID" ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and explicit offset or Z. Keep event/effective time, phenomenon time, result time and ingestion time distinct. Preserve date-only source precision without fabricating a timestamp.", "serial_naming_rule": "Use asset key, artifact kind, stable artifact ID and revision in serial names; timestamps are descriptive attributes, never identity.", "integrity_rule": "Retain source revision and content digest for each rendition; a digest establishes byte integrity, not location accuracy, legal rights or safety." }, "policies": [ "These service rules are proposed local governance, not normative requirements asserted from external sources.", "Exact critical-asset geometry and operational restrictions require need-to-know access; public views may generalize location with disclosure of precision loss.", "No automated operation, closure, isolation, excavation authorization or safety clearance is in scope. Escalate missing or conflicting evidence to qualified roles.", "Rights, jurisdiction, technical limits, inspection intervals and retention schedules require adopting-profile authority." ], "crud": { "read": [ "Resolve subject identity, reference versions, recipient scope and observation freshness; disclose unknown or withheld values." ], "create": [ "Create local records only with an authoritative key or explicitly provisional namespace, stated class, evidence and authorized steward." ], "update": [ "Check expected revision and authority; append a scoped claim and lineage rather than overwriting historical spans." ], "delete": [ "Retire local records with policy-authorized retention, legal holds and minimal tombstones; do not infer physical removal or safe ground from deletion.", "The adopting Dimension owns disposal execution; referenced evidence, rights and work masters retain their own retention policy. Restrict history and erase payloads when lawfully required rather than retaining personal data indefinitely." ] }, "roles": [ { "name": "Asset steward", "responsibilities": [ "Resolve identity and continuity decisions; maintain scoped role bindings." ] }, { "name": "Reference-system custodian", "responsibilities": [ "Approve calibration and segmentation versions; review ambiguous mappings." ] }, { "name": "Qualified condition reviewer", "responsibilities": [ "Assess inspection coverage and conflicting evidence; route safety decisions externally." ] }, { "name": "Evidence and access custodian", "responsibilities": [ "Apply sensitivity and retention policy; preserve lineage and authorized disclosure." ] }, { "name": "Local model agent", "responsibilities": [ "Perform only authorized local read, validation and proposed changes; refuse unresolved authority or stale pins." ] } ], "access": { "default_rule": "Deny disclosure until recipient purpose and least-privilege scope are established; precise geometry and contact details are restricted by default.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Emergency access requires the applicable external policy and recorded authority; it does not arise from agent inference.", "Approved public views may omit or generalize restricted values and must label that limitation." ], "audit_requirements": [ "Record actor role, purpose, asset/revision, scope, evidence and time for local changes and exports.", "Keep access decisions and external audit-record references without owning a separate audit engine." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Nearest adopting Dimension policy and AGENTS.md", "This package AGENTS.md and spec.yaml", "Pinned master references and artifact permissions", "Finding questions, evidence and applicable holds" ] } }, "coverage": { "claim": "Source-grounded proposed common core for one persistent linear physical asset, with selected road, rail and utility evidence. A separate frozen local no-tools self-audit found no critical conflicts. This remains a noncanonical reviewable draft with independent-review, source/version, specialist-profile and executable-conformance holds.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Asset, route, topology and record identities are distinct." }, { "dimension": "lifecycle", "status": "covered", "notes": "Span-level states and externally evidenced transitions; continuity policy explicit." }, { "dimension": "relationships", "status": "covered", "notes": "Optional network, topology, service-point, structure and work references preserve masters." }, { "dimension": "temporal", "status": "covered", "notes": "Effective, observation, result and ingestion times remain distinct." }, { "dimension": "provenance", "status": "covered", "notes": "Revision, derivation and attribution do not certify truth." }, { "dimension": "ownership", "status": "covered", "notes": "Owner, operator, maintainer and steward roles are scoped by span and period." }, { "dimension": "validation", "status": "gap", "notes": "Research schema is validated; instance schemas, acceptance fixtures and technical conformance are not implemented." }, { "dimension": "access", "status": "covered", "notes": "Recipient purpose, precise-location restrictions and generalized views are explicit." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Policy-qualified retirement, holds, tombstones and lawful payload disposal." }, { "dimension": "interoperability", "status": "gap", "notes": "Conceptual standards links only; executable mappings and pinned neighbor packages remain unverified." }, { "dimension": "direct properties", "status": "covered", "notes": "Class-specific values include units, tolerances, methods, conditions, time and provenance." }, { "dimension": "recognition", "status": "covered", "notes": "Survey and marker evidence preserve uncertainty and contradictions." }, { "dimension": "capabilities and actions", "status": "covered", "notes": "Capability, behavior, current state, external permission and proposed local operations are separated." }, { "dimension": "sector coverage", "status": "gap", "notes": "Detailed engineering and safety profiles for roads, rails, pipelines and cables require qualified review." } ], "known_omissions": [ "Independent external provider review is absent.", "Direct source HTTP checks are unattempted under the owner-reported sandbox restriction; statuses and body hashes are unmeasured.", "ISO normative full texts, current versions of all sources and historical report issue date remain unverified.", "Nested instance schemas, coordinate transformations, topology mappings and acceptance fixtures remain unimplemented.", "Sector-specific engineering thresholds, hazards, rights, licensing, privacy and retention profiles require qualified adoption review." ], "conflicts": [], "regional_assumptions": [ "INSPIRE guidance is a European data-model example, not a global rule; telecom scope needs separate review.", "The highway case-study report is historical US practice, not evidence of universal or current requirements.", "The pinned 2017 observation vocabulary is intentional; later editions and compatibility are not assessed." ], "adversarial_checks": [ "Duplicate route labels must not merge separate assets.", "Repeated measures and branching must prevent unqualified coordinate conversion.", "Overlapping observation spans must not fail a management-partition rule automatically.", "A geometric crossing must not create network connectivity.", "Missing inspection, work completion and record retirement must not imply healthy condition, operational permission or physical removal.", "A split must not silently remap old evidence; stale or ambiguous lineage must remain visible." ] }, "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": "Persistent owner-governed physical identity is the root. Segmentation, record revision and alignment changes do not automatically create a new asset. Network, topology, positioning geometry, rights, observations and work retain distinct masters. The registry standalone-mm value is a registry-plane classification, not a competing subject-kind enum." }, "decisions": [ { "concept": "Asset identity and continuity", "disposition": "accepted", "rationale": "The identity finding asks for an explicit replacement and continuity policy. Physical asset, alias, route and record identity remain distinct; no universal rule for retaining identity after renewal is invented." }, { "concept": "Registry parent and candidate composition", "disposition": "qualified", "rationale": "The frozen ledger has no incident relation rows and no legacy input. WM-BLT-003 supplies broader network context, not automatic inheritance. Optional neighbor bindings avoid claiming verified runtime dependencies." }, { "concept": "Alignment and coordinate conversion", "disposition": "qualified", "rationale": "The result does not equate an asset with IfcAlignment. Origin, direction, units, calibration, branch and revision are required for interpretation; ambiguous transformations may be refused. No conversion implementation is claimed." }, { "concept": "Segmentation and historical evidence", "disposition": "accepted", "rationale": "Gaps and overlaps are checked only against a declared partition and period. Independent observation spans may overlap. Many-to-many lineage retains unmapped portions rather than silently moving historical evidence." }, { "concept": "Properties and field recognition", "disposition": "accepted with profile limits", "rationale": "The questions distinguish design, installed, measured and inferred values and ask for units, tolerance, method and uncertainty. Recognition cues are evidence, not proof of identity or proof that buried assets are absent." }, { "concept": "Topology ownership", "disposition": "separated", "rationale": "Membership mappings and interface assertions do not duplicate graph ownership. Geometric crossings do not establish connections, and a graph link need not equal one asset segment." }, { "concept": "Roles and land rights", "disposition": "qualified", "rationale": "Role bindings carry extent and time. Rights and permits are external evidence claims; geometry or a role assignment cannot grant access, title or operational authority. Actual jurisdictional rules remain a profile gap." }, { "concept": "Condition, work and operational permission", "disposition": "separated", "rationale": "Observation times, sampled extents, schemes and unknown coverage qualify condition. Work completion does not resolve a defect or clear a restriction without appropriate evidence. Capability, observed behavior and permission are separate." }, { "concept": "Proposed functions and dangerous effects", "disposition": "accepted as local only", "rationale": "All six functions are explicitly unimplemented proposals with permission or authority preconditions, refusal results and local effects. They cannot operate equipment, execute work, authorize excavation or certify safety." }, { "concept": "Lifecycle and record disposal", "disposition": "accepted with policy dependency", "rationale": "Physical removal, abandonment, operational status and local record retirement are distinct. Referenced masters own their retention policies, while local history supports lawful payload erasure and minimal tombstones rather than indefinite personal-data retention." }, { "concept": "Evidence and source verification", "disposition": "limited", "rationale": "Seven primary sources supply selected conceptual support, including public ISO summaries and historical examples. Direct HTTP was unattempted under the owner-reported restriction. Browser access does not establish measured HTTP results, complete normative review or current applicability." }, { "concept": "Conformance and provider assurance", "disposition": "deferred and held", "rationale": "Candidate object groups, proposed functions and conceptual mappings are not executable instance contracts. This separate Codex audit cannot stand in for an independent provider; no waived-provider nodes or agreement claims are admitted." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped with zero attempts. The separate local Codex no-tools self-audit is not an independent second-provider review.", "Source and version verification remains incomplete. All seven direct HTTP checks are unattempted under the owner-reported sandbox restriction; statuses, redirects and response-body hashes are unmeasured. Selected official browser content was reviewed separately. ISO full normative texts, source currency, the historical report issue date and licensing remain unverified. The coordinator checker is prepared.", "Sector and jurisdiction profiles require qualified review for roads, rails, pipelines and cables, including technical limits, hazard categories, inspection intervals, rights, permits, operating authority, privacy and retention. No engineering safety or legal compliance certification is claimed.", "Nested instance schemas, pinned neighbor packages, linear-reference transformations, IFC/INSPIRE/SSN/PROV mappings and adversarial acceptance fixtures are not implemented or tested. Structural research validity is not runtime conformance.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Complete direct source retrieval and substantive version, licensing and applicability review; obtain the normative material needed for any claimed conformance.", "Develop sector profiles and test repeated measures, branching, split/merge history, mixed segmentation, crossing without connection, stale inspection, partial removal and controlled disclosure.", "Implement nested schemas and version-pinned mappings with refusal and information-loss reports before operational integration.", "Restore independent external review before promotion beyond a noncanonical reviewable draft." ] }, "statistics": { "sources": 7, "bundles": 6, "layers": 12, "findings": 12, "questions": 48, "artifacts": 12, "functions": 6 } }