# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-06T20:08:53Z", "synthesisSha256": "de5e5708db400588b6cc46693844c0f22452112bfe5019e4bf87e2a086818a6d", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-BLT-005", "registryId": "vr.wm-blt-005", "name": "Civil Works", "version": "0.1.0-reviewable", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.BLT.CIV" ], "tags": [ "civil", "works", "phy.blt.civ" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-blt-005-civil-works/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-blt-005", "model": { "registry_id": "vr.wm-blt-005", "model_id": "WM-BLT-005", "name": "Civil Works", "entry_kind": "entity", "purpose": "Describe one enduring civil infrastructure work as an identifiable physical asset, with its extent, engineered fabric, intended function, observed condition and evidence-backed history.", "scope_statement": "One civil infrastructure asset or explicitly bounded work, including engineered ground and site works. A proposed asset can be recorded before it exists; existence, completion, acceptance and service state are separate assertions. The root persists across record revisions and interventions. Multiple parts do not turn the root into a project portfolio. This proposed Vercy boundary is narrower than the legacy U1 building-and-structure umbrella.", "in_scope": [ "Stable work identity, classification, responsibility references and correspondence to external asset records.", "Asset extent, referenced survey or alignment, constituent parts and qualified physical properties.", "Intended service capability and constraints, inspection evidence, maintenance needs and referenced interventions.", "Evidence-backed lifecycle assertions, source lineage, exchange profiles and governed disclosure of this asset record." ], "out_of_scope": [ "Construction project scheduling, procurement, payment, contractor management or execution of works.", "Generic building envelopes and structural calculations, operational facility management, site administration, network topology and route linear-referencing masters.", "Land title, cadastral boundary adjudication, permit issuance, engineering certification, emergency command or physical actuation.", "Detailed geotechnical, hydraulic, pavement, bridge, dam or tunnel design rules and autonomous safety decisions." ], "boundary_notes": [ { "neighbor": "WM-BLT-001 Building / Structure", "distinction": "Generic structural fabric stays in the structural asset master. A bridge or retaining structure may have one master identity with two governed views, or a referenced component identity within a larger civil asset. Do not create duplicate real-world assets merely to populate both cards.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "WM-BLT-007 Construction Work", "distinction": "Projects create, modify or remove an asset. This record carries intervention and acceptance references but never owns work-package execution, contractual completion or certification.", "source_refs": [ "SRC-002" ] }, { "neighbor": "WM-BLT-006 Facility and WM-BLT-008 Site / Campus", "distinction": "Functional operations and site aggregation remain external. An IFC facility class is an exchange concept and is not proof that these Vercy boundaries are identical.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "WM-BLT-003 Infrastructure Network, WM-BLT-009 Linear Infrastructure Asset and WM-BLT-010 Utility Network Topology", "distinction": "Keep network membership, carried services and alignment references. Connectivity, routing, chainage calibration and topology state have external masters; a culvert or embankment is not automatically a network edge.", "source_refs": [ "SRC-002", "SRC-007" ] }, { "neighbor": "Land, ownership, survey and environmental records", "distinction": "Record spatial association and responsible-party authority references, not title or an inferred right to alter land. Natural terrain is context unless an engineered intervention is evidenced; adjacent receptors and permit restrictions remain external evidence.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] } ] }, "sources": [ { "id": "SRC-001", "title": "IFC 4.3.2.0 - IfcFacility", "organization": "buildingSMART International", "url": "https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/lexical/IfcFacility.htm", "version_or_date": "4.3.2.0 IFC4X3_ADD2", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:07:37Z", "relevance": "Section 5.4.3.25: facility types, identity and decomposition. Supports conceptual alignment, not a mandatory mapping or legal ownership assertion." }, { "id": "SRC-002", "title": "InfraGML 1.0 Part 2 - 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:07:37Z", "relevance": "Sections 1, 7.1-7.3 distinguish enduring facilities and parts from improvement projects; geometry and linear referencing dependencies require explicit exchange profiles." }, { "id": "SRC-003", "title": "IFC 4.3.2.0 - IfcEarthworksElement", "organization": "buildingSMART International", "url": "https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/lexical/IfcEarthworksElement.htm", "version_or_date": "4.3.2.0 IFC4X3_ADD2", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:07:37Z", "relevance": "Section 6.6.3.5 recognizes engineered ground elements, including fill and reinforced soil; civil assets need not be building envelopes." }, { "id": "SRC-004", "title": "Green Infrastructure Installation, Operation, and Maintenance", "organization": "United States Environmental Protection Agency", "url": "https://www.epa.gov/green-infrastructure/green-infrastructure-installation-operation-and-maintenance", "version_or_date": "Undated living guidance, browser reviewed 2026-10-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:07:37Z", "relevance": "Installation and maintenance sections support inspection, responsibility and maintenance-record questions for engineered stormwater assets; local codes govern actual obligations." }, { "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:07:37Z", "relevance": "SOSA observation, feature of interest, procedure, result, phenomenon time and result time support qualified asset observations; no safety certification follows from these terms." }, { "id": "SRC-006", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/2013/REC-prov-o-20130430/", "version_or_date": "Recommendation 2013-04-30", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:07:37Z", "relevance": "Starting-point and expanded terms support attribution, activity, derivation and revision links. Provenance is distinct from truth, title, access permission and engineering acceptance." }, { "id": "SRC-007", "title": "LandInfra / InfraGML standards overview", "organization": "Open Geospatial Consortium", "url": "https://www.ogc.org/standards/infragml/", "version_or_date": "Living catalogue, LandInfra 1.0 and InfraGML 1.0 listings, reviewed 2026-10-06", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-06T20:07:37Z", "relevance": "Overview distinguishes facilities, land, survey, alignment and division of land. Initial LandInfra release excludes wet infrastructure coverage; water-related mappings remain a gap." } ], "structure": { "bundles": [ { "id": "identity-stewardship", "name": "Identity and stewardship", "description": "Identify the asset and accountable roles without deriving ownership from a data export.", "rationale": "Proposed coherent asset concern; the cited evidence informs the questions, while the adopting profile must specify enforceable fields and rules.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006" ], "layers": [ { "id": "identity-layer", "name": "Work identity and class", "description": "A proposed identity crosswalk distinguishes the physical work, its record revisions and any project that changes it.", "source_refs": [ "SRC-001", "SRC-002" ], "findings": [ { "id": "identity-finding", "name": "Work identity and class", "description": "A proposed identity crosswalk distinguishes the physical work, its record revisions and any project that changes it.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "identity-question-1", "text": "Which master identifier denotes this civil work and which aliases refer to the same asset?", "kind": "identity", "answer_data": [ "identity-data-1", "Master system, master identifier, local stable identifier, alias issuer, match evidence and unresolved duplicates", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] }, { "id": "identity-question-2", "text": "Which civil asset class and inclusion boundary apply to this occurrence?", "kind": "classification", "answer_data": [ "identity-data-2", "Class code, scheme and version, physical scope statement, inclusion and exclusion criteria", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] }, { "id": "identity-question-3", "text": "How is a proposed, abandoned or partly built work distinguished from an existing accepted asset?", "kind": "exception", "answer_data": [ "identity-data-3", "Existence assertion, lifecycle state, affected extent, evidence reference and uncertainty", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] } ], "data_elements": [ { "id": "identity-data-1", "name": "Work identity and class answer group 1", "description": "Master system, master identifier, local stable identifier, alias issuer, match evidence and unresolved duplicates. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "identity-data-2", "name": "Work identity and class answer group 2", "description": "Class code, scheme and version, physical scope statement, inclusion and exclusion criteria. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "identity-data-3", "name": "Work identity and class answer group 3", "description": "Existence assertion, lifecycle state, affected extent, evidence reference and uncertainty. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "identity-artifact", "name": "Asset identity crosswalk", "description": "Proposed independently identifiable, revisioned evidence artifact for work identity and class. Preserve source links and issuer; an upload is not an approval.", "media_or_form": [ "Structured record", "Human-readable report with linked data" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first, governed IRI second, adopting Dimension UUID or ULID otherwise. Stable artifact identity plus immutable revision and content digest; dates are metadata, never sole identity.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null } ] }, { "id": "responsibility-layer", "name": "Responsibility and authority", "description": "A proposed responsibility record separates title, maintenance duty, operation and data stewardship; holding a record grants no power to change the asset.", "source_refs": [ "SRC-004", "SRC-006" ], "findings": [ { "id": "responsibility-finding", "name": "Responsibility and authority", "description": "A proposed responsibility record separates title, maintenance duty, operation and data stewardship; holding a record grants no power to change the asset.", "source_refs": [ "SRC-004", "SRC-006" ], "questions": [ { "id": "responsibility-question-1", "text": "Which parties hold title, operation, maintenance and record stewardship responsibilities for this work?", "kind": "ownership", "answer_data": [ "responsibility-data-1", "Role, party reference, governed extent, effective interval and unknown or disputed responsibility", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] }, { "id": "responsibility-question-2", "text": "What evidence authorizes a party to approve a civil asset record change?", "kind": "authority", "answer_data": [ "responsibility-data-2", "Authority reference, delegated scope, expiry, approving role and approval evidence", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] }, { "id": "responsibility-question-3", "text": "When do responsibility transfers take effect and what obligations remain unresolved?", "kind": "temporal", "answer_data": [ "responsibility-data-3", "Transfer reference, effective time, recorded time, predecessor and successor roles, unresolved obligations", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] } ], "data_elements": [ { "id": "responsibility-data-1", "name": "Responsibility and authority answer group 1", "description": "Role, party reference, governed extent, effective interval and unknown or disputed responsibility. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "responsibility-data-2", "name": "Responsibility and authority answer group 2", "description": "Authority reference, delegated scope, expiry, approving role and approval evidence. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "responsibility-data-3", "name": "Responsibility and authority answer group 3", "description": "Transfer reference, effective time, recorded time, predecessor and successor roles, unresolved obligations. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "responsibility-artifact", "name": "Responsibility assignment record", "description": "Proposed independently identifiable, revisioned evidence artifact for responsibility and authority. Preserve source links and issuer; an upload is not an approval.", "media_or_form": [ "Structured record", "Human-readable report with linked data" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first, governed IRI second, adopting Dimension UUID or ULID otherwise. Stable artifact identity plus immutable revision and content digest; dates are metadata, never sole identity.", "source_refs": [ "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "location-context", "name": "Location and context", "description": "Bound the work spatially and declare externally mastered interfaces.", "rationale": "Proposed coherent asset concern; the cited evidence informs the questions, while the adopting profile must specify enforceable fields and rules.", "source_refs": [ "SRC-002", "SRC-004", "SRC-005", "SRC-007" ], "layers": [ { "id": "extent-layer", "name": "Spatial extent and recognition", "description": "A proposed spatial envelope records what a survey or model represents, retaining coordinate and accuracy context. Geometry helps recognize the work but is not its identity.", "source_refs": [ "SRC-002", "SRC-005", "SRC-007" ], "findings": [ { "id": "extent-finding", "name": "Spatial extent and recognition", "description": "A proposed spatial envelope records what a survey or model represents, retaining coordinate and accuracy context. Geometry helps recognize the work but is not its identity.", "source_refs": [ "SRC-002", "SRC-005", "SRC-007" ], "questions": [ { "id": "extent-question-1", "text": "What horizontal and vertical extent identifies the surveyed civil asset?", "kind": "spatial", "answer_data": [ "extent-data-1", "Geometry reference, coordinate reference system, vertical datum, axis order, units and covered extent", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] }, { "id": "extent-question-2", "text": "Which survey method and accuracy qualify the location or dimensions?", "kind": "measurement", "answer_data": [ "extent-data-2", "Survey reference, method, observation time, tolerance or uncertainty, occlusion and coverage limits", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] }, { "id": "extent-question-3", "text": "How are design geometry, surveyed as-built geometry and later observations distinguished?", "kind": "quality", "answer_data": [ "extent-data-3", "Representation purpose, revision, valid time, surveyed extent, discrepancy and reconciliation state", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] } ], "data_elements": [ { "id": "extent-data-1", "name": "Spatial extent and recognition answer group 1", "description": "Geometry reference, coordinate reference system, vertical datum, axis order, units and covered extent. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005", "SRC-007" ] }, { "id": "extent-data-2", "name": "Spatial extent and recognition answer group 2", "description": "Survey reference, method, observation time, tolerance or uncertainty, occlusion and coverage limits. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005", "SRC-007" ] }, { "id": "extent-data-3", "name": "Spatial extent and recognition answer group 3", "description": "Representation purpose, revision, valid time, surveyed extent, discrepancy and reconciliation state. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "extent-artifact", "name": "Spatial representation manifest", "description": "Proposed independently identifiable, revisioned evidence artifact for spatial extent and recognition. Preserve source links and issuer; an upload is not an approval.", "media_or_form": [ "Structured record", "Human-readable report with linked data" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first, governed IRI second, adopting Dimension UUID or ULID otherwise. Stable artifact identity plus immutable revision and content digest; dates are metadata, never sole identity.", "source_refs": [ "SRC-002", "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "interfaces-layer", "name": "Context and external interfaces", "description": "A proposed interface register locates the work among surrounding land, structures, services and receptors without copying their master records.", "source_refs": [ "SRC-002", "SRC-004", "SRC-007" ], "findings": [ { "id": "interfaces-finding", "name": "Context and external interfaces", "description": "A proposed interface register locates the work among surrounding land, structures, services and receptors without copying their master records.", "source_refs": [ "SRC-002", "SRC-004", "SRC-007" ], "questions": [ { "id": "interfaces-question-1", "text": "Which parcels, structures, networks or adjacent assets intersect, support or are served by this work?", "kind": "relationship", "answer_data": [ "interfaces-data-1", "Target identity, relation type, interface location, effective interval and evidence", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] }, { "id": "interfaces-question-2", "text": "Which recorded land, environmental or public-access restrictions constrain use or maintenance?", "kind": "constraint", "answer_data": [ "interfaces-data-2", "Restriction or permit reference, jurisdiction, affected extent, applicability, expiry and responsible reviewer", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] }, { "id": "interfaces-question-3", "text": "Which external alignment or topology version locates a shared civil interface?", "kind": "interoperability", "answer_data": [ "interfaces-data-3", "External model identity and version, alignment or node reference, station convention, transform and unresolved match", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] } ], "data_elements": [ { "id": "interfaces-data-1", "name": "Context and external interfaces answer group 1", "description": "Target identity, relation type, interface location, effective interval and evidence. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-007" ] }, { "id": "interfaces-data-2", "name": "Context and external interfaces answer group 2", "description": "Restriction or permit reference, jurisdiction, affected extent, applicability, expiry and responsible reviewer. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-007" ] }, { "id": "interfaces-data-3", "name": "Context and external interfaces answer group 3", "description": "External model identity and version, alignment or node reference, station convention, transform and unresolved match. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-007" ] } ], "artifacts": [ { "id": "interfaces-artifact", "name": "Asset interface register", "description": "Proposed independently identifiable, revisioned evidence artifact for context and external interfaces. Preserve source links and issuer; an upload is not an approval.", "media_or_form": [ "Structured record", "Human-readable report with linked data" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first, governed IRI second, adopting Dimension UUID or ULID otherwise. Stable artifact identity plus immutable revision and content digest; dates are metadata, never sole identity.", "source_refs": [ "SRC-002", "SRC-004", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "physical-fabric", "name": "Physical fabric", "description": "Describe component references and qualified physical properties.", "rationale": "Proposed coherent asset concern; the cited evidence informs the questions, while the adopting profile must specify enforceable fields and rules.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005" ], "layers": [ { "id": "parts-layer", "name": "Engineered fabric and parts", "description": "A proposed composition map includes engineered ground as well as constructed components. Spatial containment, load-bearing association and shared service are different relations.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "findings": [ { "id": "parts-finding", "name": "Engineered fabric and parts", "description": "A proposed composition map includes engineered ground as well as constructed components. Spatial containment, load-bearing association and shared service are different relations.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "questions": [ { "id": "parts-question-1", "text": "Which maintainable components and engineered ground elements belong to this work?", "kind": "composition", "answer_data": [ "parts-data-1", "Component master reference, role, extent, inclusion rule, parent relationship and validity interval", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] }, { "id": "parts-question-2", "text": "What evidence distinguishes engineered fill or stabilization from pre-existing ground?", "kind": "definition", "answer_data": [ "parts-data-2", "Element type, intervention evidence, survey reference, inferred boundary and confidence", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] }, { "id": "parts-question-3", "text": "How are shared components assigned without duplicating asset identity or ownership?", "kind": "exception", "answer_data": [ "parts-data-3", "Shared master reference, participating assets, responsibility scope, allocation rule and unresolved dispute", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] } ], "data_elements": [ { "id": "parts-data-1", "name": "Engineered fabric and parts answer group 1", "description": "Component master reference, role, extent, inclusion rule, parent relationship and validity interval. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "parts-data-2", "name": "Engineered fabric and parts answer group 2", "description": "Element type, intervention evidence, survey reference, inferred boundary and confidence. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "parts-data-3", "name": "Engineered fabric and parts answer group 3", "description": "Shared master reference, participating assets, responsibility scope, allocation rule and unresolved dispute. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "parts-artifact", "name": "Fabric composition manifest", "description": "Proposed independently identifiable, revisioned evidence artifact for engineered fabric and parts. Preserve source links and issuer; an upload is not an approval.", "media_or_form": [ "Structured record", "Human-readable report with linked data" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first, governed IRI second, adopting Dimension UUID or ULID otherwise. Stable artifact identity plus immutable revision and content digest; dates are metadata, never sole identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null } ] }, { "id": "properties-layer", "name": "Physical properties and materials", "description": "A proposed property register separates specified, measured and inferred values. Missing test results are unknown; material labels do not certify capacity.", "source_refs": [ "SRC-003", "SRC-005" ], "findings": [ { "id": "properties-finding", "name": "Physical properties and materials", "description": "A proposed property register separates specified, measured and inferred values. Missing test results are unknown; material labels do not certify capacity.", "source_refs": [ "SRC-003", "SRC-005" ], "questions": [ { "id": "properties-question-1", "text": "Which dimensions or material properties were measured for each relevant component?", "kind": "measurement", "answer_data": [ "properties-data-1", "Subject reference, property code, result, unit, method, conditions, tolerance, uncertainty and time", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] }, { "id": "properties-question-2", "text": "Which design, sample or test record supports a physical property assertion?", "kind": "provenance", "answer_data": [ "properties-data-2", "Evidence reference, sampling location, laboratory or author reference, revision and representativeness limits", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] }, { "id": "properties-question-3", "text": "Which material or location records require restricted handling under an adopted policy?", "kind": "security", "answer_data": [ "properties-data-3", "Classification, policy reference, authorized roles, redaction rule and review date; controlled materials remain policy-level references", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] } ], "data_elements": [ { "id": "properties-data-1", "name": "Physical properties and materials answer group 1", "description": "Subject reference, property code, result, unit, method, conditions, tolerance, uncertainty and time. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-005" ] }, { "id": "properties-data-2", "name": "Physical properties and materials answer group 2", "description": "Evidence reference, sampling location, laboratory or author reference, revision and representativeness limits. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-005" ] }, { "id": "properties-data-3", "name": "Physical properties and materials answer group 3", "description": "Classification, policy reference, authorized roles, redaction rule and review date; controlled materials remain policy-level references. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "properties-artifact", "name": "Qualified property register", "description": "Proposed independently identifiable, revisioned evidence artifact for physical properties and materials. Preserve source links and issuer; an upload is not an approval.", "media_or_form": [ "Structured record", "Human-readable report with linked data" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first, governed IRI second, adopting Dimension UUID or ULID otherwise. Stable artifact identity plus immutable revision and content digest; dates are metadata, never sole identity.", "source_refs": [ "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "service-condition", "name": "Service and condition", "description": "Separate intended capability, permission and observed performance.", "rationale": "Proposed coherent asset concern; the cited evidence informs the questions, while the adopting profile must specify enforceable fields and rules.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006" ], "layers": [ { "id": "capability-layer", "name": "Intended function and service constraints", "description": "A proposed capability record distinguishes intended service, qualified assessment and authorized operation. It neither calculates structural capacity nor authorizes access.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ], "findings": [ { "id": "capability-finding", "name": "Intended function and service constraints", "description": "A proposed capability record distinguishes intended service, qualified assessment and authorized operation. It neither calculates structural capacity nor authorizes access.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ], "questions": [ { "id": "capability-question-1", "text": "Which intended service and acceptance criteria are assigned to the civil asset?", "kind": "requirement", "answer_data": [ "capability-data-1", "Service purpose, requirement reference and revision, applicable extent, acceptance authority and exclusions", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] }, { "id": "capability-question-2", "text": "Which operating limits and hazard controls are supported by a qualified assessment?", "kind": "constraint", "answer_data": [ "capability-data-2", "Assessment reference, limit and units, conditions, expiry, responsible authority and escalation policy", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] }, { "id": "capability-question-3", "text": "What evidence distinguishes available, restricted, closed and unknown service states?", "kind": "state", "answer_data": [ "capability-data-3", "State assertion, affected part, valid interval, issuer, decision reference and uncertainty", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] } ], "data_elements": [ { "id": "capability-data-1", "name": "Intended function and service constraints answer group 1", "description": "Service purpose, requirement reference and revision, applicable extent, acceptance authority and exclusions. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "id": "capability-data-2", "name": "Intended function and service constraints answer group 2", "description": "Assessment reference, limit and units, conditions, expiry, responsible authority and escalation policy. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "id": "capability-data-3", "name": "Intended function and service constraints answer group 3", "description": "State assertion, affected part, valid interval, issuer, decision reference and uncertainty. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "capability-artifact", "name": "Service capability statement", "description": "Proposed independently identifiable, revisioned evidence artifact for intended function and service constraints. Preserve source links and issuer; an upload is not an approval.", "media_or_form": [ "Structured record", "Human-readable report with linked data" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first, governed IRI second, adopting Dimension UUID or ULID otherwise. Stable artifact identity plus immutable revision and content digest; dates are metadata, never sole identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "condition-layer", "name": "Observation and condition", "description": "A proposed condition record binds every result to its inspected extent, procedure and time. An uninspected part cannot inherit a favorable grade from its neighbor.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "findings": [ { "id": "condition-finding", "name": "Observation and condition", "description": "A proposed condition record binds every result to its inspected extent, procedure and time. An uninspected part cannot inherit a favorable grade from its neighbor.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ], "questions": [ { "id": "condition-question-1", "text": "What inspection observations support the current condition assertion?", "kind": "evidence", "answer_data": [ "condition-data-1", "Feature of interest, observed property, method, result, assessor or sensor, evidence and inspection coverage", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] }, { "id": "condition-question-2", "text": "When was the condition observed and when was its result recorded or superseded?", "kind": "temporal", "answer_data": [ "condition-data-2", "Phenomenon time, result time, ingestion time, assessment revision and freshness policy", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] }, { "id": "condition-question-3", "text": "Which defects, missing coverage or conflicting assessments require review?", "kind": "quality", "answer_data": [ "condition-data-3", "Defect location, classification scheme, uncertainty, competing evidence, review status and responsible assessor", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] } ], "data_elements": [ { "id": "condition-data-1", "name": "Observation and condition answer group 1", "description": "Feature of interest, observed property, method, result, assessor or sensor, evidence and inspection coverage. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "condition-data-2", "name": "Observation and condition answer group 2", "description": "Phenomenon time, result time, ingestion time, assessment revision and freshness policy. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] }, { "id": "condition-data-3", "name": "Observation and condition answer group 3", "description": "Defect location, classification scheme, uncertainty, competing evidence, review status and responsible assessor. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "condition-artifact", "name": "Condition assessment record", "description": "Proposed independently identifiable, revisioned evidence artifact for observation and condition. Preserve source links and issuer; an upload is not an approval.", "media_or_form": [ "Structured record", "Human-readable report with linked data" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first, governed IRI second, adopting Dimension UUID or ULID otherwise. Stable artifact identity plus immutable revision and content digest; dates are metadata, never sole identity.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "asset-lifecycle", "name": "Asset lifecycle", "description": "Connect origin, service entry and interventions while preserving identity decisions.", "rationale": "Proposed coherent asset concern; the cited evidence informs the questions, while the adopting profile must specify enforceable fields and rules.", "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ], "layers": [ { "id": "acceptance-layer", "name": "Origin and entry into service", "description": "A proposed origin record keeps work completion, handover, acceptance and service entry as separately evidenced assertions; historic assets may lack some records.", "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ], "findings": [ { "id": "acceptance-finding", "name": "Origin and entry into service", "description": "A proposed origin record keeps work completion, handover, acceptance and service entry as separately evidenced assertions; historic assets may lack some records.", "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ], "questions": [ { "id": "acceptance-question-1", "text": "Which evidence establishes the origin and current lifecycle stage of this work?", "kind": "lifecycle", "answer_data": [ "acceptance-data-1", "Creation or historic provenance reference, stage, applicable extent, date precision and confidence", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] }, { "id": "acceptance-question-2", "text": "Who accepted which completed extent and under what conditions or reservations?", "kind": "authority", "answer_data": [ "acceptance-data-2", "Acceptance record, competent role, scope, date, exceptions, outstanding defects and evidence revision", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] }, { "id": "acceptance-question-3", "text": "Which recorded event permits an asserted entry into service?", "kind": "event", "answer_data": [ "acceptance-data-3", "Service-entry decision reference, event time, issuer, extent, conditions and distinction from physical completion", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] } ], "data_elements": [ { "id": "acceptance-data-1", "name": "Origin and entry into service answer group 1", "description": "Creation or historic provenance reference, stage, applicable extent, date precision and confidence. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] }, { "id": "acceptance-data-2", "name": "Origin and entry into service answer group 2", "description": "Acceptance record, competent role, scope, date, exceptions, outstanding defects and evidence revision. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] }, { "id": "acceptance-data-3", "name": "Origin and entry into service answer group 3", "description": "Service-entry decision reference, event time, issuer, extent, conditions and distinction from physical completion. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "acceptance-artifact", "name": "Origin and acceptance dossier", "description": "Proposed independently identifiable, revisioned evidence artifact for origin and entry into service. Preserve source links and issuer; an upload is not an approval.", "media_or_form": [ "Structured record", "Human-readable report with linked data" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first, governed IRI second, adopting Dimension UUID or ULID otherwise. Stable artifact identity plus immutable revision and content digest; dates are metadata, never sole identity.", "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "intervention-layer", "name": "Maintenance and asset continuity", "description": "A proposed intervention history links work records to resulting asset assertions. Physical replacement, logical identity continuity and record retirement require explicit decisions.", "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ], "findings": [ { "id": "intervention-finding", "name": "Maintenance and asset continuity", "description": "A proposed intervention history links work records to resulting asset assertions. Physical replacement, logical identity continuity and record retirement require explicit decisions.", "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ], "questions": [ { "id": "intervention-question-1", "text": "Which inspection finding or policy triggers the next proposed maintenance intervention?", "kind": "process", "answer_data": [ "intervention-data-1", "Finding reference, maintenance-plan revision, trigger, due basis, assigned responsibility and unresolved need", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] }, { "id": "intervention-question-2", "text": "Which asset parts changed after an intervention and what evidence supports the new state?", "kind": "lifecycle", "answer_data": [ "intervention-data-2", "External work reference, before and after revisions, affected components, completion evidence and review state", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] }, { "id": "intervention-question-3", "text": "How are replacement, abandonment or removal recorded while applying retention and disposal rules?", "kind": "retention", "answer_data": [ "intervention-data-3", "Identity-continuity decision, successor reference, retired extent, evidence, retention schedule, legal hold and disposition authority", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] } ], "data_elements": [ { "id": "intervention-data-1", "name": "Maintenance and asset continuity answer group 1", "description": "Finding reference, maintenance-plan revision, trigger, due basis, assigned responsibility and unresolved need. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] }, { "id": "intervention-data-2", "name": "Maintenance and asset continuity answer group 2", "description": "External work reference, before and after revisions, affected components, completion evidence and review state. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] }, { "id": "intervention-data-3", "name": "Maintenance and asset continuity answer group 3", "description": "Identity-continuity decision, successor reference, retired extent, evidence, retention schedule, legal hold and disposition authority. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "intervention-artifact", "name": "Intervention and continuity ledger", "description": "Proposed independently identifiable, revisioned evidence artifact for maintenance and asset continuity. Preserve source links and issuer; an upload is not an approval.", "media_or_form": [ "Structured record", "Human-readable report with linked data" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first, governed IRI second, adopting Dimension UUID or ULID otherwise. Stable artifact identity plus immutable revision and content digest; dates are metadata, never sole identity.", "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "evidence-exchange", "name": "Evidence and exchange", "description": "Make record provenance and exchange limitations reviewable.", "rationale": "Proposed coherent asset concern; the cited evidence informs the questions, while the adopting profile must specify enforceable fields and rules.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006", "SRC-007" ], "layers": [ { "id": "lineage-layer", "name": "Evidence and revision lineage", "description": "A proposed evidence index retains the source of each assertion and records corrections without treating a digest or signature as proof of engineering truth.", "source_refs": [ "SRC-005", "SRC-006" ], "findings": [ { "id": "lineage-finding", "name": "Evidence and revision lineage", "description": "A proposed evidence index retains the source of each assertion and records corrections without treating a digest or signature as proof of engineering truth.", "source_refs": [ "SRC-005", "SRC-006" ], "questions": [ { "id": "lineage-question-1", "text": "Which source entity, activity and accountable party produced this asset assertion?", "kind": "provenance", "answer_data": [ "lineage-data-1", "Evidence identifier, revision, derivation, producing activity, attribution, time and applicability", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] }, { "id": "lineage-question-2", "text": "What checks support acceptance of an imported report or survey into the evidence index?", "kind": "validation", "answer_data": [ "lineage-data-2", "Origin check, integrity digest, schema profile, subject match, completeness, reviewer and validation outcome", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] }, { "id": "lineage-question-3", "text": "How are contradictory evidence, retracted reports and corrected observations preserved?", "kind": "exception", "answer_data": [ "lineage-data-3", "Competing assertions, supersession or retraction reason, reviewer, effective time and unresolved conflict flag", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] } ], "data_elements": [ { "id": "lineage-data-1", "name": "Evidence and revision lineage answer group 1", "description": "Evidence identifier, revision, derivation, producing activity, attribution, time and applicability. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006" ] }, { "id": "lineage-data-2", "name": "Evidence and revision lineage answer group 2", "description": "Origin check, integrity digest, schema profile, subject match, completeness, reviewer and validation outcome. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006" ] }, { "id": "lineage-data-3", "name": "Evidence and revision lineage answer group 3", "description": "Competing assertions, supersession or retraction reason, reviewer, effective time and unresolved conflict flag. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "lineage-artifact", "name": "Evidence lineage index", "description": "Proposed independently identifiable, revisioned evidence artifact for evidence and revision lineage. Preserve source links and issuer; an upload is not an approval.", "media_or_form": [ "Structured record", "Human-readable report with linked data" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first, governed IRI second, adopting Dimension UUID or ULID otherwise. Stable artifact identity plus immutable revision and content digest; dates are metadata, never sole identity.", "source_refs": [ "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "exchange-layer", "name": "Exchange and permitted views", "description": "A proposed exchange manifest identifies scope, authorization and mapping loss. Reference to an external vocabulary is not a conformance result.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007" ], "findings": [ { "id": "exchange-finding", "name": "Exchange and permitted views", "description": "A proposed exchange manifest identifies scope, authorization and mapping loss. Reference to an external vocabulary is not a conformance result.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007" ], "questions": [ { "id": "exchange-question-1", "text": "Which pinned exchange profile maps the civil asset and what information cannot be represented?", "kind": "interoperability", "answer_data": [ "exchange-data-1", "Schema and version, mapping revision, target identity, units and coordinate mapping, unsupported fields and loss report", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] }, { "id": "exchange-question-2", "text": "Which recipient may receive each asset view and at what level of spatial detail?", "kind": "access", "answer_data": [ "exchange-data-2", "Recipient role, purpose, policy grant, bundle or artifact scope, location generalization, redaction and expiry", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] }, { "id": "exchange-question-3", "text": "Which round-trip and identity checks must pass before an exchange is accepted?", "kind": "validation", "answer_data": [ "exchange-data-3", "Fixture set, expected correspondences, geometry tolerance, revision preservation, permissions check and rejection reason", "Explicit unknown, not-applicable with reason, disputed or supported status; absent is not false." ] } ], "data_elements": [ { "id": "exchange-data-1", "name": "Exchange and permitted views answer group 1", "description": "Schema and version, mapping revision, target identity, units and coordinate mapping, unsupported fields and loss report. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007" ] }, { "id": "exchange-data-2", "name": "Exchange and permitted views answer group 2", "description": "Recipient role, purpose, policy grant, bundle or artifact scope, location generalization, redaction and expiry. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007" ] }, { "id": "exchange-data-3", "name": "Exchange and permitted views answer group 3", "description": "Fixture set, expected correspondences, geometry tolerance, revision preservation, permissions check and rejection reason. Candidate field group; nested schema and required-field profile remain to be implemented.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "exchange-artifact", "name": "Exchange and disclosure manifest", "description": "Proposed independently identifiable, revisioned evidence artifact for exchange and permitted views. Preserve source links and issuer; an upload is not an approval.", "media_or_form": [ "Structured record", "Human-readable report with linked data" ], "serial": true, "identity_strategy": "Authoritative master-system identifier first, governed IRI second, adopting Dimension UUID or ULID otherwise. Stable artifact identity plus immutable revision and content digest; dates are metadata, never sole identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-work", "name": "Register an asset draft", "description": "Proposed and unimplemented local function. Resolve identity before introducing a proposed local asset record.", "inputs": [ "Master identifier or governed provisional identifier", "Scope and class evidence", "External duplicate candidates" ], "outputs": [ "Draft record and identity crosswalk", "Refusal with unresolved identity conflicts" ], "preconditions": [ "Authorized record role, purpose and applicable Dimension policy are resolved.", "Asset identity, evidence access and expected record revision are checked; missing or conflicting authority returns refusal." ], "effects": [ "Creates only a local draft and unresolved-reference flags.", "Record accountable actor, input revisions, decision basis, operation time and outcome in the external audit service." ], "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "link-observation", "name": "Link a qualified observation", "description": "Proposed and unimplemented local function. Bind a report to the inspected asset extent and time.", "inputs": [ "Asset revision", "Observation evidence", "Method, unit and time context" ], "outputs": [ "Observation reference and coverage flags", "Refusal for ambiguous subject or missing qualification" ], "preconditions": [ "Authorized record role, purpose and applicable Dimension policy are resolved.", "Asset identity, evidence access and expected record revision are checked; missing or conflicting authority returns refusal." ], "effects": [ "Adds an evidence-backed local observation assertion; does not certify safety.", "Record accountable actor, input revisions, decision basis, operation time and outcome in the external audit service." ], "source_refs": [ "SRC-005", "SRC-006" ] }, { "id": "record-asset-change", "name": "Record an evidenced asset change", "description": "Proposed and unimplemented local function. Propose a revision from a referenced intervention or acceptance record.", "inputs": [ "Prior asset revision", "External work and approval evidence", "Affected extent and continuity decision" ], "outputs": [ "Candidate revision and change trace", "Refusal for stale revision or unsupported transition" ], "preconditions": [ "Authorized record role, purpose and applicable Dimension policy are resolved.", "Asset identity, evidence access and expected record revision are checked; missing or conflicting authority returns refusal." ], "effects": [ "Records a proposed local state change; does not execute works or grant service permission.", "Record accountable actor, input revisions, decision basis, operation time and outcome in the external audit service." ], "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] }, { "id": "review-maintenance-gap", "name": "Review maintenance evidence gaps", "description": "Proposed and unimplemented local function. Compare record completeness against an explicitly supplied maintenance profile.", "inputs": [ "Current asset and inspection references", "Approved maintenance-profile revision", "Evaluation time" ], "outputs": [ "Missing or stale evidence report", "Unknown result for absent applicability or time basis" ], "preconditions": [ "Authorized record role, purpose and applicable Dimension policy are resolved.", "Asset identity, evidence access and expected record revision are checked; missing or conflicting authority returns refusal." ], "effects": [ "Adds review flags only; does not calculate engineering risk or schedule field actions.", "Record accountable actor, input revisions, decision basis, operation time and outcome in the external audit service." ], "source_refs": [ "SRC-004", "SRC-005" ] }, { "id": "prepare-asset-view", "name": "Prepare an authorized asset view", "description": "Proposed and unimplemented local function. Apply an adopted disclosure and mapping policy to a local projection.", "inputs": [ "Asset revision", "Recipient grant", "Pinned exchange and redaction profiles" ], "outputs": [ "Local view and loss manifest", "Refusal for missing authority or unresolved protected fields" ], "preconditions": [ "Authorized record role, purpose and applicable Dimension policy are resolved.", "Asset identity, evidence access and expected record revision are checked; missing or conflicting authority returns refusal." ], "effects": [ "Creates a local projection with provenance; external delivery is a separate authorized process.", "Record accountable actor, input revisions, decision basis, operation time and outcome in the external audit service." ], "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "propose-retirement", "name": "Propose record retirement", "description": "Proposed and unimplemented local function. Prepare a record continuity decision using physical-state evidence and retention policy.", "inputs": [ "Removal or replacement evidence", "Successor identity if any", "Retention policy and holds" ], "outputs": [ "Retirement proposal and minimal continuity references", "Refusal for absent disposition authority" ], "preconditions": [ "Authorized record role, purpose and applicable Dimension policy are resolved.", "Asset identity, evidence access and expected record revision are checked; missing or conflicting authority returns refusal." ], "effects": [ "Marks a proposal only; no asset demolition, payload destruction or title transfer occurs.", "Record accountable actor, input revisions, decision basis, operation time and outcome in the external audit service." ], "source_refs": [ "SRC-002", "SRC-006" ] } ], "composition": [ { "target": "WM-BLT-001", "relation": "REFERENCE", "purpose": "Proposed binding, not an approved registry relation. Optional structural asset reference or same-master correspondence. Detailed structural fabric, calculations and its lifecycle remain at that master.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "WM-BLT-007", "relation": "REFERENCE", "purpose": "Proposed binding, not an approved registry relation. Optional construction or maintenance work reference. Only the asset effect and supporting acceptance reference are local; project execution is external.", "required": false, "source_refs": [ "SRC-002", "SRC-004" ] }, { "target": "WM-BLT-006", "relation": "REFERENCE", "purpose": "Proposed binding, not an approved registry relation. Optional operating facility reference; the facility operation and service-management lifecycle are external.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "WM-BLT-008", "relation": "REFERENCE", "purpose": "Proposed binding, not an approved registry relation. Optional site or campus membership; site administration is external.", "required": false, "source_refs": [ "SRC-002", "SRC-007" ] }, { "target": "WM-BLT-003", "relation": "REFERENCE", "purpose": "Proposed binding, not an approved registry relation. Optional infrastructure network membership or carried-service reference; no local topology or route computation.", "required": false, "source_refs": [ "SRC-002", "SRC-007" ] }, { "target": "WM-BLT-009", "relation": "REFERENCE", "purpose": "Proposed binding, not an approved registry relation. Optional linear asset and alignment reference with version and station convention; no local recalibration of chainage.", "required": false, "source_refs": [ "SRC-002", "SRC-007" ] }, { "target": "WM-BLT-010", "relation": "REFERENCE", "purpose": "Proposed binding, not an approved registry relation. Optional utility topology interface reference; network connectivity and operation are external.", "required": false, "source_refs": [ "SRC-007" ] }, { "target": "Adopting Dimension land and authority masters", "relation": "REFERENCE", "purpose": "Proposed binding, not an approved registry relation. Profile must pin actual land, party, title, access, retention and audit bindings before operation; conceptual external target, not an invented registry ID.", "required": false, "source_refs": [ "SRC-004", "SRC-006", "SRC-007" ] }, { "target": "IFC 4.3.2.0", "relation": "ALIGN", "purpose": "Map supported asset and element concepts through a pinned profile; no universal one-to-one mapping or certified exchange.", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "target": "InfraGML 1.0 Part 2", "relation": "ALIGN", "purpose": "Map facility versus project concepts and explicitly declare core dependencies and unsupported domains.", "required": false, "source_refs": [ "SRC-002", "SRC-007" ] }, { "target": "SOSA/SSN 2017 and PROV-O 2013", "relation": "ALIGN", "purpose": "Align observation qualification and provenance, without inheriting operational safety, ownership or access powers.", "required": false, "source_refs": [ "SRC-005", "SRC-006" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Name the adopting public asset custodian, private asset owner or delegated record steward by role; no named company is the model owner.", "Pin the instance namespace, master identifier policy, authorized record roles and separation from title or maintenance authority.", "Supply jurisdiction, asset-class profile, evidence policy, units and coordinate conventions, retention schedule and disclosure policy.", "Supply resolvable specification, storage, interface and process bindings; this draft does not supply live endpoints." ], "namespace_guidance": "Use an adopting Dimension namespace with stable asset and artifact identifiers; revision and representation identities are separate. A name, coordinate, address or date alone cannot identify a work.", "registry_links": [ "vr.wm-blt-005", "Candidate neighbor references require profile-level identity and version bindings before use." ] }, "canon_and_patch": { "canonicalization_rules": [ "Maintain a selected asset revision with evidence status, scope and effective time; draft selection is not canonical research promotion.", "Never merge two assets solely because names or geometries match. Preserve external master identity and unresolved correspondence." ], "patch_rules": [ "Require expected revision, authorized editor, reason and evidence for each patch; append revision lineage and refuse stale updates.", "Correct an assessment by supersession or retraction, not silent overwriting; preserve contrary evidence subject to lawful retention." ], "compatibility_rules": [ "Boundary, identity, units, datum, property meaning or state-machine changes require a reviewed migration profile.", "Keep unknown distinct from false, zero, not applicable, uninspected and inaccessible. A schema version alone does not establish semantic compatibility." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier with issuer and scope", "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. Separate event or phenomenon time, result time and ingestion time; retain date precision or unknown status rather than inventing midnight instants.", "serial_naming_rule": "Stable asset or artifact key plus explicit revision identifier; descriptive filenames are labels, dates alone never establish uniqueness.", "integrity_rule": "Record digest, source revision, issuer, lineage and acquisition metadata. A matching digest proves byte consistency only; qualification, authority and truth require separate evidence." }, "policies": [ "This is a noncanonical reviewable draft under the single-provider waiver; independent external review, source/version checking and executable profiles remain holds.", "Detailed design, hazardous-material treatment, protected infrastructure layouts and physical interventions remain under competent external authorities; record policy and evidence references only.", "Do not infer safe operation, regulatory compliance, approval, ownership or public access from record completeness or an exchange file.", "Use purpose-limited access and redaction for protected locations and personal information. Public availability of a map does not authorize publication of detailed asset records." ], "crud": { "read": [ "Resolve identity, revision, authorization, freshness and scope; present disputed or incomplete observations explicitly." ], "create": [ "Create a provisional draft only after identity and duplicate checks; require a scope and accountable steward; unsupported values remain unknown." ], "update": [ "Use authorized revision patches with evidence; retain a correction trace and reject silent geometry, datum or identity changes." ], "delete": [ "Retire an asset record through a continuity reference when removal is evidenced; retirement does not demolish the asset.", "Adopting Dimension retention and legal-hold policy controls deletion of local payloads through its records service. Preserve only lawful minimal tombstones and references; do not impose perpetual retention of personal or restricted payloads.", "Referenced source records, permits, title and audit records have their own masters and disposition rules; local deletion cannot delete them." ] }, "roles": [ { "name": "Asset record steward", "responsibilities": [ "Maintains identity and scope; resolves correspondence and authorizes supported record revisions." ] }, { "name": "Qualified assessor", "responsibilities": [ "Supplies scope-limited observations and assessments with method, uncertainty and time; competence is verified externally." ] }, { "name": "Maintenance custodian", "responsibilities": [ "Provides responsibility and maintenance evidence; cannot turn task completion into safety certification." ] }, { "name": "Evidence reviewer", "responsibilities": [ "Checks attribution, applicability, contradictions and revision lineage without silently discarding contrary evidence." ] }, { "name": "Access and records custodian", "responsibilities": [ "Applies recipient-specific disclosure, retention, legal holds and lawful disposal." ] } ], "access": { "default_rule": "Deny access until the adopting Dimension policy grants a purpose-specific view; enforce restrictions at bundle, layer, finding and artifact, including linked payloads.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "A public generalized view requires an explicit release policy and license; suppress protected detail and personal information.", "An emergency grant must cite authority, scope, purpose and expiry and receive subsequent review; urgency alone is not a grant." ], "audit_requirements": [ "Reference an external audit service for actor, purpose, object revision, grant, outcome and time of reads, exports and mutations.", "Keep redaction and mapping-loss manifests with every derived view; do not expose restricted source locations in metadata." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read AGENTS.md, research holds and spec.yaml.", "Read adopting Dimension authority, profile and retention policy, then resolve asset masters and evidence.", "Traverse Bundle, Layer, Finding, Question and Artifact; collect missing facts before proposing local changes." ] } }, "coverage": { "claim": "Source-grounded proposed structure for one persistent civil infrastructure asset, explicitly reconciled with the broader legacy U1 card. A separate frozen local no-tools self-audit found no critical conflict. This is a noncanonical reviewable draft; independent review, source/version verification, adoption profiles and executable conformance remain holds.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Stable master identity and alias resolution; geometry is recognition evidence." }, { "dimension": "lifecycle", "status": "covered", "notes": "Proposed, existing, accepted, in-service and retired assertions stay distinct." }, { "dimension": "relationships", "status": "covered", "notes": "Parts and external references have explicit ownership boundaries and candidate status." }, { "dimension": "temporal", "status": "covered", "notes": "Effective, observed, result and ingestion times remain distinct with uncertain dates retained." }, { "dimension": "provenance", "status": "covered", "notes": "Evidence attribution and revision chains do not certify truth." }, { "dimension": "ownership", "status": "covered", "notes": "Owner, operator, maintenance duty and data steward are distinct externally evidenced roles." }, { "dimension": "validation", "status": "gap", "notes": "Research structure passes the repository gate; nested instance schemas and engineering acceptance fixtures remain unimplemented." }, { "dimension": "access", "status": "covered", "notes": "Recipient-specific scope, generalization, redaction and audit policies proposed." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Retirement and governed payload disposition separated from removal of the physical asset." }, { "dimension": "interoperability", "status": "gap", "notes": "Conceptual IFC, InfraGML, SOSA and PROV alignments only; wet infrastructure and round-trip mappings unproven." }, { "dimension": "physical properties", "status": "covered", "notes": "Component properties carry units, conditions, method, uncertainty and source." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Survey and inspection coverage prevent inference from appearance to identity or safety." }, { "dimension": "capabilities and actions", "status": "covered", "notes": "Service constraints are evidence references; local functions do not authorize or actuate physical changes." }, { "dimension": "regional and asset-class coverage", "status": "gap", "notes": "No universal design code, inspection interval or legal duty. US stormwater guidance is an example, not a global rule." } ], "known_omissions": [ "No independent second-provider review; the required separate local self-audit cannot restore independent review.", "Direct HTTP checks are not attempted under the owner-reported sandbox block; source versions, availability and licensing require coordinator verification.", "Nested object schemas, quantity types, controlled vocabularies, coordinate transformations and executable conformance fixtures remain to be developed.", "Detailed bridge, tunnel, dam, road, railway, coastal and geotechnical profiles, climate exposure and environmental assessment methods are outside this cross-asset draft.", "Wet infrastructure has no claimed complete LandInfra 1.0 mapping; an adopting profile must supply suitable verified semantics.", "Neighbor bindings and real instance migration from legacy U1 remain untested. Historic evidence gaps and contested identity need profile review." ], "conflicts": [], "regional_assumptions": [ "English descriptions; source terminology does not determine local legal meaning.", "The US green-infrastructure guidance informs maintenance questions only; local statutory responsibilities, permits and engineering criteria require qualified review.", "No globally mandatory inspection frequency, capacity threshold, energy certificate or single owner is assumed." ], "adversarial_checks": [ "Challenge whether Civil Works is a project rather than a persistent asset: projects are external and proposed assets carry explicit existence status.", "Challenge a bridge represented in two cards: preserve one master identity or a scoped part reference; never count two physical assets from two views.", "Challenge a dated favorable inspection on one part: preserve extent, time, method and unknown uninspected areas.", "Challenge title inferred from IFC metadata: reject it; evidence attribution does not grant ownership or operational authority.", "Challenge routine maintenance as automatic safety approval: preserve a separate qualified decision reference.", "Challenge permanent history versus lawful deletion: retain lineage only under the applicable retention and legal-hold policy." ] }, "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 root retains identity across physical interventions and record revisions. Project execution, network topology and operating facility management are external. The registry standalone-mm value describes the record plane, while entity describes the chosen subject boundary. The legacy U1 umbrella is narrowed explicitly rather than silently copied." }, "decisions": [ { "concept": "Asset versus construction activity", "disposition": "accepted as persistent entity", "rationale": "The admitted root is an identifiable civil asset; projects only appear through references and evidenced effects. Proposed, physical, completed, accepted and operational states are not conflated." }, { "concept": "Legacy umbrella and duplicate structural identity", "disposition": "qualified and narrowed", "rationale": "The result does not copy building massing or energy requirements universally. A shared bridge or structural view must use a same-master correspondence or an explicitly scoped component identity, preventing silent duplication." }, { "concept": "Neighbor bindings and relation ledger", "disposition": "accepted as candidates only", "rationale": "No frozen relation-ledger rows exist for this model. The result labels new references as proposed and keeps structural, project, site, facility, network and alignment operations at their external masters." }, { "concept": "Identity and responsible parties", "disposition": "accepted", "rationale": "The identity crosswalk rejects geometry or address as sufficient identity, while responsibility questions distinguish title, operation, maintenance duty and record authority. Attribution cannot grant legal powers." }, { "concept": "Extent, survey and contextual restrictions", "disposition": "accepted with profile dependency", "rationale": "Spatial findings preserve datum, units, uncertainty and observation purpose. External land and environmental restrictions are references with applicability questions, not inferred legal conclusions." }, { "concept": "Engineered ground and measured properties", "disposition": "accepted", "rationale": "The fabric questions distinguish engineered interventions from natural context and preserve shared component masters. Measured, specified and inferred values remain qualified instead of certifying structural capacity." }, { "concept": "Service capability and condition evidence", "disposition": "separated", "rationale": "An intended service, an observed condition and an authorized service state are separate assertions. Uninspected extent, stale reports and contrary assessments cannot inherit a favorable conclusion." }, { "concept": "Acceptance and intervention history", "disposition": "accepted with qualified evidence", "rationale": "Partial acceptance, historic uncertainty and explicit identity-continuity decisions are supported by the questions. Neither an upload nor maintenance completion establishes permission to operate the asset." }, { "concept": "Local functions and operational authority", "disposition": "accepted as proposed and unimplemented", "rationale": "All six operations require record authority and input revision checks with refusal paths. They prepare local assertions and views without executing works or legal acts; external audit recording requires a future governed binding." }, { "concept": "Lineage, access and retention", "disposition": "accepted", "rationale": "Source attribution and content integrity are separate from truth and permission. Governed views and legal-hold checks reconcile revision history with lawful disposal; local deletion cannot erase externally mastered evidence or title." }, { "concept": "Source support and regional scope", "disposition": "limited", "rationale": "Official asset, project, ground-element, maintenance, observation and provenance concepts inform the proposed hierarchy. US stormwater guidance is not universal law, direct HTTP was unattempted and wet-infrastructure mapping remains incomplete." }, { "concept": "Instance schemas and exchange conformance", "disposition": "deferred", "rationale": "Candidate object groups and conceptual alignments do not supply nested instance validation, mandatory fields, coordinate transformations, complete domain mappings or passing round-trip fixtures. No executable or certified implementation is claimed." }, { "concept": "Independent review", "disposition": "waived and held", "rationale": "Claude and Grok were skipped with zero attempts under the owner override. This distinct local no-tools self-audit admits no new facts and is not independent external review or provider agreement." } ], "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 independent review.", "Live source and version verification remains incomplete. Direct HTTP was not attempted under the owner-reported sandbox block; zero responses were measured and no source HTTP status is known. Browser evidence is recorded separately. The coordinator must run check_sources.py outside the sandbox and verify editions, living pages, claim support and licenses.", "Jurisdiction and asset-class adoption profiles require qualified review of design and inspection rules, service limits, environmental and land constraints, authority, protected data and retention. No engineering, safety or legal certification is claimed.", "Nested instance schemas, mandatory-field rules, identity migration fixtures, pinned neighbor bindings, coordinate and unit mappings, wet-infrastructure coverage and executable IFC/InfraGML/SOSA/PROV conformance remain incomplete.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Restore independent external review before canonical or publishable-draft promotion.", "Verify source editions, availability, licensing and profile-specific claim support; HTTP success alone is insufficient.", "Develop asset-class and jurisdiction profiles with competent reviewers, including historical assets, partial acceptance, engineered ground, shared structural identity and disputed responsibility.", "Implement nested schemas and adversarial instance fixtures for coordinate changes, stale inspections, missing units, replacement, mapping loss, restricted views and lawful payload disposal." ] }, "statistics": { "sources": 7, "bundles": 6, "layers": 12, "findings": 12, "questions": 36, "artifacts": 12, "functions": 6 } }