# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-05T23:03:23Z", "synthesisSha256": "9bc2d3db8704461af686e029a635b77948e7d25ab605878bce8e7ea60f13c483", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-BLT-001", "registryId": "vr.wm-blt-001", "name": "Building / Structure", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.BLT.BLD" ], "tags": [ "building", "structure", "phy.blt.bld" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-blt-001-building-structure/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-blt-001", "model": { "registry_id": "vr.wm-blt-001", "model_id": "WM-BLT-001", "name": "Building / Structure", "entry_kind": "aggregate", "purpose": "Represent a persistent building or engineered structure as a governed physical artifact with identity, geometry, composition, fabric, materials, systems, capabilities, condition, performance and lifecycle evidence independent of any storage or exchange format.", "scope_statement": "Owns built-artifact identity, class, geometry bindings, spatial and fabric decomposition, material and installed-system bindings, measured physical properties, recognition features, affordances, hazards, condition and performance assessments, lifecycle changes and exchange projections while referencing facility, site, space, equipment, works, party, permit, incident and document masters.", "in_scope": [ "Building and engineered-structure identity, classification, recognition, geometry, pose and spatial decomposition", "Structural system, envelope, materials, physical properties, installed-system bindings, capabilities, affordances and hazards", "Condition, performance, design and as-built provenance, alteration, end of life, access, retention and interoperability" ], "out_of_scope": [ "Facility operations, land and site tenure, postal address authority, room occupancy and tenancy, individual equipment and product master lifecycles", "Construction-project and work-order execution, party identity, permits, incidents, finance, valuation, insurance and document payloads", "Universal building-code, safety, load, energy, condition or structure-subtype vocabularies" ], "boundary_notes": [ { "neighbor": "Facility WM-BLT-006", "distinction": "Building or structure owns physical fabric; Facility owns the managed operational aggregation. A facility may contain buildings even though IFC uses a different type hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "neighbor": "Site, land parcel and address", "distinction": "The artifact references location, cadastral and address authorities but does not own land tenure, site management or address normalization.", "source_refs": [ "SRC-002", "SRC-005" ] }, { "neighbor": "Premises, space and spatial unit WM-BLT-002", "distinction": "This model owns the outer artifact and decomposition bindings; independently usable or governed interior units retain their own identity and lifecycle.", "source_refs": [ "SRC-003", "SRC-005" ] }, { "neighbor": "Equipment and installed product", "distinction": "The structure owns serving-system, interface and scope bindings while equipment serial identity, maintenance, warranty and spare-parts lifecycle stay external.", "source_refs": [ "SRC-001", "SRC-003" ] }, { "neighbor": "Construction works and project", "distinction": "Works create or alter the artifact, but schedules, contracts, resources, cost and execution remain in project and work models; accepted outputs update the physical record.", "source_refs": [ "SRC-001", "SRC-006" ] }, { "neighbor": "Incident, defect and repair", "distinction": "An incident occurs externally, a defect or damage observation is recorded here, an engineering assessment interprets it, and repair execution remains a referenced work record.", "source_refs": [ "SRC-008", "SRC-009" ] } ] }, "sources": [ { "id": "SRC-001", "title": "IFC 4.3.2 Documentation", "organization": "buildingSMART International", "url": "https://ifc43-docs.standards.buildingsmart.org/", "version_or_date": "IFC 4.3.2.0 current documentation accessed 2026-09-06", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:00:00Z", "relevance": "Defines an open built-asset information schema, lifecycle scope, identity, property, quantity, geometry and exchange concepts." }, { "id": "SRC-002", "title": "IfcBuilding semantic definition", "organization": "buildingSMART International", "url": "https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/IfcBuilding.htm", "version_or_date": "IFC 4.3.2.0", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:00:00Z", "relevance": "Defines a building as a sheltering construction and specifies composition, spatial hierarchy, systems and base quantities." }, { "id": "SRC-003", "title": "IFC spatial structure", "organization": "buildingSMART International", "url": "https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/concepts/Object_Connectivity/Spatial_Structure/content.html", "version_or_date": "IFC 4.3.2.0", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:00:00Z", "relevance": "Provides hierarchical decomposition and containment rules for site, building, storey, space and physical elements." }, { "id": "SRC-004", "title": "IFC material resource", "organization": "buildingSMART International", "url": "https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/ifcmaterialresource/content.html", "version_or_date": "IFC 4.3.2.0", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:00:00Z", "relevance": "Defines material designation, properties, layers, profiles, constituents and associations to elements." }, { "id": "SRC-005", "title": "OGC CityGML Part 1: Conceptual Model Standard", "organization": "Open Geospatial Consortium", "url": "https://docs.ogc.org/is/20-010/20-010.html", "version_or_date": "OGC 20-010, CityGML 3.0.0", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:00:00Z", "relevance": "Defines platform-independent urban objects, building parts, geometry, topology, appearance, levels of detail and change over time." }, { "id": "SRC-006", "title": "ISO 16739-1:2024 Industry Foundation Classes", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/84123.html", "version_or_date": "ISO 16739-1:2024, Edition 2", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:00:00Z", "relevance": "Confirms current IFC scope across buildings, infrastructure works, physical and spatial components, analysis, process, actors and lifecycle exchange." }, { "id": "SRC-007", "title": "Directive (EU) 2024/1275 on the energy performance of buildings", "organization": "European Union", "url": "https://eur-lex.europa.eu/eli/dir/2024/1275/oj", "version_or_date": "Directive (EU) 2024/1275, 24 April 2024", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:00:00Z", "relevance": "Defines building energy-performance, lifecycle global-warming, renovation, technical-system, inspection and certification concepts as a regional profile." }, { "id": "SRC-008", "title": "Selected methods for condition assessment of existing buildings", "organization": "National Institute of Standards and Technology", "url": "https://nvlpubs.nist.gov/nistpubs/Legacy/IR/nbsir80-2171.pdf", "version_or_date": "NBSIR 80-2171", "source_type": "public-authority", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-06T02:00:00Z", "relevance": "Provides an official condition-assessment reference across structural and building-service systems." }, { "id": "SRC-009", "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-09-06T02:00:00Z", "relevance": "Provides portable entity, activity, agent, derivation, attribution and revision semantics for building observations and records." }, { "id": "SRC-010", "title": "RFC 3339: Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339", "version_or_date": "RFC 3339, July 2002", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T02:00:00Z", "relevance": "Defines interoperable timestamps with seconds and explicit offset for lifecycle events and observations." } ], "structure": { "bundles": [ { "id": "identity-classification-and-boundary", "name": "Identity, classification and boundary", "description": "Establishes the persistent physical artifact and its class boundary.", "rationale": "A stable building or structure identity must survive ownership, use, geometry and condition changes without absorbing facility or project identities.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-006" ], "layers": [ { "id": "artifact-identity", "name": "Artifact identity", "description": "Authoritative identity, aliases and continuity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-009" ], "findings": [ { "id": "authoritative-identity-namespace-and-version", "name": "Authoritative identity, namespace and version", "description": "Master-system identifier, namespace, immutable revision and record authority for the physical artifact.", "source_refs": [ "SRC-001", "SRC-002", "SRC-009" ], "questions": [ { "id": "authoritative-identity-namespace-and-version-q01", "text": "What is the current governed value of authoritative identity, namespace and version for this building or structure, and which subtype or scope does it apply to?", "kind": "identity", "answer_data": [ "Authoritative identity, namespace and version", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "authoritative-identity-namespace-and-version-q02", "text": "Which observation, source, method and authority establish authoritative identity, namespace and version, at what time, accuracy and confidence?", "kind": "temporal", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "authoritative-identity-namespace-and-version-q03", "text": "Which validation, access or change rule may revise authoritative identity, namespace and version while preserving the prior physical-state history?", "kind": "validation", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "authoritative-identity-namespace-and-version-data", "name": "Authoritative identity, namespace and version assertion", "description": "Structured built-asset answer data for authoritative identity, namespace and version, including scope, status, time and provenance.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-009" ] } ], "artifacts": [ { "id": "authoritative-identity-namespace-and-version-artifact", "name": "Authoritative identity, namespace and version record", "description": "Versioned building-owned record supporting authoritative identity, namespace and version with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-002", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "aliases-complex-parts-merge-and-split", "name": "Aliases, complex parts, merge and split", "description": "External IDs and identity continuity when a complex is decomposed, connected buildings are grouped or records are corrected.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ], "questions": [ { "id": "aliases-complex-parts-merge-and-split-q01", "text": "What is the current governed value of aliases, complex parts, merge and split for this building or structure, and which subtype or scope does it apply to?", "kind": "relationship", "answer_data": [ "Aliases, complex parts, merge and split", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "aliases-complex-parts-merge-and-split-q02", "text": "Which observation, source, method and authority establish aliases, complex parts, merge and split, at what time, accuracy and confidence?", "kind": "requirement", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "aliases-complex-parts-merge-and-split-q03", "text": "Which validation, access or change rule may revise aliases, complex parts, merge and split while preserving the prior physical-state history?", "kind": "composition", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "aliases-complex-parts-merge-and-split-data", "name": "Aliases, complex parts, merge and split assertion", "description": "Structured built-asset answer data for aliases, complex parts, merge and split, including scope, status, time and provenance.", "value_kind": "collection", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "aliases-complex-parts-merge-and-split-artifact", "name": "Aliases, complex parts, merge and split record", "description": "Versioned building-owned record supporting aliases, complex parts, merge and split with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "classification-and-recognition", "name": "Classification and recognition", "description": "Class, intended function and distinguishing features.", "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ], "findings": [ { "id": "building-structure-class-and-intended-function", "name": "Building or structure class and intended function", "description": "Versioned taxonomy and purpose that distinguish roofed buildings from bridges, towers, dams, tunnels and other engineered works.", "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ], "questions": [ { "id": "building-structure-class-and-intended-function-q01", "text": "What is the current governed value of building or structure class and intended function for this building or structure, and which subtype or scope does it apply to?", "kind": "classification", "answer_data": [ "Building or structure class and intended function", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "building-structure-class-and-intended-function-q02", "text": "Which observation, source, method and authority establish building or structure class and intended function, at what time, accuracy and confidence?", "kind": "evidence", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "building-structure-class-and-intended-function-q03", "text": "Which validation, access or change rule may revise building or structure class and intended function while preserving the prior physical-state history?", "kind": "process", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "building-structure-class-and-intended-function-data", "name": "Building or structure class and intended function assertion", "description": "Structured built-asset answer data for building or structure class and intended function, including scope, status, time and provenance.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ] } ], "artifacts": [ { "id": "building-structure-class-and-intended-function-artifact", "name": "Building or structure class and intended function record", "description": "Versioned building-owned record supporting building or structure class and intended function with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null }, { "id": "recognition-features-neighbor-classes-and-confidence", "name": "Recognition features, neighboring classes and confidence", "description": "Observed visual, geometric, material or functional features and the evidence that distinguishes the artifact from temporary works, equipment, sites and facilities.", "source_refs": [ "SRC-002", "SRC-005" ], "questions": [ { "id": "recognition-features-neighbor-classes-and-confidence-q01", "text": "What is the current governed value of recognition features, neighboring classes and confidence for this building or structure, and which subtype or scope does it apply to?", "kind": "evidence", "answer_data": [ "Recognition features, neighboring classes and confidence", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "recognition-features-neighbor-classes-and-confidence-q02", "text": "Which observation, source, method and authority establish recognition features, neighboring classes and confidence, at what time, accuracy and confidence?", "kind": "retention", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "recognition-features-neighbor-classes-and-confidence-q03", "text": "Which validation, access or change rule may revise recognition features, neighboring classes and confidence while preserving the prior physical-state history?", "kind": "interoperability", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "recognition-features-neighbor-classes-and-confidence-data", "name": "Recognition features, neighboring classes and confidence assertion", "description": "Structured built-asset answer data for recognition features, neighboring classes and confidence, including scope, status, time and provenance.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-005" ] } ], "artifacts": [ { "id": "recognition-features-neighbor-classes-and-confidence-artifact", "name": "Recognition features, neighboring classes and confidence record", "description": "Versioned building-owned record supporting recognition features, neighboring classes and confidence with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-002", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "geometry-location-and-spatial-composition", "name": "Geometry, location and spatial composition", "description": "Represents current and historical shape, pose and hierarchical subdivisions.", "rationale": "Geometry is an observation or representation with coordinate system, accuracy, level of detail and time, not a timeless intrinsic truth.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005" ], "layers": [ { "id": "georeference-and-placement", "name": "Georeference and placement", "description": "Location, coordinate reference and pose.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ], "findings": [ { "id": "site-parcel-address-and-geographic-references", "name": "Site, parcel, address and geographic references", "description": "Typed external location references with jurisdiction and master authority, without importing tenure or address lifecycle.", "source_refs": [ "SRC-002", "SRC-005" ], "questions": [ { "id": "site-parcel-address-and-geographic-references-q01", "text": "What is the current governed value of site, parcel, address and geographic references for this building or structure, and which subtype or scope does it apply to?", "kind": "spatial", "answer_data": [ "Site, parcel, address and geographic references", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "site-parcel-address-and-geographic-references-q02", "text": "Which observation, source, method and authority establish site, parcel, address and geographic references, at what time, accuracy and confidence?", "kind": "definition", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "site-parcel-address-and-geographic-references-q03", "text": "Which validation, access or change rule may revise site, parcel, address and geographic references while preserving the prior physical-state history?", "kind": "provenance", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "site-parcel-address-and-geographic-references-data", "name": "Site, parcel, address and geographic references assertion", "description": "Structured built-asset answer data for site, parcel, address and geographic references, including scope, status, time and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-005" ] } ], "artifacts": [], "inline_only_rationale": "This finding stores only typed references or inline bindings; the external model owns the related payload and independent lifecycle." }, { "id": "coordinate-reference-origin-orientation-and-pose", "name": "Coordinate reference, origin, orientation and pose", "description": "Coordinate reference system, local datum, placement transform, elevation reference, orientation, accuracy and observation time.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ], "questions": [ { "id": "coordinate-reference-origin-orientation-and-pose-q01", "text": "What is the current governed value of coordinate reference, origin, orientation and pose for this building or structure, and which subtype or scope does it apply to?", "kind": "spatial", "answer_data": [ "Coordinate reference, origin, orientation and pose", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "coordinate-reference-origin-orientation-and-pose-q02", "text": "Which observation, source, method and authority establish coordinate reference, origin, orientation and pose, at what time, accuracy and confidence?", "kind": "state", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "coordinate-reference-origin-orientation-and-pose-q03", "text": "Which validation, access or change rule may revise coordinate reference, origin, orientation and pose while preserving the prior physical-state history?", "kind": "security", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "coordinate-reference-origin-orientation-and-pose-data", "name": "Coordinate reference, origin, orientation and pose assertion", "description": "Structured built-asset answer data for coordinate reference, origin, orientation and pose, including scope, status, time and provenance.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] } ], "artifacts": [ { "id": "coordinate-reference-origin-orientation-and-pose-artifact", "name": "Coordinate reference, origin, orientation and pose record", "description": "Versioned building-owned record supporting coordinate reference, origin, orientation and pose with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "shape-extent-and-representation", "name": "Shape, extent and representation", "description": "Footprint, volume, dimensions and alternate geometries.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ], "findings": [ { "id": "footprint-height-area-volume-and-extents", "name": "Footprint, height, area, volume and extents", "description": "Measured or derived quantities with unit, boundary convention, tolerance, method and validity time.", "source_refs": [ "SRC-002", "SRC-005" ], "questions": [ { "id": "footprint-height-area-volume-and-extents-q01", "text": "What is the current governed value of footprint, height, area, volume and extents for this building or structure, and which subtype or scope does it apply to?", "kind": "measurement", "answer_data": [ "Footprint, height, area, volume and extents", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "footprint-height-area-volume-and-extents-q02", "text": "Which observation, source, method and authority establish footprint, height, area, volume and extents, at what time, accuracy and confidence?", "kind": "ownership", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "footprint-height-area-volume-and-extents-q03", "text": "Which validation, access or change rule may revise footprint, height, area, volume and extents while preserving the prior physical-state history?", "kind": "relationship", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "footprint-height-area-volume-and-extents-data", "name": "Footprint, height, area, volume and extents assertion", "description": "Structured built-asset answer data for footprint, height, area, volume and extents, including scope, status, time and provenance.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-005" ] } ], "artifacts": [ { "id": "footprint-height-area-volume-and-extents-artifact", "name": "Footprint, height, area, volume and extents record", "description": "Versioned building-owned record supporting footprint, height, area, volume and extents with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-002", "SRC-005" ] } ], "inline_only_rationale": null }, { "id": "designed-as-built-surveyed-current-and-lod", "name": "Designed, as-built, surveyed, current and level of detail", "description": "Distinct representations with purpose, level of detail, accuracy, source, capture time and transformation lineage.", "source_refs": [ "SRC-001", "SRC-005", "SRC-009" ], "questions": [ { "id": "designed-as-built-surveyed-current-and-lod-q01", "text": "What is the current governed value of designed, as-built, surveyed, current and level of detail for this building or structure, and which subtype or scope does it apply to?", "kind": "provenance", "answer_data": [ "Designed, as-built, surveyed, current and level of detail", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "designed-as-built-surveyed-current-and-lod-q02", "text": "Which observation, source, method and authority establish designed, as-built, surveyed, current and level of detail, at what time, accuracy and confidence?", "kind": "event", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "designed-as-built-surveyed-current-and-lod-q03", "text": "Which validation, access or change rule may revise designed, as-built, surveyed, current and level of detail while preserving the prior physical-state history?", "kind": "measurement", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "designed-as-built-surveyed-current-and-lod-data", "name": "Designed, as-built, surveyed, current and level of detail assertion", "description": "Structured built-asset answer data for designed, as-built, surveyed, current and level of detail, including scope, status, time and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-009" ] } ], "artifacts": [ { "id": "designed-as-built-surveyed-current-and-lod-artifact", "name": "Designed, as-built, surveyed, current and level of detail record", "description": "Versioned building-owned record supporting designed, as-built, surveyed, current and level of detail with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-005", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "spatial-decomposition", "name": "Spatial decomposition", "description": "Complex, building parts, storeys, spaces or segments and zones.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ], "findings": [ { "id": "complex-building-part-storey-and-segment", "name": "Complex, building part, storey and segment", "description": "Hierarchical decomposition with role, composition type, parent, order and effective interval.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ], "questions": [ { "id": "complex-building-part-storey-and-segment-q01", "text": "What is the current governed value of complex, building part, storey and segment for this building or structure, and which subtype or scope does it apply to?", "kind": "composition", "answer_data": [ "Complex, building part, storey and segment", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "complex-building-part-storey-and-segment-q02", "text": "Which observation, source, method and authority establish complex, building part, storey and segment, at what time, accuracy and confidence?", "kind": "security", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "complex-building-part-storey-and-segment-q03", "text": "Which validation, access or change rule may revise complex, building part, storey and segment while preserving the prior physical-state history?", "kind": "decision", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "complex-building-part-storey-and-segment-data", "name": "Complex, building part, storey and segment assertion", "description": "Structured built-asset answer data for complex, building part, storey and segment, including scope, status, time and provenance.", "value_kind": "collection", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "complex-building-part-storey-and-segment-artifact", "name": "Complex, building part, storey and segment record", "description": "Versioned building-owned record supporting complex, building part, storey and segment with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null }, { "id": "premises-space-zone-and-containment-boundary", "name": "Premises, space, zone and containment boundary", "description": "References to interior units and functional zones plus the boundary or rule by which elements are contained.", "source_refs": [ "SRC-003", "SRC-005" ], "questions": [ { "id": "premises-space-zone-and-containment-boundary-q01", "text": "What is the current governed value of premises, space, zone and containment boundary for this building or structure, and which subtype or scope does it apply to?", "kind": "composition", "answer_data": [ "Premises, space, zone and containment boundary", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "premises-space-zone-and-containment-boundary-q02", "text": "Which observation, source, method and authority establish premises, space, zone and containment boundary, at what time, accuracy and confidence?", "kind": "interoperability", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "premises-space-zone-and-containment-boundary-q03", "text": "Which validation, access or change rule may revise premises, space, zone and containment boundary while preserving the prior physical-state history?", "kind": "ownership", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "premises-space-zone-and-containment-boundary-data", "name": "Premises, space, zone and containment boundary assertion", "description": "Structured built-asset answer data for premises, space, zone and containment boundary, including scope, status, time and provenance.", "value_kind": "collection", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-005" ] } ], "artifacts": [], "inline_only_rationale": "This finding stores only typed references or inline bindings; the external model owns the related payload and independent lifecycle." } ] } ] }, { "id": "fabric-structure-envelope-and-materials", "name": "Fabric, structure, envelope and materials", "description": "Describes what the physical artifact is made of and how loads and separation are achieved.", "rationale": "Elements, systems and materials need typed decomposition and observed properties while their product catalog or equipment lifecycle stays external.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-006" ], "layers": [ { "id": "structural-system-and-load-path", "name": "Structural system and load path", "description": "Foundation, frame, stability and supported actions.", "source_refs": [ "SRC-001", "SRC-006", "SRC-008" ], "findings": [ { "id": "foundation-frame-bearing-system-and-connections", "name": "Foundation, frame, bearing system and connections", "description": "System topology and member-role references for foundations, frames, walls, slabs, shells, cables and connections.", "source_refs": [ "SRC-001", "SRC-008" ], "questions": [ { "id": "foundation-frame-bearing-system-and-connections-q01", "text": "What is the current governed value of foundation, frame, bearing system and connections for this building or structure, and which subtype or scope does it apply to?", "kind": "composition", "answer_data": [ "Foundation, frame, bearing system and connections", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "foundation-frame-bearing-system-and-connections-q02", "text": "Which observation, source, method and authority establish foundation, frame, bearing system and connections, at what time, accuracy and confidence?", "kind": "relationship", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "foundation-frame-bearing-system-and-connections-q03", "text": "Which validation, access or change rule may revise foundation, frame, bearing system and connections while preserving the prior physical-state history?", "kind": "privacy", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "foundation-frame-bearing-system-and-connections-data", "name": "Foundation, frame, bearing system and connections assertion", "description": "Structured built-asset answer data for foundation, frame, bearing system and connections, including scope, status, time and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-008" ] } ], "artifacts": [ { "id": "foundation-frame-bearing-system-and-connections-artifact", "name": "Foundation, frame, bearing system and connections record", "description": "Versioned building-owned record supporting foundation, frame, bearing system and connections with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "load-path-actions-capacity-and-design-basis", "name": "Load path, actions, capacity and design basis", "description": "Declared design actions, combinations, load transfer, resistance, serviceability and code or engineering basis without asserting current safety.", "source_refs": [ "SRC-001", "SRC-006", "SRC-008" ], "questions": [ { "id": "load-path-actions-capacity-and-design-basis-q01", "text": "What is the current governed value of load path, actions, capacity and design basis for this building or structure, and which subtype or scope does it apply to?", "kind": "constraint", "answer_data": [ "Load path, actions, capacity and design basis", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "load-path-actions-capacity-and-design-basis-q02", "text": "Which observation, source, method and authority establish load path, actions, capacity and design basis, at what time, accuracy and confidence?", "kind": "spatial", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "load-path-actions-capacity-and-design-basis-q03", "text": "Which validation, access or change rule may revise load path, actions, capacity and design basis while preserving the prior physical-state history?", "kind": "state", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "load-path-actions-capacity-and-design-basis-data", "name": "Load path, actions, capacity and design basis assertion", "description": "Structured built-asset answer data for load path, actions, capacity and design basis, including scope, status, time and provenance.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-006", "SRC-008" ] } ], "artifacts": [ { "id": "load-path-actions-capacity-and-design-basis-artifact", "name": "Load path, actions, capacity and design basis record", "description": "Versioned building-owned record supporting load path, actions, capacity and design basis with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-006", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "envelope-and-openings", "name": "Envelope and openings", "description": "Exterior separation, thermal boundary and controlled openings.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ], "findings": [ { "id": "roof-facade-ground-boundary-and-continuity", "name": "Roof, facade, ground boundary and continuity", "description": "Envelope surfaces, layers, junctions, continuity and exterior or interior side semantics.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ], "questions": [ { "id": "roof-facade-ground-boundary-and-continuity-q01", "text": "What is the current governed value of roof, facade, ground boundary and continuity for this building or structure, and which subtype or scope does it apply to?", "kind": "composition", "answer_data": [ "Roof, facade, ground boundary and continuity", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "roof-facade-ground-boundary-and-continuity-q02", "text": "Which observation, source, method and authority establish roof, facade, ground boundary and continuity, at what time, accuracy and confidence?", "kind": "constraint", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "roof-facade-ground-boundary-and-continuity-q03", "text": "Which validation, access or change rule may revise roof, facade, ground boundary and continuity while preserving the prior physical-state history?", "kind": "measurement", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "roof-facade-ground-boundary-and-continuity-data", "name": "Roof, facade, ground boundary and continuity assertion", "description": "Structured built-asset answer data for roof, facade, ground boundary and continuity, including scope, status, time and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "roof-facade-ground-boundary-and-continuity-artifact", "name": "Roof, facade, ground boundary and continuity record", "description": "Versioned building-owned record supporting roof, facade, ground boundary and continuity with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "door-window-opening-penetration-and-interface", "name": "Door, window, opening, penetration and interface", "description": "Typed openings and interfaces with dimensions, operation, adjacency, sealing and external component references.", "source_refs": [ "SRC-001", "SRC-005" ], "questions": [ { "id": "door-window-opening-penetration-and-interface-q01", "text": "What is the current governed value of door, window, opening, penetration and interface for this building or structure, and which subtype or scope does it apply to?", "kind": "relationship", "answer_data": [ "Door, window, opening, penetration and interface", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "door-window-opening-penetration-and-interface-q02", "text": "Which observation, source, method and authority establish door, window, opening, penetration and interface, at what time, accuracy and confidence?", "kind": "quality", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "door-window-opening-penetration-and-interface-q03", "text": "Which validation, access or change rule may revise door, window, opening, penetration and interface while preserving the prior physical-state history?", "kind": "definition", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "door-window-opening-penetration-and-interface-data", "name": "Door, window, opening, penetration and interface assertion", "description": "Structured built-asset answer data for door, window, opening, penetration and interface, including scope, status, time and provenance.", "value_kind": "collection", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] } ], "artifacts": [], "inline_only_rationale": "This finding stores only typed references or inline bindings; the external model owns the related payload and independent lifecycle." } ] }, { "id": "materials-and-physical-properties", "name": "Materials and physical properties", "description": "Substances, assemblies and measured intrinsic properties.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ], "findings": [ { "id": "material-layer-profile-constituent-and-source", "name": "Material layer, profile, constituent and source", "description": "Material identity or classification, assembly order, thickness, proportion, manufacturer or source reference and confidence.", "source_refs": [ "SRC-004" ], "questions": [ { "id": "material-layer-profile-constituent-and-source-q01", "text": "What is the current governed value of material layer, profile, constituent and source for this building or structure, and which subtype or scope does it apply to?", "kind": "composition", "answer_data": [ "Material layer, profile, constituent and source", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "material-layer-profile-constituent-and-source-q02", "text": "Which observation, source, method and authority establish material layer, profile, constituent and source, at what time, accuracy and confidence?", "kind": "access", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "material-layer-profile-constituent-and-source-q03", "text": "Which validation, access or change rule may revise material layer, profile, constituent and source while preserving the prior physical-state history?", "kind": "authority", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "material-layer-profile-constituent-and-source-data", "name": "Material layer, profile, constituent and source assertion", "description": "Structured built-asset answer data for material layer, profile, constituent and source, including scope, status, time and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-004" ] } ], "artifacts": [ { "id": "material-layer-profile-constituent-and-source-artifact", "name": "Material layer, profile, constituent and source record", "description": "Versioned building-owned record supporting material layer, profile, constituent and source with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-004" ] } ], "inline_only_rationale": null }, { "id": "density-mass-hardness-strength-fragility-and-surface", "name": "Density, mass, hardness, strength, fragility and surface", "description": "Relevant measured properties with units, tolerance, anisotropy, moisture, temperature, method, sample and validity conditions.", "source_refs": [ "SRC-004", "SRC-008" ], "questions": [ { "id": "density-mass-hardness-strength-fragility-and-surface-q01", "text": "What is the current governed value of density, mass, hardness, strength, fragility and surface for this building or structure, and which subtype or scope does it apply to?", "kind": "measurement", "answer_data": [ "Density, mass, hardness, strength, fragility and surface", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "density-mass-hardness-strength-fragility-and-surface-q02", "text": "Which observation, source, method and authority establish density, mass, hardness, strength, fragility and surface, at what time, accuracy and confidence?", "kind": "identity", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "density-mass-hardness-strength-fragility-and-surface-q03", "text": "Which validation, access or change rule may revise density, mass, hardness, strength, fragility and surface while preserving the prior physical-state history?", "kind": "retention", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "density-mass-hardness-strength-fragility-and-surface-data", "name": "Density, mass, hardness, strength, fragility and surface assertion", "description": "Structured built-asset answer data for density, mass, hardness, strength, fragility and surface, including scope, status, time and provenance.", "value_kind": "collection", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "density-mass-hardness-strength-fragility-and-surface-artifact", "name": "Density, mass, hardness, strength, fragility and surface record", "description": "Versioned building-owned record supporting density, mass, hardness, strength, fragility and surface with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "systems-capabilities-affordances-and-safety", "name": "Systems, capabilities, affordances and safety", "description": "Connects installed systems to supported uses, actions, constraints and hazards.", "rationale": "The structure owns system and capability bindings while maintainable component details and operational work remain in equipment and facility systems.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-007" ], "layers": [ { "id": "installed-systems-and-services", "name": "Installed systems and services", "description": "Technical, distribution, transport, fire and control systems.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "findings": [ { "id": "system-identity-function-scope-and-topology", "name": "System identity, function, scope and topology", "description": "References to systems and components with served areas, ports, networks, function and operational boundary.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "system-identity-function-scope-and-topology-q01", "text": "What is the current governed value of system identity, function, scope and topology for this building or structure, and which subtype or scope does it apply to?", "kind": "relationship", "answer_data": [ "System identity, function, scope and topology", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "system-identity-function-scope-and-topology-q02", "text": "Which observation, source, method and authority establish system identity, function, scope and topology, at what time, accuracy and confidence?", "kind": "lifecycle", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "system-identity-function-scope-and-topology-q03", "text": "Which validation, access or change rule may revise system identity, function, scope and topology while preserving the prior physical-state history?", "kind": "temporal", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "system-identity-function-scope-and-topology-data", "name": "System identity, function, scope and topology assertion", "description": "Structured built-asset answer data for system identity, function, scope and topology, including scope, status, time and provenance.", "value_kind": "collection", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [], "inline_only_rationale": "This finding stores only typed references or inline bindings; the external model owns the related payload and independent lifecycle." }, { "id": "capacity-availability-control-and-dependency", "name": "Capacity, availability, control and dependency", "description": "Rated and observed capacity, service state, control authority, utilities, upstream dependencies and failure propagation.", "source_refs": [ "SRC-001", "SRC-007" ], "questions": [ { "id": "capacity-availability-control-and-dependency-q01", "text": "What is the current governed value of capacity, availability, control and dependency for this building or structure, and which subtype or scope does it apply to?", "kind": "state", "answer_data": [ "Capacity, availability, control and dependency", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "capacity-availability-control-and-dependency-q02", "text": "Which observation, source, method and authority establish capacity, availability, control and dependency, at what time, accuracy and confidence?", "kind": "authority", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "capacity-availability-control-and-dependency-q03", "text": "Which validation, access or change rule may revise capacity, availability, control and dependency while preserving the prior physical-state history?", "kind": "evidence", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "capacity-availability-control-and-dependency-data", "name": "Capacity, availability, control and dependency assertion", "description": "Structured built-asset answer data for capacity, availability, control and dependency, including scope, status, time and provenance.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] } ], "artifacts": [ { "id": "capacity-availability-control-and-dependency-artifact", "name": "Capacity, availability, control and dependency record", "description": "Versioned building-owned record supporting capacity, availability, control and dependency with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "use-affordance-and-hazard", "name": "Use, affordance and hazard", "description": "Supported occupancy or function, actions, access and failure modes.", "source_refs": [ "SRC-002", "SRC-005", "SRC-007", "SRC-008" ], "findings": [ { "id": "supported-use-occupancy-load-access-and-egress", "name": "Supported use, occupancy, load, access and egress", "description": "Permitted or designed uses, occupancy and load limits, accessibility, circulation, entry, exit and evacuation affordances.", "source_refs": [ "SRC-002", "SRC-005", "SRC-007" ], "questions": [ { "id": "supported-use-occupancy-load-access-and-egress-q01", "text": "What is the current governed value of supported use, occupancy, load, access and egress for this building or structure, and which subtype or scope does it apply to?", "kind": "process", "answer_data": [ "Supported use, occupancy, load, access and egress", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "supported-use-occupancy-load-access-and-egress-q02", "text": "Which observation, source, method and authority establish supported use, occupancy, load, access and egress, at what time, accuracy and confidence?", "kind": "measurement", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "supported-use-occupancy-load-access-and-egress-q03", "text": "Which validation, access or change rule may revise supported use, occupancy, load, access and egress while preserving the prior physical-state history?", "kind": "identity", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "supported-use-occupancy-load-access-and-egress-data", "name": "Supported use, occupancy, load, access and egress assertion", "description": "Structured built-asset answer data for supported use, occupancy, load, access and egress, including scope, status, time and provenance.", "value_kind": "collection", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "supported-use-occupancy-load-access-and-egress-artifact", "name": "Supported use, occupancy, load, access and egress record", "description": "Versioned building-owned record supporting supported use, occupancy, load, access and egress with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-002", "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "hazard-vulnerability-protection-and-failure-mode", "name": "Hazard, vulnerability, protection and failure mode", "description": "Exposure, vulnerability, protective feature, foreseeable failure, trigger, consequence and safe operating restriction.", "source_refs": [ "SRC-007", "SRC-008" ], "questions": [ { "id": "hazard-vulnerability-protection-and-failure-mode-q01", "text": "What is the current governed value of hazard, vulnerability, protection and failure mode for this building or structure, and which subtype or scope does it apply to?", "kind": "security", "answer_data": [ "Hazard, vulnerability, protection and failure mode", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "hazard-vulnerability-protection-and-failure-mode-q02", "text": "Which observation, source, method and authority establish hazard, vulnerability, protection and failure mode, at what time, accuracy and confidence?", "kind": "privacy", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "hazard-vulnerability-protection-and-failure-mode-q03", "text": "Which validation, access or change rule may revise hazard, vulnerability, protection and failure mode while preserving the prior physical-state history?", "kind": "requirement", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "hazard-vulnerability-protection-and-failure-mode-data", "name": "Hazard, vulnerability, protection and failure mode assertion", "description": "Structured built-asset answer data for hazard, vulnerability, protection and failure mode, including scope, status, time and provenance.", "value_kind": "collection", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "hazard-vulnerability-protection-and-failure-mode-artifact", "name": "Hazard, vulnerability, protection and failure mode record", "description": "Versioned building-owned record supporting hazard, vulnerability, protection and failure mode with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "condition-and-performance", "name": "Condition and performance", "description": "Records dated observations and assessments of current fabric and behavior.", "rationale": "Condition grades and performance certificates are method-bound evidence, not permanent direct properties or universal safety decisions.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008", "SRC-009" ], "layers": [ { "id": "inspection-condition-and-damage", "name": "Inspection, condition and damage", "description": "Observation scope, defects, damage and restrictions.", "source_refs": [ "SRC-008", "SRC-009", "SRC-010" ], "findings": [ { "id": "inspection-method-scope-access-and-limitations", "name": "Inspection method, scope, access and limitations", "description": "Inspector, competence, method, covered and inaccessible parts, instruments, conditions, time, evidence and limitations.", "source_refs": [ "SRC-008", "SRC-009", "SRC-010" ], "questions": [ { "id": "inspection-method-scope-access-and-limitations-q01", "text": "What is the current governed value of inspection method, scope, access and limitations for this building or structure, and which subtype or scope does it apply to?", "kind": "evidence", "answer_data": [ "Inspection method, scope, access and limitations", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "inspection-method-scope-access-and-limitations-q02", "text": "Which observation, source, method and authority establish inspection method, scope, access and limitations, at what time, accuracy and confidence?", "kind": "decision", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "inspection-method-scope-access-and-limitations-q03", "text": "Which validation, access or change rule may revise inspection method, scope, access and limitations while preserving the prior physical-state history?", "kind": "access", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "inspection-method-scope-access-and-limitations-data", "name": "Inspection method, scope, access and limitations assertion", "description": "Structured built-asset answer data for inspection method, scope, access and limitations, including scope, status, time and provenance.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-008", "SRC-009", "SRC-010" ] } ], "artifacts": [ { "id": "inspection-method-scope-access-and-limitations-artifact", "name": "Inspection method, scope, access and limitations record", "description": "Versioned building-owned record supporting inspection method, scope, access and limitations with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-008", "SRC-009", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "defect-damage-condition-grade-and-restriction", "name": "Defect, damage, condition grade and restriction", "description": "Localized observation, cause hypothesis, extent, severity, confidence, assessment scheme and resulting use restriction.", "source_refs": [ "SRC-008", "SRC-009" ], "questions": [ { "id": "defect-damage-condition-grade-and-restriction-q01", "text": "What is the current governed value of defect, damage, condition grade and restriction for this building or structure, and which subtype or scope does it apply to?", "kind": "quality", "answer_data": [ "Defect, damage, condition grade and restriction", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "defect-damage-condition-grade-and-restriction-q02", "text": "Which observation, source, method and authority establish defect, damage, condition grade and restriction, at what time, accuracy and confidence?", "kind": "relationship", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "defect-damage-condition-grade-and-restriction-q03", "text": "Which validation, access or change rule may revise defect, damage, condition grade and restriction while preserving the prior physical-state history?", "kind": "temporal", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "defect-damage-condition-grade-and-restriction-data", "name": "Defect, damage, condition grade and restriction assertion", "description": "Structured built-asset answer data for defect, damage, condition grade and restriction, including scope, status, time and provenance.", "value_kind": "collection", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008", "SRC-009" ] } ], "artifacts": [ { "id": "defect-damage-condition-grade-and-restriction-artifact", "name": "Defect, damage, condition grade and restriction record", "description": "Versioned building-owned record supporting defect, damage, condition grade and restriction with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "functional-environmental-and-energy-performance", "name": "Functional, environmental and energy performance", "description": "Measured or modelled behavior under declared conditions.", "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ], "findings": [ { "id": "structural-serviceability-function-and-reliability", "name": "Structural, serviceability, function and reliability", "description": "Capacity or performance assessment, demand, margin, reliability basis, functional failure and remaining-life estimate.", "source_refs": [ "SRC-001", "SRC-008" ], "questions": [ { "id": "structural-serviceability-function-and-reliability-q01", "text": "What is the current governed value of structural, serviceability, function and reliability for this building or structure, and which subtype or scope does it apply to?", "kind": "validation", "answer_data": [ "Structural, serviceability, function and reliability", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "structural-serviceability-function-and-reliability-q02", "text": "Which observation, source, method and authority establish structural, serviceability, function and reliability, at what time, accuracy and confidence?", "kind": "provenance", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "structural-serviceability-function-and-reliability-q03", "text": "Which validation, access or change rule may revise structural, serviceability, function and reliability while preserving the prior physical-state history?", "kind": "quality", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "structural-serviceability-function-and-reliability-data", "name": "Structural, serviceability, function and reliability assertion", "description": "Structured built-asset answer data for structural, serviceability, function and reliability, including scope, status, time and provenance.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-008" ] } ], "artifacts": [ { "id": "structural-serviceability-function-and-reliability-artifact", "name": "Structural, serviceability, function and reliability record", "description": "Versioned building-owned record supporting structural, serviceability, function and reliability with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "energy-carbon-indoor-environment-and-resource-profile", "name": "Energy, carbon, indoor environment and resource profile", "description": "Metered or calculated energy, emissions, lifecycle warming, indoor environmental quality and resource performance with regional method binding.", "source_refs": [ "SRC-007" ], "questions": [ { "id": "energy-carbon-indoor-environment-and-resource-profile-q01", "text": "What is the current governed value of energy, carbon, indoor environment and resource profile for this building or structure, and which subtype or scope does it apply to?", "kind": "measurement", "answer_data": [ "Energy, carbon, indoor environment and resource profile", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "energy-carbon-indoor-environment-and-resource-profile-q02", "text": "Which observation, source, method and authority establish energy, carbon, indoor environment and resource profile, at what time, accuracy and confidence?", "kind": "process", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "energy-carbon-indoor-environment-and-resource-profile-q03", "text": "Which validation, access or change rule may revise energy, carbon, indoor environment and resource profile while preserving the prior physical-state history?", "kind": "classification", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "energy-carbon-indoor-environment-and-resource-profile-data", "name": "Energy, carbon, indoor environment and resource profile assertion", "description": "Structured built-asset answer data for energy, carbon, indoor environment and resource profile, including scope, status, time and provenance.", "value_kind": "collection", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007" ] } ], "artifacts": [ { "id": "energy-carbon-indoor-environment-and-resource-profile-artifact", "name": "Energy, carbon, indoor environment and resource profile record", "description": "Versioned building-owned record supporting energy, carbon, indoor environment and resource profile with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "lifecycle-change-and-provenance", "name": "Lifecycle, change and provenance", "description": "Preserves origin, acceptance, alteration, use change, decommissioning and demolition.", "rationale": "The physical artifact record persists after demolition, while projects and work orders own delivery execution.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007", "SRC-009", "SRC-010" ], "layers": [ { "id": "origin-design-construction-and-handover", "name": "Origin, design, construction and handover", "description": "Design intent, as-built evidence and acceptance into service.", "source_refs": [ "SRC-001", "SRC-006", "SRC-009" ], "findings": [ { "id": "design-authority-basis-and-approved-representation", "name": "Design authority, basis and approved representation", "description": "Designer or responsible authority, requirement and code basis, approved model or document references and issue status.", "source_refs": [ "SRC-001", "SRC-006", "SRC-009" ], "questions": [ { "id": "design-authority-basis-and-approved-representation-q01", "text": "What is the current governed value of design authority, basis and approved representation for this building or structure, and which subtype or scope does it apply to?", "kind": "authority", "answer_data": [ "Design authority, basis and approved representation", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "design-authority-basis-and-approved-representation-q02", "text": "Which observation, source, method and authority establish design authority, basis and approved representation, at what time, accuracy and confidence?", "kind": "validation", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "design-authority-basis-and-approved-representation-q03", "text": "Which validation, access or change rule may revise design authority, basis and approved representation while preserving the prior physical-state history?", "kind": "constraint", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "design-authority-basis-and-approved-representation-data", "name": "Design authority, basis and approved representation assertion", "description": "Structured built-asset answer data for design authority, basis and approved representation, including scope, status, time and provenance.", "value_kind": "collection", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-006", "SRC-009" ] } ], "artifacts": [], "inline_only_rationale": "This finding stores only typed references or inline bindings; the external model owns the related payload and independent lifecycle." }, { "id": "construction-completion-commissioning-and-acceptance", "name": "Construction completion, commissioning and acceptance", "description": "References to works, completion, tests, commissioning, handover package and acceptance event that establish as-built state.", "source_refs": [ "SRC-001", "SRC-006", "SRC-010" ], "questions": [ { "id": "construction-completion-commissioning-and-acceptance-q01", "text": "What is the current governed value of construction completion, commissioning and acceptance for this building or structure, and which subtype or scope does it apply to?", "kind": "event", "answer_data": [ "Construction completion, commissioning and acceptance", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "construction-completion-commissioning-and-acceptance-q02", "text": "Which observation, source, method and authority establish construction completion, commissioning and acceptance, at what time, accuracy and confidence?", "kind": "exception", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "construction-completion-commissioning-and-acceptance-q03", "text": "Which validation, access or change rule may revise construction completion, commissioning and acceptance while preserving the prior physical-state history?", "kind": "interoperability", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "construction-completion-commissioning-and-acceptance-data", "name": "Construction completion, commissioning and acceptance assertion", "description": "Structured built-asset answer data for construction completion, commissioning and acceptance, including scope, status, time and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-006", "SRC-010" ] } ], "artifacts": [ { "id": "construction-completion-commissioning-and-acceptance-artifact", "name": "Construction completion, commissioning and acceptance record", "description": "Versioned building-owned record supporting construction completion, commissioning and acceptance with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-006", "SRC-010" ] } ], "inline_only_rationale": null } ] }, { "id": "alteration-use-change-and-end-of-life", "name": "Alteration, use change and end of life", "description": "Versioned change to fabric, function or physical existence.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-009" ], "findings": [ { "id": "alteration-renovation-repair-and-change-of-use", "name": "Alteration, renovation, repair and change of use", "description": "Before and after fabric or function states, work and authorization references, effective time and updated performance assumptions.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-009" ], "questions": [ { "id": "alteration-renovation-repair-and-change-of-use-q01", "text": "What is the current governed value of alteration, renovation, repair and change of use for this building or structure, and which subtype or scope does it apply to?", "kind": "lifecycle", "answer_data": [ "Alteration, renovation, repair and change of use", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "alteration-renovation-repair-and-change-of-use-q02", "text": "Which observation, source, method and authority establish alteration, renovation, repair and change of use, at what time, accuracy and confidence?", "kind": "classification", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "alteration-renovation-repair-and-change-of-use-q03", "text": "Which validation, access or change rule may revise alteration, renovation, repair and change of use while preserving the prior physical-state history?", "kind": "spatial", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "alteration-renovation-repair-and-change-of-use-data", "name": "Alteration, renovation, repair and change of use assertion", "description": "Structured built-asset answer data for alteration, renovation, repair and change of use, including scope, status, time and provenance.", "value_kind": "collection", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-009" ] } ], "artifacts": [ { "id": "alteration-renovation-repair-and-change-of-use-artifact", "name": "Alteration, renovation, repair and change of use record", "description": "Versioned building-owned record supporting alteration, renovation, repair and change of use with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-005", "SRC-007", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "decommission-demolition-removal-and-residual-record", "name": "Decommission, demolition, removal and residual record", "description": "Physical cessation, partial retention, material-recovery references, evidence, status and continuing historical or legal references.", "source_refs": [ "SRC-001", "SRC-005", "SRC-009" ], "questions": [ { "id": "decommission-demolition-removal-and-residual-record-q01", "text": "What is the current governed value of decommission, demolition, removal and residual record for this building or structure, and which subtype or scope does it apply to?", "kind": "retention", "answer_data": [ "Decommission, demolition, removal and residual record", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "decommission-demolition-removal-and-residual-record-q02", "text": "Which observation, source, method and authority establish decommission, demolition, removal and residual record, at what time, accuracy and confidence?", "kind": "temporal", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "decommission-demolition-removal-and-residual-record-q03", "text": "Which validation, access or change rule may revise decommission, demolition, removal and residual record while preserving the prior physical-state history?", "kind": "validation", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "decommission-demolition-removal-and-residual-record-data", "name": "Decommission, demolition, removal and residual record assertion", "description": "Structured built-asset answer data for decommission, demolition, removal and residual record, including scope, status, time and provenance.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-009" ] } ], "artifacts": [ { "id": "decommission-demolition-removal-and-residual-record-artifact", "name": "Decommission, demolition, removal and residual record record", "description": "Versioned building-owned record supporting decommission, demolition, removal and residual record with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-005", "SRC-009" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "governance-access-and-interoperability", "name": "Governance, access and interoperability", "description": "Controls authority, disclosure, integrity, retention and exchange.", "rationale": "Built-asset records span many owners and systems, so agents need explicit mastership, projection and crosswalk rules.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009", "SRC-010" ], "layers": [ { "id": "ownership-custody-access-and-retention", "name": "Ownership, custody, access and retention", "description": "External party bindings and minimum authorized views.", "source_refs": [ "SRC-001", "SRC-009" ], "findings": [ { "id": "owner-operator-custodian-and-record-authority", "name": "Owner, operator, custodian and record authority", "description": "Time-bounded external party roles and distinct authority over fabric, operation, data and decisions.", "source_refs": [ "SRC-001", "SRC-009" ], "questions": [ { "id": "owner-operator-custodian-and-record-authority-q01", "text": "What is the current governed value of owner, operator, custodian and record authority for this building or structure, and which subtype or scope does it apply to?", "kind": "ownership", "answer_data": [ "Owner, operator, custodian and record authority", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "owner-operator-custodian-and-record-authority-q02", "text": "Which observation, source, method and authority establish owner, operator, custodian and record authority, at what time, accuracy and confidence?", "kind": "requirement", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "owner-operator-custodian-and-record-authority-q03", "text": "Which validation, access or change rule may revise owner, operator, custodian and record authority while preserving the prior physical-state history?", "kind": "composition", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "owner-operator-custodian-and-record-authority-data", "name": "Owner, operator, custodian and record authority assertion", "description": "Structured built-asset answer data for owner, operator, custodian and record authority, including scope, status, time and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-009" ] } ], "artifacts": [], "inline_only_rationale": "This finding stores only typed references or inline bindings; the external model owns the related payload and independent lifecycle." }, { "id": "projection-security-retention-and-legal-hold", "name": "Projection, security, retention and legal hold", "description": "Field and artifact disclosure, sensitive geometry controls, permitted purpose, retention, hold and tombstone rules.", "source_refs": [ "SRC-001", "SRC-009" ], "questions": [ { "id": "projection-security-retention-and-legal-hold-q01", "text": "What is the current governed value of projection, security, retention and legal hold for this building or structure, and which subtype or scope does it apply to?", "kind": "access", "answer_data": [ "Projection, security, retention and legal hold", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "projection-security-retention-and-legal-hold-q02", "text": "Which observation, source, method and authority establish projection, security, retention and legal hold, at what time, accuracy and confidence?", "kind": "evidence", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "projection-security-retention-and-legal-hold-q03", "text": "Which validation, access or change rule may revise projection, security, retention and legal hold while preserving the prior physical-state history?", "kind": "process", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "projection-security-retention-and-legal-hold-data", "name": "Projection, security, retention and legal hold assertion", "description": "Structured built-asset answer data for projection, security, retention and legal hold, including scope, status, time and provenance.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-009" ] } ], "artifacts": [ { "id": "projection-security-retention-and-legal-hold-artifact", "name": "Projection, security, retention and legal hold record", "description": "Versioned building-owned record supporting projection, security, retention and legal hold with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-001", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "provenance-and-exchange", "name": "Provenance and exchange", "description": "Revision lineage, validation and versioned mappings.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-009" ], "findings": [ { "id": "observation-revision-derivation-and-confidence", "name": "Observation, revision, derivation and confidence", "description": "Actor, activity, source, method, observation time, derivation, uncertainty, predecessor and correction reason.", "source_refs": [ "SRC-009", "SRC-010" ], "questions": [ { "id": "observation-revision-derivation-and-confidence-q01", "text": "What is the current governed value of observation, revision, derivation and confidence for this building or structure, and which subtype or scope does it apply to?", "kind": "provenance", "answer_data": [ "Observation, revision, derivation and confidence", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "observation-revision-derivation-and-confidence-q02", "text": "Which observation, source, method and authority establish observation, revision, derivation and confidence, at what time, accuracy and confidence?", "kind": "retention", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "observation-revision-derivation-and-confidence-q03", "text": "Which validation, access or change rule may revise observation, revision, derivation and confidence while preserving the prior physical-state history?", "kind": "interoperability", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "observation-revision-derivation-and-confidence-data", "name": "Observation, revision, derivation and confidence assertion", "description": "Structured built-asset answer data for observation, revision, derivation and confidence, including scope, status, time and provenance.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-009", "SRC-010" ] } ], "artifacts": [ { "id": "observation-revision-derivation-and-confidence-artifact", "name": "Observation, revision, derivation and confidence record", "description": "Versioned building-owned record supporting observation, revision, derivation and confidence with provenance and access marking.", "media_or_form": [ "structured built-asset record", "survey, assessment or controlled statement", "resolvable evidence index" ], "serial": true, "identity_strategy": "Authoritative built-asset master identifier first; otherwise a Dimension-governed UUID or ULID.", "source_refs": [ "SRC-009", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "ifc-citygml-schema-crosswalk-and-loss", "name": "IFC, CityGML, schema crosswalk and loss", "description": "Pinned source and target versions, model view or level of detail, field mappings, extension namespace, validation and round-trip loss.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "questions": [ { "id": "ifc-citygml-schema-crosswalk-and-loss-q01", "text": "What is the current governed value of ifc, citygml, schema crosswalk and loss for this building or structure, and which subtype or scope does it apply to?", "kind": "interoperability", "answer_data": [ "IFC, CityGML, schema crosswalk and loss", "artifact subtype and scope", "assertion status or explicit unknown" ] }, { "id": "ifc-citygml-schema-crosswalk-and-loss-q02", "text": "Which observation, source, method and authority establish ifc, citygml, schema crosswalk and loss, at what time, accuracy and confidence?", "kind": "definition", "answer_data": [ "source and authority", "method, units and observation time", "accuracy, tolerance, confidence and evidence" ] }, { "id": "ifc-citygml-schema-crosswalk-and-loss-q03", "text": "Which validation, access or change rule may revise ifc, citygml, schema crosswalk and loss while preserving the prior physical-state history?", "kind": "provenance", "answer_data": [ "validation and access rule", "authorized revision event", "predecessor, correction or counterclaim reference" ] } ], "data_elements": [ { "id": "ifc-citygml-schema-crosswalk-and-loss-data", "name": "IFC, CityGML, schema crosswalk and loss assertion", "description": "Structured built-asset answer data for ifc, citygml, schema crosswalk and loss, including scope, status, time and provenance.", "value_kind": "collection", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "artifacts": [], "inline_only_rationale": "This finding stores only typed references or inline bindings; the external model owns the related payload and independent lifecycle." } ] } ] } ] }, "functions": [ { "id": "register-built-artifact", "name": "Register built artifact", "description": "Create the authoritative building or structure identity and boundary without inventing unavailable fabric facts.", "inputs": [ "source identity", "class", "location references" ], "outputs": [ "built-artifact record" ], "preconditions": [ "record authority and namespace resolve" ], "effects": [ "stable identity and explicit unknowns exist" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "classify-and-recognize-artifact", "name": "Classify and recognize artifact", "description": "Apply a pinned taxonomy and evidence-backed distinguishing features.", "inputs": [ "artifact", "taxonomy", "observations" ], "outputs": [ "classification revision" ], "preconditions": [ "taxonomy and observation provenance resolve" ], "effects": [ "building, structure and neighbor-class uncertainty stays visible" ], "source_refs": [ "SRC-002", "SRC-005", "SRC-006" ] }, { "id": "attach-geometric-representation", "name": "Attach geometric representation", "description": "Bind a designed, as-built, surveyed or current geometry with CRS, accuracy and level of detail.", "inputs": [ "artifact", "geometry reference", "representation metadata" ], "outputs": [ "geometry binding revision" ], "preconditions": [ "CRS, purpose and source resolve" ], "effects": [ "alternate representations remain distinguishable" ], "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "compose-spatial-and-fabric-parts", "name": "Compose spatial and fabric parts", "description": "Add or revise typed complex, part, storey, space, element or material membership.", "inputs": [ "artifact", "part references", "composition rule" ], "outputs": [ "composition revision" ], "preconditions": [ "parentage and containment validate" ], "effects": [ "decomposition remains acyclic and historically traceable" ], "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] }, { "id": "bind-installed-system", "name": "Bind installed system", "description": "Reference a serving system, component register and served scope.", "inputs": [ "artifact", "system reference", "scope and function" ], "outputs": [ "system binding" ], "preconditions": [ "system master and topology resolve" ], "effects": [ "building context expands without copying equipment lifecycle" ], "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "record-physical-property", "name": "Record physical property", "description": "Append a measured or derived geometry, material or performance quantity.", "inputs": [ "subject", "value and unit", "method and conditions" ], "outputs": [ "physical-property observation" ], "preconditions": [ "unit, tolerance and observation time are present" ], "effects": [ "direct property remains attributable and time-bounded" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] }, { "id": "record-condition-assessment", "name": "Record condition assessment", "description": "Capture inspection scope, defect observations, grade, restrictions and limitations.", "inputs": [ "artifact", "inspection evidence", "assessment profile" ], "outputs": [ "condition assessment revision" ], "preconditions": [ "assessor authority and method resolve" ], "effects": [ "observation, judgement and safety decision remain separate" ], "source_refs": [ "SRC-008", "SRC-009" ] }, { "id": "assess-performance-and-capability", "name": "Assess performance and capability", "description": "Evaluate loads, serviceability, energy, environmental quality or supported use under a pinned method.", "inputs": [ "artifact", "observations", "method and requirements" ], "outputs": [ "performance assessment" ], "preconditions": [ "scope and method versions resolve" ], "effects": [ "result does not overclaim current safety or legal compliance" ], "source_refs": [ "SRC-001", "SRC-007", "SRC-008" ] }, { "id": "record-alteration-or-use-change", "name": "Record alteration or use change", "description": "Link before and after physical or functional states to authorized work and acceptance evidence.", "inputs": [ "artifact", "change set", "work and authorization references" ], "outputs": [ "change revision" ], "preconditions": [ "effective time and acceptance basis exist" ], "effects": [ "current state changes without erasing prior fabric" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-009" ] }, { "id": "decommission-or-demolish-artifact", "name": "Decommission or demolish artifact", "description": "Record physical cessation while retaining historical identity and residual references.", "inputs": [ "artifact", "decision", "completion evidence" ], "outputs": [ "end-of-life revision" ], "preconditions": [ "authority and retention policy permit action" ], "effects": [ "artifact becomes historical rather than disappearing" ], "source_refs": [ "SRC-001", "SRC-009" ] }, { "id": "issue-built-asset-projection", "name": "Issue built-asset projection", "description": "Produce a minimum authorized geometry, condition, performance or handover view.", "inputs": [ "artifact revision", "recipient and purpose", "projection policy" ], "outputs": [ "digest-pinned projection" ], "preconditions": [ "access and sensitive-geometry decision permit release" ], "effects": [ "redaction, provenance and omitted content are explicit" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-009" ] }, { "id": "map-external-built-asset-schema", "name": "Map external built-asset schema", "description": "Transform a pinned IFC, CityGML or partner representation with validation and loss declaration.", "inputs": [ "source representation", "versioned crosswalk", "target profile" ], "outputs": [ "mapped projection and report" ], "preconditions": [ "versions and model view resolve" ], "effects": [ "extensions, omissions and round-trip limits are recorded" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ] } ], "composition": [ { "target": "WM-BLT-006 Facility", "relation": "REFERENCE", "purpose": "Binds operational aggregation while the building retains independent physical identity and fabric lifecycle.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "WM-BLT-002 Premises / Spatial Unit", "relation": "COMPOSE", "purpose": "Provides the candidate spatial matryoshka for independently governed interior units while preserving their typed identities.", "required": false, "source_refs": [ "SRC-003", "SRC-005" ] }, { "target": "Site, Land Parcel, Address and Geography models", "relation": "REFERENCE", "purpose": "Locates the physical artifact without importing cadastral, tenure or address mastership.", "required": true, "source_refs": [ "SRC-002", "SRC-005" ] }, { "target": "Equipment, Product and Material models", "relation": "REFERENCE", "purpose": "Binds installed components and material classifications while external masters own serial, product and supply lifecycles.", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "target": "Construction Works, Project and Work Order models", "relation": "REFERENCE", "purpose": "Links creation and alteration evidence while execution remains independently governed.", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "target": "Person, Organization, Ownership, Permit and Document models", "relation": "REFERENCE", "purpose": "Binds parties, interests, authorizations and evidence without absorbing their lifecycle.", "required": false, "source_refs": [ "SRC-001", "SRC-009" ] }, { "target": "Incident and Hazard models", "relation": "REFERENCE", "purpose": "Links damaging events and external hazards while storing only building-local observations and assessments.", "required": false, "source_refs": [ "SRC-008", "SRC-009" ] }, { "target": "IFC 4.3 and ISO 16739-1:2024", "relation": "ALIGN", "purpose": "Supports pinned built-asset exchange mappings without making IFC serialization the logical model identity.", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "target": "CityGML 3.0", "relation": "ALIGN", "purpose": "Supports platform-independent city-scale semantics and level-of-detail projections with declared loss.", "required": false, "source_refs": [ "SRC-005" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Declare the Dimension owner, built-asset registry authority, stewards, coordinate and unit policies and delegated engineering decision roles.", "Declare building, site, parcel, space, equipment, works, permit, party, incident and document master systems.", "Publish model, object, event, relation, classification, access, retention and interoperability registries.", "Pin building or structure subtype, geometry, inspection, performance, energy, safety and jurisdiction profiles." ], "namespace_guidance": "Mint building and structure identifiers only in the adopting Dimension's governed namespace; preserve cadastral, address, IFC, CityGML, permit and facility IDs as typed aliases or references with authority and time.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md", "Dimension-local built-asset, geometry, event, policy and relation registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by registry ID, model version, built-asset master ID, immutable revision and explicit authority; do not use address, owner, geometry hash or mutable name as identity.", "Keep designed, approved, as-built, surveyed and current observed state distinct and preserve conflicting representations." ], "patch_rules": [ "Additive extensions use a Dimension-owned namespace and declare target node, subtype, source, units, rationale, safety and access impact.", "Breaking changes require a new version, migration and crosswalk maps, compatibility declaration and continued resolution of prior asset revisions." ], "compatibility_rules": [ "Consumers may ignore unknown additive fields only when identity, units, CRS, time, provenance, safety and access meaning remain intact.", "IFC, CityGML and partner mappings pin source and target versions, model view or level of detail and declare transformed, omitted or non-round-trippable values." ] }, "artifact_rules": { "identity_priority": [ "Authoritative built-asset master-system identifier and immutable revision identifier.", "Governed globally resolvable asset IRI or federation identifier.", "Adopting-Dimension UUID or ULID when no authoritative external identifier exists." ], "timestamp_rule": "Record event timestamps in RFC 3339 with seconds and an explicit UTC offset or Z; keep design, approval, construction, observation, effective, publication and ingestion times distinct.", "serial_naming_rule": "Name serial artifacts as {asset-id}--{artifact-kind}--{revision-or-event-id}; never use an address, date, filename or hash alone as asset identity.", "integrity_rule": "Store digest, media type, byte length, issuer or surveyor, method and software version, CRS, units, provenance, access marking and immutable reference for every retained serial artifact." }, "policies": [ "The adopting Dimension declares who may register, classify, survey, assess, alter, disclose, restrict, decommission and tombstone a built artifact.", "Safety, capacity, compliance and fitness-for-use claims require competent authority, declared scope, method, evidence, effective time and limitations.", "Agents never infer current safety from age, appearance, design capacity, energy certificate or generic condition grade.", "Site, tenure, parties, spaces, equipment, projects, permits, incidents, valuations, documents and work execution remain in their owning systems and are referenced.", "Automated agents may enrich low-risk measurements and mappings under delegation but must propose consequential restrictions, disclosure, demolition, safety and compliance decisions." ], "crud": { "read": [ "Resolve active Dimension, purpose, role, profiles, asset revision and external masters; return the minimum permitted view and preserve representation status and uncertainty." ], "create": [ "Create master identity, class, authority, location references and explicit unknowns before attaching fabric, geometry or performance claims." ], "update": [ "Append an immutable revision with actor, authority, reason, RFC 3339 effective time and predecessor; validate identity, containment, units, CRS, evidence, safety and access before and after mutation." ], "delete": [ "Apply retention, legal hold and end-of-life policy; tombstone built-asset records or withdraw projections while maintaining historical identity and avoiding cascading deletion of external records." ] }, "roles": [ { "name": "Dimension owner", "responsibilities": [ "Own namespace, mastership, delegation, classification, access, retention and federation rules." ] }, { "name": "Built-asset owner or custodian", "responsibilities": [ "Maintain accountable fabric record and authorize permitted disclosure and change." ] }, { "name": "Designer or engineering authority", "responsibilities": [ "Issue design basis, capacity, safety and alteration assessments within competence and mandate." ] }, { "name": "Surveyor or inspector", "responsibilities": [ "Record geometry and condition evidence with method, scope, accuracy and limitations." ] }, { "name": "Operator or facility representative", "responsibilities": [ "Supply current use, system, restriction and performance context without changing fabric authority." ] }, { "name": "Records and information steward", "responsibilities": [ "Maintain revisions, provenance, crosswalks, access, retention and handover integrity." ] }, { "name": "Auditor", "responsibilities": [ "Review decisions, evidence, changes and access without rewriting physical truth." ] } ], "access": { "default_rule": "Deny mutation and sensitive disclosure unless the active Dimension, role, purpose, asset class and field or geometry policy grant the action; expose the minimum necessary projection.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Emergency access must be time-limited, purpose-bound, attributable, independently reviewed and unable to erase immutable history, evidence, safety restrictions or legal hold." ], "audit_requirements": [ "Log actor, role, purpose, asset and revision identity, action, decision, profile version, RFC 3339 timestamp with offset, affected scope and outcome for privileged mutation or disclosure." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read the nearest Dimension-owner AGENTS.md, asset authority, active engineering profiles and access policies.", "Read this model AGENTS.md, pinned spec.yaml and required site, space, equipment, works, incident and document model instructions before mutation." ] } }, "coverage": { "claim": "A source-grounded reviewable draft of the Building / Structure aggregate across buildingSMART IFC, ISO IFC, OGC CityGML, European Union energy-performance law, NIST condition-assessment guidance, W3C provenance and IETF time standards, without a claim of universal subtype, code or exchange-profile completeness.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Master identity, aliases, complex and part continuity, merge or split and immutable revisions are explicit." }, { "dimension": "classification and recognition", "status": "covered", "notes": "Building and engineered-structure subtypes, intended function, distinguishing features, neighbor classes and confidence are represented." }, { "dimension": "direct properties", "status": "covered", "notes": "Geometry, dimensions, mass, materials, density, strength, surface and other measured properties carry units, conditions and time." }, { "dimension": "spatial", "status": "covered", "notes": "Site references, CRS, placement, pose, footprint, extents, levels of detail and hierarchical decomposition are explicit." }, { "dimension": "lifecycle", "status": "covered", "notes": "Design, construction, commissioning, alteration, repair, use change, decommissioning and demolition preserve history." }, { "dimension": "relationships", "status": "covered", "notes": "Sites, parcels, spaces, elements, materials, systems, equipment, works, parties, permits, incidents and documents use typed bindings." }, { "dimension": "temporal", "status": "covered", "notes": "Design, approval, construction, observation, effective, publication and ingestion times remain distinct." }, { "dimension": "provenance", "status": "covered", "notes": "Designed, as-built, surveyed and observed representations identify source, method, actor, software, derivation and confidence." }, { "dimension": "ownership", "status": "covered", "notes": "Owner, operator, custodian, record authority, engineering authority and external master systems have distinct roles." }, { "dimension": "validation and safety", "status": "covered", "notes": "Identity, containment, units, CRS, geometry, evidence, capacity, limitations, state and access validation are explicit." }, { "dimension": "access", "status": "covered", "notes": "Granular projections, sensitive geometry, emergency access, purpose, audit and role-bound mutation are covered." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Historical identity, legal hold, tombstone, withdrawal and non-cascading external references are explicit." }, { "dimension": "interoperability", "status": "covered", "notes": "IFC and CityGML mappings pin versions, model views or levels of detail, validation and loss." }, { "dimension": "capabilities and affordances", "status": "covered", "notes": "Supported use, occupancy, loads, access, egress, system capacity, hazards, protections and failure modes are represented." } ], "known_omissions": [ "Building-code, structural-system, bridge, tunnel, tower, dam and regional safety profiles must supply exact classes, loads, limits, tests and legal decisions.", "Component-level equipment, product, maintenance, work-order, permit, valuation and occupancy semantics remain in neighboring models.", "Certified IFC and CityGML exchange crosswalks, model-view profiles and round-trip tests remain future work." ], "conflicts": [ "IFC defines IfcBuilding as a subtype of IfcFacility while the Vercy registry uses operational Facility CONTAINS Building; the draft keeps Vercy aggregation and records IFC type hierarchy as an alignment conflict.", "The previous card said every building stands on parcels, but buildings can span or lack resolved cadastral links; parcel and site bindings are required only where an adopting profile mandates them.", "Current condition, safety and performance cannot be inferred from as-designed or as-built information and require dated evidence." ], "regional_assumptions": [ "EU energy and carbon concepts are a regional profile under Directive (EU) 2024/1275 and do not create universal metrics or certification duties.", "NIST condition-assessment material is methodological evidence, not a current universal building-code or legal requirement." ], "adversarial_checks": [ "Reject address, owner, geometry hash or project number used as the sole building identity and reject silent identity change after subdivision or connection.", "Reject geometry or physical quantities without units, CRS where relevant, representation status, tolerance, method, observation time and provenance.", "Reject design capacity, age, appearance or generic condition grade presented as proof of current safety, compliance or fitness for use.", "Reject copied site, tenure, party, space, equipment, work, permit, incident or document lifecycles when governed references are sufficient.", "Reject demolition, safety restriction, sensitive-geometry disclosure or external schema export without authority, purpose, preserved history and loss declaration." ] }, "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": "aggregate", "status": "accepted", "rationale": "A building or engineered structure persists as one governed physical artifact while aggregating spatial parts, fabric, material and system bindings plus evolving observations and lifecycle events, so aggregate is more defensible than entity." }, "decisions": [ { "concept": "Building versus Facility", "disposition": "accepted as separate", "rationale": "Building or structure owns persistent physical fabric, while Facility owns the managed operational aggregation. The existing Vercy Facility CONTAINS Building relation is retained with an explicit IFC type-hierarchy conflict." }, { "concept": "Premises and spatial units", "disposition": "accepted as candidate COMPOSE", "rationale": "The approved registry candidate WM-BLT-001 CONTAINS WM-BLT-002 expresses the spatial matryoshka, while independently governed premises keep their own identity and lifecycle." }, { "concept": "Broad structure class", "disposition": "accepted with subtype profiles", "rationale": "The base covers roofed buildings and engineered works, but bridge, tunnel, tower, dam and other profiles must specialize geometry, components, actions, hazards and performance rules." }, { "concept": "Geometry truth", "disposition": "accepted as multiple time-bound representations", "rationale": "Designed, approved, as-built, surveyed and current observed geometry must remain distinct and carry CRS, units, accuracy, level of detail, method and provenance." }, { "concept": "Direct physical properties", "disposition": "accepted", "rationale": "Geometry, dimensions, mass, materials, density, strength, hardness, fragility and surface properties belong in the physical model when observed with units, tolerance, conditions and time." }, { "concept": "System and equipment boundary", "disposition": "accepted as typed references", "rationale": "The structure owns system function, served scope, interfaces and dependencies while serial equipment identity, maintenance, warranties and spare parts remain external." }, { "concept": "Condition versus safety", "disposition": "accepted as separate", "rationale": "A defect observation or condition grade is not proof of current capacity, compliance or fitness. Engineering conclusions require competent authority, scope, method, evidence and limitations." }, { "concept": "Incident, damage and repair", "disposition": "accepted as separate records", "rationale": "The incident remains external, damage is a building-local observation, assessment interprets it, restrictions are governed decisions and repair is referenced work execution." }, { "concept": "IFC and CityGML", "disposition": "accepted as ALIGN", "rationale": "Both standards provide valuable schemas and conceptual mappings, but neither serialization determines Vercy logical identity and every crosswalk must pin versions and disclose loss." }, { "concept": "EU energy profile", "disposition": "accepted as regional binding", "rationale": "Directive (EU) 2024/1275 supports energy, carbon, renovation and technical-system concepts only where the relevant jurisdiction and implementation apply." }, { "concept": "Identity after demolition", "disposition": "accepted as historical persistence", "rationale": "Physical removal changes lifecycle state but does not erase the asset identity, prior observations, legal references or provenance." }, { "concept": "Question coverage", "disposition": "accepted as reviewable draft", "rationale": "Every finding asks for subtype scope, source and method, observation time, accuracy and authorized revision. Machine-oriented repetition still requires later engineering-profile review." } ], "publicationHolds": [ "Claude and Grok timed out during their bounded attempts, so independent external review is absent and explicitly waived for this published reviewable draft.", "IFC defines IfcBuilding as a subtype of IfcFacility while the Vercy registry uses Facility CONTAINS Building; the operational Vercy relation is retained but requires a formal crosswalk decision.", "Building-code, structure-subtype, structural-safety, energy and jurisdiction profiles need competent specialist review before operational enforcement.", "Certified IFC and CityGML field mappings, model-view constraints and round-trip tests remain unverified for canonical conformance.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Validate the base against building, bridge, tunnel, tower, dam, retaining-structure and temporary-works subtype profiles.", "Develop formal structural, fire, accessibility, energy, indoor-environment and climate-hazard profile recipes with jurisdictional authority.", "Create certified IFC 4.3 and CityGML 3.0 crosswalks with model views, levels of detail, validation fixtures and declared information loss.", "Approve sibling model identifiers and relation cardinalities for sites, parcels, spaces, equipment, materials, works, permits, incidents and documents." ] }, "statistics": { "sources": 10, "bundles": 7, "layers": 16, "findings": 32, "questions": 96, "artifacts": 25, "functions": 12 } }