# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-06T00:53:52Z", "synthesisSha256": "fe7db7276ba03a268929c6a6f39652d256368ed3993339b766911cf503364b59", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-OBJ-007", "registryId": "vr.wm-obj-007", "name": "Vehicle", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Physical world and living systems", "industry": [ "Cross-industry" ], "domain": [ "PHY.OBJ.VEH" ], "tags": [ "vehicle", "phy.obj.veh" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-obj-007-vehicle/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-obj-007", "model": { "registry_id": "vr.wm-obj-007", "model_id": "WM-OBJ-007", "name": "Vehicle", "entry_kind": "entity", "purpose": "Represent an individual multimodal vehicle as a physical system with stable identity, measurable form, composition, capabilities, observed state and governed lifecycle so agents can recognize, reason about and act safely around it.", "scope_statement": "Owns vehicle instance identity, mode and class assertions, physical composition, intrinsic specifications, installed systems, propulsion and energy, capacities, capabilities, recognition profile, observed state, configuration and lifecycle history, party-role references, safety and interoperability projections while external systems own type designs, components, parties, journeys, cargo, registrations, certificates, maintenance work and telemetry events.", "in_scope": [ "Vehicle instance identity, mode, category, purpose, geometry, dimensions, mass, materials, construction and installed configuration", "Propulsion, energy, capacity, operating envelope, affordances, recognition, position, telemetry, condition, faults and operability", "Manufacture, commissioning, modification, ownership and custody roles, registrations, service, safety, compliance, access, retention and per-mode projections" ], "out_of_scope": [ "Vehicle type, model, variant, component, engine, battery, sensor, party, occupant, cargo, shipment, journey, route, registration, title, permit, certificate, maintenance work order or incident master lifecycle", "Universal legal categorization or approval across every road, rail, maritime, aviation, space, industrial and micro-mobility regime", "Automatic authority to operate, control, track, disclose or modify a vehicle based on technical capability or record access alone" ], "boundary_notes": [ { "neighbor": "Vehicle Type, Model, Variant and Version", "distinction": "Design and regulatory classes define shared properties and approvals; this model represents one physical instance and records which class applied when.", "source_refs": [ "SRC-001", "SRC-004" ] }, { "neighbor": "Component and System", "distinction": "Engines, batteries, sensors, controls and structural assemblies have separate identity and lifecycle and are linked through versioned installation configuration.", "source_refs": [ "SRC-004", "SRC-008" ] }, { "neighbor": "Party and Role", "distinction": "Owner, keeper, operator, custodian, occupant, manufacturer and maintainer are separate parties and time-bound roles, not attributes that determine vehicle identity.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-009" ] }, { "neighbor": "Journey, Movement, Shipment and Cargo", "distinction": "The vehicle provides carriage capability and may participate in movements; trip plan, execution, cargo and custody histories remain external events and objects.", "source_refs": [ "SRC-001", "SRC-004" ] }, { "neighbor": "Registration, Approval, Certificate and Maintenance", "distinction": "These governed records and processes reference the vehicle but retain their own issuer, scope, validity, status and lifecycle.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] }, { "neighbor": "Sensor Observation and Telemetry", "distinction": "The vehicle is the feature of interest or platform; sensors, procedures, observations and results remain event records with phenomenon and result time.", "source_refs": [ "SRC-008", "SRC-010" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Consolidated Resolution on the Construction of Vehicles (R.E.3)", "organization": "United Nations Economic Commission for Europe", "url": "https://unece.org/transport/vehicle-regulations/wp29/resolutions", "version_or_date": "ECE/TRANS/WP.29/78/Rev.7 listed 2026", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T00:45:00Z", "relevance": "Defines road-vehicle categories and construction terminology under the international vehicle-regulation framework." }, { "id": "SRC-002", "title": "ISO 3779:2009 Road vehicles, Vehicle identification number", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/52200.html", "version_or_date": "Edition 4, confirmed 2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T00:45:00Z", "relevance": "Defines worldwide VIN content and structure for road motor vehicles, towed vehicles, motorcycles and mopeds." }, { "id": "SRC-003", "title": "Vehicle Manufacturers and vPIC", "organization": "National Highway Traffic Safety Administration", "url": "https://www.nhtsa.gov/vehicle-manufacturers", "version_or_date": "Current service accessed 2026-09-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T00:45:00Z", "relevance": "Provides manufacturer-reported vehicle product and identifier data and VIN decoding context." }, { "id": "SRC-004", "title": "Regulation (EU) 2018/858", "organization": "European Union", "url": "https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX:32018R0858", "version_or_date": "Consolidated legal text accessed 2026-09-06", "source_type": "legislation", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T00:45:00Z", "relevance": "Defines road vehicle and trailer categories, type, variant, version, approval, conformity and market-surveillance concepts." }, { "id": "SRC-005", "title": "IMO identification number schemes", "organization": "International Maritime Organization", "url": "https://www.imo.org/en/ourwork/msas/pages/imo-identification-number-scheme.aspx", "version_or_date": "Current scheme page accessed 2026-09-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T00:45:00Z", "relevance": "Defines permanent ship and registered owner or company identifiers and distinguishes identity from name, flag and ownership changes." }, { "id": "SRC-006", "title": "Aircraft Nationality and Registration Marks", "organization": "International Civil Aviation Organization", "url": "https://www.icao.int/nationality-marks", "version_or_date": "Annex 7 overview accessed 2026-09-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T00:45:00Z", "relevance": "Defines aircraft nationality, common and registration marks and their registering authority." }, { "id": "SRC-007", "title": "European Vehicle Register", "organization": "European Union Agency for Railways", "url": "https://www.era.europa.eu/registers/evr_en", "version_or_date": "Production register guidance accessed 2026-09-06", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T00:45:00Z", "relevance": "Defines rail-vehicle numbers, keepers, registration entities and registration updates." }, { "id": "SRC-008", "title": "Semantic Sensor Network Ontology", "organization": "World Wide Web Consortium and Open Geospatial Consortium", "url": "https://www.w3.org/TR/vocab-ssn/", "version_or_date": "W3C Recommendation, 19 October 2017", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-06T00:45:00Z", "relevance": "Defines systems, platforms, deployments, capabilities, operating ranges, sensors, observations, actuators, procedures and results." }, { "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-06T00:45:00Z", "relevance": "Defines entity, activity, agent, attribution, source, derivation, revision and invalidation provenance." }, { "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-06T00:45:00Z", "relevance": "Defines interoperable event timestamps with seconds and an explicit UTC offset." } ], "structure": { "bundles": [ { "id": "identity-classification-and-registry", "name": "Identity, classification and registry", "description": "Identifies the vehicle independently of its type, name, operator and registration.", "rationale": "VIN, IMO number, aircraft mark, rail number and local asset ID have different authorities and applicability.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "layers": [ { "id": "vehicle-master-identity", "name": "Vehicle master identity", "description": "Stable instance identity, authority and aliases.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007" ], "findings": [ { "id": "authoritative-instance-identifier", "name": "Authoritative instance identifier", "description": "Records the master identifier, scheme, issuing authority, validation, assignment time and prior identifiers.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007" ], "questions": [ { "id": "authoritative-instance-identifier-q01", "text": "What exact design and observed values must be recorded for authoritative instance identifier, with units, tolerance and applicability where relevant?", "kind": "identity", "answer_data": [ "Authoritative instance identifier", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "authoritative-instance-identifier-q02", "text": "Which source, authority, method and evidence establish authoritative instance identifier, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "authoritative-instance-identifier-q03", "text": "How is authoritative instance identifier validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "authoritative-instance-identifier-record", "name": "Authoritative instance identifier record", "description": "Structured source-qualified values for authoritative instance identifier including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "authoritative-instance-identifier-artifact", "name": "Vehicle identity record", "description": "Versioned evidence or exchange artifact supporting authoritative instance identifier without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "registration-mark-serial-and-display-identity", "name": "Registration mark, serial and display identity", "description": "Records mutable marks, manufacturer serial, fleet number, plate, name and marking location.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007" ], "questions": [ { "id": "registration-mark-serial-and-display-identity-q01", "text": "What exact design and observed values must be recorded for registration mark, serial and display identity, with units, tolerance and applicability where relevant?", "kind": "identity", "answer_data": [ "Registration mark, serial and display identity", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "registration-mark-serial-and-display-identity-q02", "text": "Which source, authority, method and evidence establish registration mark, serial and display identity, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "registration-mark-serial-and-display-identity-q03", "text": "How is registration mark, serial and display identity validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "registration-mark-serial-and-display-identity-record", "name": "Registration mark, serial and display identity record", "description": "Structured source-qualified values for registration mark, serial and display identity including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "registration-mark-serial-and-display-identity-artifact", "name": "Identity marking inventory", "description": "Versioned evidence or exchange artifact supporting registration mark, serial and display identity without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "mode-class-purpose-and-boundary", "name": "Mode, class, purpose and boundary", "description": "Functional and regulatory classification with explicit applicability.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "findings": [ { "id": "transport-mode-vehicle-category-and-role", "name": "Transport mode, vehicle category and role", "description": "Classifies road, rail, water, air or other mode, powered status, carriage purpose and source vocabulary.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "questions": [ { "id": "transport-mode-vehicle-category-and-role-q01", "text": "What exact design and observed values must be recorded for transport mode, vehicle category and role, with units, tolerance and applicability where relevant?", "kind": "classification", "answer_data": [ "Transport mode, vehicle category and role", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "transport-mode-vehicle-category-and-role-q02", "text": "Which source, authority, method and evidence establish transport mode, vehicle category and role, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "transport-mode-vehicle-category-and-role-q03", "text": "How is transport mode, vehicle category and role validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "transport-mode-vehicle-category-and-role-record", "name": "Transport mode, vehicle category and role record", "description": "Structured source-qualified values for transport mode, vehicle category and role including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "transport-mode-vehicle-category-and-role-artifact", "name": "Vehicle classification profile", "description": "Versioned evidence or exchange artifact supporting transport mode, vehicle category and role without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "instance-type-component-cargo-and-event-boundary", "name": "Instance, type, component, cargo and event boundary", "description": "Separates the vehicle from design type, component, carried subject, journey, permit and maintenance event.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-008" ], "questions": [ { "id": "instance-type-component-cargo-and-event-boundary-q01", "text": "What exact design and observed values must be recorded for instance, type, component, cargo and event boundary, with units, tolerance and applicability where relevant?", "kind": "relationship", "answer_data": [ "Instance, type, component, cargo and event boundary", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "instance-type-component-cargo-and-event-boundary-q02", "text": "Which source, authority, method and evidence establish instance, type, component, cargo and event boundary, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "instance-type-component-cargo-and-event-boundary-q03", "text": "How is instance, type, component, cargo and event boundary validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "instance-type-component-cargo-and-event-boundary-record", "name": "Instance, type, component, cargo and event boundary record", "description": "Structured source-qualified values for instance, type, component, cargo and event boundary including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "instance-type-component-cargo-and-event-boundary-artifact", "name": "Vehicle boundary decision", "description": "Versioned evidence or exchange artifact supporting instance, type, component, cargo and event boundary without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "physical-form-composition-and-construction", "name": "Physical form, composition and construction", "description": "Describes geometry, quantities, materials, assemblies and installed systems.", "rationale": "Direct physical properties must remain distinct from type-design limits and changing observations.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ], "layers": [ { "id": "geometry-dimensions-mass-and-pose", "name": "Geometry, dimensions, mass and pose", "description": "Measured or declared physical extent and spatial configuration.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ], "findings": [ { "id": "geometry-dimensions-volume-and-clearance", "name": "Geometry, dimensions, volume and clearance", "description": "Records coordinate frame, shape, length, width, height, draft, envelope, clearances, units and tolerance.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ], "questions": [ { "id": "geometry-dimensions-volume-and-clearance-q01", "text": "What exact design and observed values must be recorded for geometry, dimensions, volume and clearance, with units, tolerance and applicability where relevant?", "kind": "measurement", "answer_data": [ "Geometry, dimensions, volume and clearance", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "geometry-dimensions-volume-and-clearance-q02", "text": "Which source, authority, method and evidence establish geometry, dimensions, volume and clearance, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "geometry-dimensions-volume-and-clearance-q03", "text": "How is geometry, dimensions, volume and clearance validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "geometry-dimensions-volume-and-clearance-record", "name": "Geometry, dimensions, volume and clearance record", "description": "Structured source-qualified values for geometry, dimensions, volume and clearance including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "geometry-dimensions-volume-and-clearance-artifact", "name": "Dimensional survey", "description": "Versioned evidence or exchange artifact supporting geometry, dimensions, volume and clearance without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "mass-balance-centre-of-gravity-and-pose", "name": "Mass, balance, centre of gravity and pose", "description": "Records empty, operating, payload and maximum masses, loads, balance, centre of gravity and orientation.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ], "questions": [ { "id": "mass-balance-centre-of-gravity-and-pose-q01", "text": "What exact design and observed values must be recorded for mass, balance, centre of gravity and pose, with units, tolerance and applicability where relevant?", "kind": "measurement", "answer_data": [ "Mass, balance, centre of gravity and pose", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "mass-balance-centre-of-gravity-and-pose-q02", "text": "Which source, authority, method and evidence establish mass, balance, centre of gravity and pose, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "mass-balance-centre-of-gravity-and-pose-q03", "text": "How is mass, balance, centre of gravity and pose validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "mass-balance-centre-of-gravity-and-pose-record", "name": "Mass, balance, centre of gravity and pose record", "description": "Structured source-qualified values for mass, balance, centre of gravity and pose including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "mass-balance-centre-of-gravity-and-pose-artifact", "name": "Mass and pose record", "description": "Versioned evidence or exchange artifact supporting mass, balance, centre of gravity and pose without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "structure-materials-and-assemblies", "name": "Structure, materials and assemblies", "description": "Body and load-bearing construction across modes.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ], "findings": [ { "id": "body-chassis-hull-airframe-and-running-gear", "name": "Body, chassis, hull, airframe and running gear", "description": "References load-bearing structure, body, hull, airframe, bogies, axles, landing gear or equivalent assemblies.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007", "SRC-008" ], "questions": [ { "id": "body-chassis-hull-airframe-and-running-gear-q01", "text": "What exact design and observed values must be recorded for body, chassis, hull, airframe and running gear, with units, tolerance and applicability where relevant?", "kind": "composition", "answer_data": [ "Body, chassis, hull, airframe and running gear", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "body-chassis-hull-airframe-and-running-gear-q02", "text": "Which source, authority, method and evidence establish body, chassis, hull, airframe and running gear, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "body-chassis-hull-airframe-and-running-gear-q03", "text": "How is body, chassis, hull, airframe and running gear validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "body-chassis-hull-airframe-and-running-gear-record", "name": "Body, chassis, hull, airframe and running gear record", "description": "Structured source-qualified values for body, chassis, hull, airframe and running gear including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "body-chassis-hull-airframe-and-running-gear-artifact", "name": "Structural assembly manifest", "description": "Versioned evidence or exchange artifact supporting body, chassis, hull, airframe and running gear without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "materials-coatings-joints-and-integrity", "name": "Materials, coatings, joints and integrity", "description": "Records materials, construction, coatings, critical joints, corrosion or fatigue zones, hardness and fragility.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "materials-coatings-joints-and-integrity-q01", "text": "What exact design and observed values must be recorded for materials, coatings, joints and integrity, with units, tolerance and applicability where relevant?", "kind": "composition", "answer_data": [ "Materials, coatings, joints and integrity", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "materials-coatings-joints-and-integrity-q02", "text": "Which source, authority, method and evidence establish materials, coatings, joints and integrity, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "materials-coatings-joints-and-integrity-q03", "text": "How is materials, coatings, joints and integrity validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "materials-coatings-joints-and-integrity-record", "name": "Materials, coatings, joints and integrity record", "description": "Structured source-qualified values for materials, coatings, joints and integrity including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "materials-coatings-joints-and-integrity-artifact", "name": "Material and integrity profile", "description": "Versioned evidence or exchange artifact supporting materials, coatings, joints and integrity without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "installed-systems-and-payload-interface", "name": "Installed systems and payload interface", "description": "Whole-part configuration and carriage interfaces.", "source_refs": [ "SRC-004", "SRC-008" ], "findings": [ { "id": "installed-subsystems-components-and-configuration", "name": "Installed subsystems, components and configuration", "description": "References propulsion, energy, control, navigation, braking, communication, safety, sensor and actuator assemblies.", "source_refs": [ "SRC-004", "SRC-008" ], "questions": [ { "id": "installed-subsystems-components-and-configuration-q01", "text": "What exact design and observed values must be recorded for installed subsystems, components and configuration, with units, tolerance and applicability where relevant?", "kind": "composition", "answer_data": [ "Installed subsystems, components and configuration", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "installed-subsystems-components-and-configuration-q02", "text": "Which source, authority, method and evidence establish installed subsystems, components and configuration, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "installed-subsystems-components-and-configuration-q03", "text": "How is installed subsystems, components and configuration validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "installed-subsystems-components-and-configuration-record", "name": "Installed subsystems, components and configuration record", "description": "Structured source-qualified values for installed subsystems, components and configuration including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "installed-subsystems-components-and-configuration-artifact", "name": "Installed system configuration", "description": "Versioned evidence or exchange artifact supporting installed subsystems, components and configuration without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "occupant-cargo-coupling-and-loading-interface", "name": "Occupant, cargo, coupling and loading interface", "description": "Describes seats, holds, doors, ramps, attachment points, couplers, restraints and loading constraints.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "occupant-cargo-coupling-and-loading-interface-q01", "text": "What exact design and observed values must be recorded for occupant, cargo, coupling and loading interface, with units, tolerance and applicability where relevant?", "kind": "composition", "answer_data": [ "Occupant, cargo, coupling and loading interface", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "occupant-cargo-coupling-and-loading-interface-q02", "text": "Which source, authority, method and evidence establish occupant, cargo, coupling and loading interface, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "occupant-cargo-coupling-and-loading-interface-q03", "text": "How is occupant, cargo, coupling and loading interface validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "occupant-cargo-coupling-and-loading-interface-record", "name": "Occupant, cargo, coupling and loading interface record", "description": "Structured source-qualified values for occupant, cargo, coupling and loading interface including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "occupant-cargo-coupling-and-loading-interface-artifact", "name": "Carriage interface plan", "description": "Versioned evidence or exchange artifact supporting occupant, cargo, coupling and loading interface without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "propulsion-energy-and-environmental-performance", "name": "Propulsion, energy and environmental performance", "description": "Represents movement generation, energy storage and condition-dependent performance.", "rationale": "Propulsion capability and consumption cannot be inferred from registration class alone.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ], "layers": [ { "id": "propulsion-drive-and-control", "name": "Propulsion, drive and control", "description": "Prime movers, transmission and movement controls.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ], "findings": [ { "id": "prime-mover-propulsor-and-drivetrain", "name": "Prime mover, propulsor and drivetrain", "description": "References engines, motors, sails, propellers, rotors, wheels, tracks, transmissions and thrust paths.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ], "questions": [ { "id": "prime-mover-propulsor-and-drivetrain-q01", "text": "What exact design and observed values must be recorded for prime mover, propulsor and drivetrain, with units, tolerance and applicability where relevant?", "kind": "composition", "answer_data": [ "Prime mover, propulsor and drivetrain", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "prime-mover-propulsor-and-drivetrain-q02", "text": "Which source, authority, method and evidence establish prime mover, propulsor and drivetrain, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "prime-mover-propulsor-and-drivetrain-q03", "text": "How is prime mover, propulsor and drivetrain validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "prime-mover-propulsor-and-drivetrain-record", "name": "Prime mover, propulsor and drivetrain record", "description": "Structured source-qualified values for prime mover, propulsor and drivetrain including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "prime-mover-propulsor-and-drivetrain-artifact", "name": "Propulsion architecture", "description": "Versioned evidence or exchange artifact supporting prime mover, propulsor and drivetrain without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "steering-braking-stability-and-control-authority", "name": "Steering, braking, stability and control authority", "description": "Records steering, guidance, stopping, stability, manual, remote or automated authority and degraded behavior.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ], "questions": [ { "id": "steering-braking-stability-and-control-authority-q01", "text": "What exact design and observed values must be recorded for steering, braking, stability and control authority, with units, tolerance and applicability where relevant?", "kind": "state", "answer_data": [ "Steering, braking, stability and control authority", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "steering-braking-stability-and-control-authority-q02", "text": "Which source, authority, method and evidence establish steering, braking, stability and control authority, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "steering-braking-stability-and-control-authority-q03", "text": "How is steering, braking, stability and control authority validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "steering-braking-stability-and-control-authority-record", "name": "Steering, braking, stability and control authority record", "description": "Structured source-qualified values for steering, braking, stability and control authority including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "steering-braking-stability-and-control-authority-artifact", "name": "Control and stopping capability", "description": "Versioned evidence or exchange artifact supporting steering, braking, stability and control authority without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "energy-consumption-emissions-and-range", "name": "Energy, consumption, emissions and range", "description": "Energy storage, replenishment and performance.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ], "findings": [ { "id": "fuel-battery-energy-storage-and-replenishment", "name": "Fuel, battery, energy storage and replenishment", "description": "Records energy stores, capacity, chemistry or carrier, connectors, replenishment limits and observed state.", "source_refs": [ "SRC-004", "SRC-008" ], "questions": [ { "id": "fuel-battery-energy-storage-and-replenishment-q01", "text": "What exact design and observed values must be recorded for fuel, battery, energy storage and replenishment, with units, tolerance and applicability where relevant?", "kind": "measurement", "answer_data": [ "Fuel, battery, energy storage and replenishment", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "fuel-battery-energy-storage-and-replenishment-q02", "text": "Which source, authority, method and evidence establish fuel, battery, energy storage and replenishment, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "fuel-battery-energy-storage-and-replenishment-q03", "text": "How is fuel, battery, energy storage and replenishment validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "fuel-battery-energy-storage-and-replenishment-record", "name": "Fuel, battery, energy storage and replenishment record", "description": "Structured source-qualified values for fuel, battery, energy storage and replenishment including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "fuel-battery-energy-storage-and-replenishment-artifact", "name": "Energy system state", "description": "Versioned evidence or exchange artifact supporting fuel, battery, energy storage and replenishment without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "consumption-emissions-efficiency-and-range", "name": "Consumption, emissions, efficiency and range", "description": "Records declared and observed consumption, emissions, efficiency, endurance and range with conditions.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ], "questions": [ { "id": "consumption-emissions-efficiency-and-range-q01", "text": "What exact design and observed values must be recorded for consumption, emissions, efficiency and range, with units, tolerance and applicability where relevant?", "kind": "measurement", "answer_data": [ "Consumption, emissions, efficiency and range", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "consumption-emissions-efficiency-and-range-q02", "text": "Which source, authority, method and evidence establish consumption, emissions, efficiency and range, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "consumption-emissions-efficiency-and-range-q03", "text": "How is consumption, emissions, efficiency and range validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "consumption-emissions-efficiency-and-range-record", "name": "Consumption, emissions, efficiency and range record", "description": "Structured source-qualified values for consumption, emissions, efficiency and range including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "consumption-emissions-efficiency-and-range-artifact", "name": "Performance observation series", "description": "Versioned evidence or exchange artifact supporting consumption, emissions, efficiency and range without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "capacity-capabilities-and-affordances", "name": "Capacity, capabilities and affordances", "description": "Defines what the vehicle can carry or do and where it can operate.", "rationale": "Safe action requires operating limits, prerequisites, hazards and failure modes.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ], "layers": [ { "id": "capacity-and-load-envelope", "name": "Capacity and load envelope", "description": "Occupant, cargo, towing and distributed-load limits.", "source_refs": [ "SRC-001", "SRC-004" ], "findings": [ { "id": "occupant-cargo-and-volume-capacity", "name": "Occupant, cargo and volume capacity", "description": "Records seating, standing, berth, accessibility, mass, volume and special-cargo capacity.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "occupant-cargo-and-volume-capacity-q01", "text": "What exact design and observed values must be recorded for occupant, cargo and volume capacity, with units, tolerance and applicability where relevant?", "kind": "measurement", "answer_data": [ "Occupant, cargo and volume capacity", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "occupant-cargo-and-volume-capacity-q02", "text": "Which source, authority, method and evidence establish occupant, cargo and volume capacity, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "occupant-cargo-and-volume-capacity-q03", "text": "How is occupant, cargo and volume capacity validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "occupant-cargo-and-volume-capacity-record", "name": "Occupant, cargo and volume capacity record", "description": "Structured source-qualified values for occupant, cargo and volume capacity including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "occupant-cargo-and-volume-capacity-artifact", "name": "Capacity certificate", "description": "Versioned evidence or exchange artifact supporting occupant, cargo and volume capacity without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null }, { "id": "towing-coupling-axle-and-structural-load-limits", "name": "Towing, coupling, axle and structural load limits", "description": "Records tow, coupling, axle, deck, floor, wing or structural load limits and compatibility requirements.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "towing-coupling-axle-and-structural-load-limits-q01", "text": "What exact design and observed values must be recorded for towing, coupling, axle and structural load limits, with units, tolerance and applicability where relevant?", "kind": "constraint", "answer_data": [ "Towing, coupling, axle and structural load limits", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "towing-coupling-axle-and-structural-load-limits-q02", "text": "Which source, authority, method and evidence establish towing, coupling, axle and structural load limits, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "towing-coupling-axle-and-structural-load-limits-q03", "text": "How is towing, coupling, axle and structural load limits validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "towing-coupling-axle-and-structural-load-limits-record", "name": "Towing, coupling, axle and structural load limits record", "description": "Structured source-qualified values for towing, coupling, axle and structural load limits including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "towing-coupling-axle-and-structural-load-limits-artifact", "name": "Load limit matrix", "description": "Versioned evidence or exchange artifact supporting towing, coupling, axle and structural load limits without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "mobility-operating-envelope-and-interaction", "name": "Mobility, operating envelope and interaction", "description": "Movement performance, allowed conditions and interfaces.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ], "findings": [ { "id": "speed-manoeuvre-terrain-medium-and-weather-envelope", "name": "Speed, manoeuvre, terrain, medium and weather envelope", "description": "Records speed, acceleration, grade, turning, depth, altitude, route infrastructure, terrain and weather limits.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ], "questions": [ { "id": "speed-manoeuvre-terrain-medium-and-weather-envelope-q01", "text": "What exact design and observed values must be recorded for speed, manoeuvre, terrain, medium and weather envelope, with units, tolerance and applicability where relevant?", "kind": "constraint", "answer_data": [ "Speed, manoeuvre, terrain, medium and weather envelope", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "speed-manoeuvre-terrain-medium-and-weather-envelope-q02", "text": "Which source, authority, method and evidence establish speed, manoeuvre, terrain, medium and weather envelope, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "speed-manoeuvre-terrain-medium-and-weather-envelope-q03", "text": "How is speed, manoeuvre, terrain, medium and weather envelope validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "speed-manoeuvre-terrain-medium-and-weather-envelope-record", "name": "Speed, manoeuvre, terrain, medium and weather envelope record", "description": "Structured source-qualified values for speed, manoeuvre, terrain, medium and weather envelope including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "speed-manoeuvre-terrain-medium-and-weather-envelope-artifact", "name": "Operating envelope", "description": "Versioned evidence or exchange artifact supporting speed, manoeuvre, terrain, medium and weather envelope without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "boarding-loading-driving-command-and-service-affordances", "name": "Boarding, loading, driving, command and service affordances", "description": "Describes actions, required interfaces, tools, permissions, effects, reversibility, hazards and failure modes.", "source_refs": [ "SRC-004", "SRC-008" ], "questions": [ { "id": "boarding-loading-driving-command-and-service-affordances-q01", "text": "What exact design and observed values must be recorded for boarding, loading, driving, command and service affordances, with units, tolerance and applicability where relevant?", "kind": "process", "answer_data": [ "Boarding, loading, driving, command and service affordances", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "boarding-loading-driving-command-and-service-affordances-q02", "text": "Which source, authority, method and evidence establish boarding, loading, driving, command and service affordances, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "boarding-loading-driving-command-and-service-affordances-q03", "text": "How is boarding, loading, driving, command and service affordances validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "boarding-loading-driving-command-and-service-affordances-record", "name": "Boarding, loading, driving, command and service affordances record", "description": "Structured source-qualified values for boarding, loading, driving, command and service affordances including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "boarding-loading-driving-command-and-service-affordances-artifact", "name": "Affordance and action catalogue", "description": "Versioned evidence or exchange artifact supporting boarding, loading, driving, command and service affordances without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "recognition-observation-and-operational-state", "name": "Recognition, observation and operational state", "description": "Supports real-world identification and time-bound state.", "rationale": "Mutable pose, load and health require observation context, confidence and evidence.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-010" ], "layers": [ { "id": "appearance-markings-and-recognition", "name": "Appearance, markings and recognition", "description": "Visual, electronic and machine-readable identity signals.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007" ], "findings": [ { "id": "colour-shape-livery-markings-and-distinguishing-features", "name": "Colour, shape, livery, markings and distinguishing features", "description": "Records observed colour, shape, livery, damage, decals, plates and distinguishing features.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008" ], "questions": [ { "id": "colour-shape-livery-markings-and-distinguishing-features-q01", "text": "What exact design and observed values must be recorded for colour, shape, livery, markings and distinguishing features, with units, tolerance and applicability where relevant?", "kind": "classification", "answer_data": [ "Colour, shape, livery, markings and distinguishing features", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "colour-shape-livery-markings-and-distinguishing-features-q02", "text": "Which source, authority, method and evidence establish colour, shape, livery, markings and distinguishing features, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "colour-shape-livery-markings-and-distinguishing-features-q03", "text": "How is colour, shape, livery, markings and distinguishing features validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "colour-shape-livery-markings-and-distinguishing-features-record", "name": "Colour, shape, livery, markings and distinguishing features record", "description": "Structured source-qualified values for colour, shape, livery, markings and distinguishing features including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "colour-shape-livery-markings-and-distinguishing-features-artifact", "name": "Vehicle recognition profile", "description": "Versioned evidence or exchange artifact supporting colour, shape, livery, markings and distinguishing features without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-003", "SRC-005", "SRC-006", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "electronic-identifier-signal-and-recognition-confidence", "name": "Electronic identifier, signal and recognition confidence", "description": "Records transponder, beacon, tag or radio observations, sensor, position, match candidates and spoofing risk.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008" ], "questions": [ { "id": "electronic-identifier-signal-and-recognition-confidence-q01", "text": "What exact design and observed values must be recorded for electronic identifier, signal and recognition confidence, with units, tolerance and applicability where relevant?", "kind": "security", "answer_data": [ "Electronic identifier, signal and recognition confidence", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "electronic-identifier-signal-and-recognition-confidence-q02", "text": "Which source, authority, method and evidence establish electronic identifier, signal and recognition confidence, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "electronic-identifier-signal-and-recognition-confidence-q03", "text": "How is electronic identifier, signal and recognition confidence validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "electronic-identifier-signal-and-recognition-confidence-record", "name": "Electronic identifier, signal and recognition confidence record", "description": "Structured source-qualified values for electronic identifier, signal and recognition confidence including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008" ] } ], "artifacts": [ { "id": "electronic-identifier-signal-and-recognition-confidence-artifact", "name": "Electronic recognition event", "description": "Versioned evidence or exchange artifact supporting electronic identifier, signal and recognition confidence without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "location-motion-and-telemetry", "name": "Location, motion and telemetry", "description": "Time-bound state observations.", "source_refs": [ "SRC-008", "SRC-010" ], "findings": [ { "id": "position-orientation-velocity-and-route-state", "name": "Position, orientation, velocity and route state", "description": "Records coordinate reference, position, altitude or depth, heading, attitude, speed, route and uncertainty.", "source_refs": [ "SRC-008", "SRC-010" ], "questions": [ { "id": "position-orientation-velocity-and-route-state-q01", "text": "What exact design and observed values must be recorded for position, orientation, velocity and route state, with units, tolerance and applicability where relevant?", "kind": "spatial", "answer_data": [ "Position, orientation, velocity and route state", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "position-orientation-velocity-and-route-state-q02", "text": "Which source, authority, method and evidence establish position, orientation, velocity and route state, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "position-orientation-velocity-and-route-state-q03", "text": "How is position, orientation, velocity and route state validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "position-orientation-velocity-and-route-state-record", "name": "Position, orientation, velocity and route state record", "description": "Structured source-qualified values for position, orientation, velocity and route state including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008", "SRC-010" ] } ], "artifacts": [ { "id": "position-orientation-velocity-and-route-state-artifact", "name": "Position and motion observation", "description": "Versioned evidence or exchange artifact supporting position, orientation, velocity and route state without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-008", "SRC-010" ] } ], "inline_only_rationale": null }, { "id": "sensor-telemetry-source-quality-and-freshness", "name": "Sensor telemetry, source, quality and freshness", "description": "Records observed property, sensor, procedure, unit, result, phenomenon time, quality, latency and access.", "source_refs": [ "SRC-008", "SRC-010" ], "questions": [ { "id": "sensor-telemetry-source-quality-and-freshness-q01", "text": "What exact design and observed values must be recorded for sensor telemetry, source, quality and freshness, with units, tolerance and applicability where relevant?", "kind": "measurement", "answer_data": [ "Sensor telemetry, source, quality and freshness", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "sensor-telemetry-source-quality-and-freshness-q02", "text": "Which source, authority, method and evidence establish sensor telemetry, source, quality and freshness, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "sensor-telemetry-source-quality-and-freshness-q03", "text": "How is sensor telemetry, source, quality and freshness validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "sensor-telemetry-source-quality-and-freshness-record", "name": "Sensor telemetry, source, quality and freshness record", "description": "Structured source-qualified values for sensor telemetry, source, quality and freshness including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008", "SRC-010" ] } ], "artifacts": [ { "id": "sensor-telemetry-source-quality-and-freshness-artifact", "name": "Telemetry observation bundle", "description": "Versioned evidence or exchange artifact supporting sensor telemetry, source, quality and freshness without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-008", "SRC-010" ] } ], "inline_only_rationale": null } ] }, { "id": "condition-damage-fault-and-operability", "name": "Condition, damage, fault and operability", "description": "Current health and readiness evidence.", "source_refs": [ "SRC-004", "SRC-008", "SRC-009", "SRC-010" ], "findings": [ { "id": "condition-integrity-damage-wear-and-contamination", "name": "Condition, integrity, damage, wear and contamination", "description": "Records zone condition, damage geometry, wear, corrosion, contamination, severity and safe-use impact.", "source_refs": [ "SRC-004", "SRC-008", "SRC-009" ], "questions": [ { "id": "condition-integrity-damage-wear-and-contamination-q01", "text": "What exact design and observed values must be recorded for condition, integrity, damage, wear and contamination, with units, tolerance and applicability where relevant?", "kind": "state", "answer_data": [ "Condition, integrity, damage, wear and contamination", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "condition-integrity-damage-wear-and-contamination-q02", "text": "Which source, authority, method and evidence establish condition, integrity, damage, wear and contamination, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "condition-integrity-damage-wear-and-contamination-q03", "text": "How is condition, integrity, damage, wear and contamination validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "condition-integrity-damage-wear-and-contamination-record", "name": "Condition, integrity, damage, wear and contamination record", "description": "Structured source-qualified values for condition, integrity, damage, wear and contamination including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-008", "SRC-009" ] } ], "artifacts": [ { "id": "condition-integrity-damage-wear-and-contamination-artifact", "name": "Vehicle condition assessment", "description": "Versioned evidence or exchange artifact supporting condition, integrity, damage, wear and contamination without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-004", "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "fault-operability-availability-and-degraded-mode", "name": "Fault, operability, availability and degraded mode", "description": "Records faults, diagnostics, operational state, affected capability, workaround and next action.", "source_refs": [ "SRC-004", "SRC-008", "SRC-009", "SRC-010" ], "questions": [ { "id": "fault-operability-availability-and-degraded-mode-q01", "text": "What exact design and observed values must be recorded for fault, operability, availability and degraded mode, with units, tolerance and applicability where relevant?", "kind": "state", "answer_data": [ "Fault, operability, availability and degraded mode", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "fault-operability-availability-and-degraded-mode-q02", "text": "Which source, authority, method and evidence establish fault, operability, availability and degraded mode, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "fault-operability-availability-and-degraded-mode-q03", "text": "How is fault, operability, availability and degraded mode validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "fault-operability-availability-and-degraded-mode-record", "name": "Fault, operability, availability and degraded mode record", "description": "Structured source-qualified values for fault, operability, availability and degraded mode including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-008", "SRC-009", "SRC-010" ] } ], "artifacts": [ { "id": "fault-operability-availability-and-degraded-mode-artifact", "name": "Operability status record", "description": "Versioned evidence or exchange artifact supporting fault, operability, availability and degraded mode without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-004", "SRC-008", "SRC-009", "SRC-010" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "lifecycle-ownership-and-operational-context", "name": "Lifecycle, ownership and operational context", "description": "Connects manufacture, configuration, party roles, service and retirement.", "rationale": "Identity persists through changes of mark, flag, owner, keeper, operator, location and components.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-009", "SRC-010" ], "layers": [ { "id": "manufacture-commissioning-modification-and-retirement", "name": "Manufacture, commissioning, modification and retirement", "description": "Physical lifecycle and configuration succession.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-009" ], "findings": [ { "id": "manufacturer-build-place-date-and-conformity", "name": "Manufacturer, build place, date and conformity", "description": "Records manufacturer, production site, completion date, type reference, initial configuration and conformity evidence.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-009" ], "questions": [ { "id": "manufacturer-build-place-date-and-conformity-q01", "text": "What exact design and observed values must be recorded for manufacturer, build place, date and conformity, with units, tolerance and applicability where relevant?", "kind": "provenance", "answer_data": [ "Manufacturer, build place, date and conformity", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "manufacturer-build-place-date-and-conformity-q02", "text": "Which source, authority, method and evidence establish manufacturer, build place, date and conformity, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "manufacturer-build-place-date-and-conformity-q03", "text": "How is manufacturer, build place, date and conformity validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "manufacturer-build-place-date-and-conformity-record", "name": "Manufacturer, build place, date and conformity record", "description": "Structured source-qualified values for manufacturer, build place, date and conformity including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-009" ] } ], "artifacts": [ { "id": "manufacturer-build-place-date-and-conformity-artifact", "name": "Build and conformity record", "description": "Versioned evidence or exchange artifact supporting manufacturer, build place, date and conformity without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "commissioning-modification-rebuild-and-retirement", "name": "Commissioning, modification, rebuild and retirement", "description": "Records service entry, material changes, conversions, baselines, succession and disposal events.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-009", "SRC-010" ], "questions": [ { "id": "commissioning-modification-rebuild-and-retirement-q01", "text": "What exact design and observed values must be recorded for commissioning, modification, rebuild and retirement, with units, tolerance and applicability where relevant?", "kind": "lifecycle", "answer_data": [ "Commissioning, modification, rebuild and retirement", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "commissioning-modification-rebuild-and-retirement-q02", "text": "Which source, authority, method and evidence establish commissioning, modification, rebuild and retirement, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "commissioning-modification-rebuild-and-retirement-q03", "text": "How is commissioning, modification, rebuild and retirement validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "commissioning-modification-rebuild-and-retirement-record", "name": "Commissioning, modification, rebuild and retirement record", "description": "Structured source-qualified values for commissioning, modification, rebuild and retirement including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-009", "SRC-010" ] } ], "artifacts": [ { "id": "commissioning-modification-rebuild-and-retirement-artifact", "name": "Vehicle lifecycle event log", "description": "Versioned evidence or exchange artifact supporting commissioning, modification, rebuild and retirement without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-009", "SRC-010" ] } ], "inline_only_rationale": null } ] }, { "id": "ownership-custody-registration-and-service", "name": "Ownership, custody, registration and service", "description": "Party roles, authority records and upkeep.", "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-009" ], "findings": [ { "id": "owner-keeper-operator-custodian-and-occupant-role", "name": "Owner, keeper, operator, custodian and occupant role", "description": "Records distinct party roles, authority, purpose, interval, evidence and contested status.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-009" ], "questions": [ { "id": "owner-keeper-operator-custodian-and-occupant-role-q01", "text": "What exact design and observed values must be recorded for owner, keeper, operator, custodian and occupant role, with units, tolerance and applicability where relevant?", "kind": "ownership", "answer_data": [ "Owner, keeper, operator, custodian and occupant role", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "owner-keeper-operator-custodian-and-occupant-role-q02", "text": "Which source, authority, method and evidence establish owner, keeper, operator, custodian and occupant role, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "owner-keeper-operator-custodian-and-occupant-role-q03", "text": "How is owner, keeper, operator, custodian and occupant role validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "owner-keeper-operator-custodian-and-occupant-role-record", "name": "Owner, keeper, operator, custodian and occupant role record", "description": "Structured source-qualified values for owner, keeper, operator, custodian and occupant role including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-009" ] } ], "artifacts": [ { "id": "owner-keeper-operator-custodian-and-occupant-role-artifact", "name": "Vehicle party-role ledger", "description": "Versioned evidence or exchange artifact supporting owner, keeper, operator, custodian and occupant role without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-009" ] } ], "inline_only_rationale": null }, { "id": "registration-title-permit-inspection-maintenance-and-recall", "name": "Registration, title, permit, inspection, maintenance and recall", "description": "References external governed records, issuer, status, validity, restrictions, service and recall applicability.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "questions": [ { "id": "registration-title-permit-inspection-maintenance-and-recall-q01", "text": "What exact design and observed values must be recorded for registration, title, permit, inspection, maintenance and recall, with units, tolerance and applicability where relevant?", "kind": "lifecycle", "answer_data": [ "Registration, title, permit, inspection, maintenance and recall", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "registration-title-permit-inspection-maintenance-and-recall-q02", "text": "Which source, authority, method and evidence establish registration, title, permit, inspection, maintenance and recall, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "registration-title-permit-inspection-maintenance-and-recall-q03", "text": "How is registration, title, permit, inspection, maintenance and recall validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "registration-title-permit-inspection-maintenance-and-recall-record", "name": "Registration, title, permit, inspection, maintenance and recall record", "description": "Structured source-qualified values for registration, title, permit, inspection, maintenance and recall including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "registration-title-permit-inspection-maintenance-and-recall-artifact", "name": "Compliance and service dossier", "description": "Versioned evidence or exchange artifact supporting registration, title, permit, inspection, maintenance and recall without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "safety-compliance-and-interoperability", "name": "Safety, compliance and interoperability", "description": "Governs hazards, evidence, profiles, access, retention and projections.", "rationale": "A multimodal base cannot treat one jurisdiction or mode as universal.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009" ], "layers": [ { "id": "hazards-safety-and-compliance", "name": "Hazards, safety and compliance", "description": "Risk controls and source-qualified approvals.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008" ], "findings": [ { "id": "hazard-operating-risk-emergency-and-safing", "name": "Hazard, operating risk, emergency and safing", "description": "Records collision, fire, energy, stability, environmental and access hazards, controls and safe state.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ], "questions": [ { "id": "hazard-operating-risk-emergency-and-safing-q01", "text": "What exact design and observed values must be recorded for hazard, operating risk, emergency and safing, with units, tolerance and applicability where relevant?", "kind": "security", "answer_data": [ "Hazard, operating risk, emergency and safing", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "hazard-operating-risk-emergency-and-safing-q02", "text": "Which source, authority, method and evidence establish hazard, operating risk, emergency and safing, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "hazard-operating-risk-emergency-and-safing-q03", "text": "How is hazard, operating risk, emergency and safing validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "hazard-operating-risk-emergency-and-safing-record", "name": "Hazard, operating risk, emergency and safing record", "description": "Structured source-qualified values for hazard, operating risk, emergency and safing including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] } ], "artifacts": [ { "id": "hazard-operating-risk-emergency-and-safing-artifact", "name": "Vehicle hazard and safing plan", "description": "Versioned evidence or exchange artifact supporting hazard, operating risk, emergency and safing without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] } ], "inline_only_rationale": null }, { "id": "approval-certificate-rule-conformance-and-exception", "name": "Approval, certificate, rule conformance and exception", "description": "Records authority, rule, approval, certificate, test, exception, condition, validity and decision.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "questions": [ { "id": "approval-certificate-rule-conformance-and-exception-q01", "text": "What exact design and observed values must be recorded for approval, certificate, rule conformance and exception, with units, tolerance and applicability where relevant?", "kind": "validation", "answer_data": [ "Approval, certificate, rule conformance and exception", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "approval-certificate-rule-conformance-and-exception-q02", "text": "Which source, authority, method and evidence establish approval, certificate, rule conformance and exception, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "approval-certificate-rule-conformance-and-exception-q03", "text": "How is approval, certificate, rule conformance and exception validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "approval-certificate-rule-conformance-and-exception-record", "name": "Approval, certificate, rule conformance and exception record", "description": "Structured source-qualified values for approval, certificate, rule conformance and exception including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "approval-certificate-rule-conformance-and-exception-artifact", "name": "Vehicle conformance matrix", "description": "Versioned evidence or exchange artifact supporting approval, certificate, rule conformance and exception without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "mode-profiles-access-provenance-and-projections", "name": "Mode profiles, access, provenance and projections", "description": "Specialization and exchange across registries.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009" ], "findings": [ { "id": "road-rail-maritime-aviation-and-special-mode-profile", "name": "Road, rail, maritime, aviation and special-mode profile", "description": "Declares authoritative classifications, identifiers, measurements, approvals, registries and non-applicable fields.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "questions": [ { "id": "road-rail-maritime-aviation-and-special-mode-profile-q01", "text": "What exact design and observed values must be recorded for road, rail, maritime, aviation and special-mode profile, with units, tolerance and applicability where relevant?", "kind": "interoperability", "answer_data": [ "Road, rail, maritime, aviation and special-mode profile", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "road-rail-maritime-aviation-and-special-mode-profile-q02", "text": "Which source, authority, method and evidence establish road, rail, maritime, aviation and special-mode profile, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "road-rail-maritime-aviation-and-special-mode-profile-q03", "text": "How is road, rail, maritime, aviation and special-mode profile validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "road-rail-maritime-aviation-and-special-mode-profile-record", "name": "Road, rail, maritime, aviation and special-mode profile record", "description": "Structured source-qualified values for road, rail, maritime, aviation and special-mode profile including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "road-rail-maritime-aviation-and-special-mode-profile-artifact", "name": "Mode-specific extension profile", "description": "Versioned evidence or exchange artifact supporting road, rail, maritime, aviation and special-mode profile without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null }, { "id": "access-provenance-retention-and-exchange-projection", "name": "Access, provenance, retention and exchange projection", "description": "Defines field access, sensitive location or owner data, provenance, retention and loss-aware projections.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ], "questions": [ { "id": "access-provenance-retention-and-exchange-projection-q01", "text": "What exact design and observed values must be recorded for access, provenance, retention and exchange projection, with units, tolerance and applicability where relevant?", "kind": "access", "answer_data": [ "Access, provenance, retention and exchange projection", "Design or declared value", "Observed value and unit", "Applicability or not-applicable reason" ] }, { "id": "access-provenance-retention-and-exchange-projection-q02", "text": "Which source, authority, method and evidence establish access, provenance, retention and exchange projection, at what time and with what confidence?", "kind": "evidence", "answer_data": [ "Authority and master-system reference", "Method and evidence", "Phenomenon and record times", "Confidence and uncertainty" ] }, { "id": "access-provenance-retention-and-exchange-projection-q03", "text": "How is access, provenance, retention and exchange projection validated, related and changed without confusing the vehicle with its type, components, parties or events?", "kind": "validation", "answer_data": [ "Validation result", "Typed external references", "Predecessor or successor", "Conflict, exception and retention decision" ] } ], "data_elements": [ { "id": "access-provenance-retention-and-exchange-projection-record", "name": "Access, provenance, retention and exchange projection record", "description": "Structured source-qualified values for access, provenance, retention and exchange projection including authority, units, conditions, time, provenance and uncertainty.", "value_kind": "collection", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ] } ], "artifacts": [ { "id": "access-provenance-retention-and-exchange-projection-artifact", "name": "Vehicle exchange and access pack", "description": "Versioned evidence or exchange artifact supporting access, provenance, retention and exchange projection without replacing its authoritative master record.", "media_or_form": [ "JSON", "YAML", "RDF or CSV when mapped", "Human-readable record" ], "serial": true, "identity_strategy": "Use the authoritative vehicle ID plus immutable assertion or event ID; never use a date, filename, registration mark or hash alone as vehicle identity.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-008", "SRC-009" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-vehicle", "name": "Register vehicle", "description": "Create stable vehicle identity and initial configuration.", "inputs": [ "Authority", "Identifier scheme", "Instance identifiers", "Mode profile" ], "outputs": [ "Vehicle master record", "Validation result" ], "preconditions": [ "Identity authority is resolved" ], "effects": [ "Registers one physical vehicle independently of type and mutable marks" ], "source_refs": [ "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "classify-vehicle", "name": "Classify vehicle", "description": "Bind functional and regulatory categories.", "inputs": [ "Vehicle", "Classification source", "Category" ], "outputs": [ "Classification assertion" ], "preconditions": [ "Profile version is pinned" ], "effects": [ "Adds source-qualified class without universalizing one mode" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "record-physical-specification", "name": "Record physical specification", "description": "Attach measured or declared physical properties.", "inputs": [ "Vehicle", "Property set", "Method", "Conditions" ], "outputs": [ "Physical specification record" ], "preconditions": [ "Units and frame are declared" ], "effects": [ "Preserves design-versus-observation status" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] }, { "id": "configure-installed-system", "name": "Configure installed system", "description": "Record component installation or configuration.", "inputs": [ "Vehicle", "Component", "Position", "Time" ], "outputs": [ "Configuration revision" ], "preconditions": [ "Identities are resolved" ], "effects": [ "Creates a successor configuration" ], "source_refs": [ "SRC-004", "SRC-008", "SRC-009" ] }, { "id": "declare-capability-and-envelope", "name": "Declare capability and envelope", "description": "Record capacity, movement and limits.", "inputs": [ "Vehicle", "Capability", "Conditions", "Evidence" ], "outputs": [ "Capability assertion" ], "preconditions": [ "Design and state are distinguished" ], "effects": [ "Adds prerequisites, limits and hazards" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] }, { "id": "observe-vehicle-state", "name": "Observe vehicle state", "description": "Record recognition, pose, telemetry, condition or fault.", "inputs": [ "Vehicle", "Property", "Observer", "Procedure", "Time" ], "outputs": [ "Observation", "Quality assessment" ], "preconditions": [ "Vehicle match is available" ], "effects": [ "Appends state without overwriting design truth" ], "source_refs": [ "SRC-008", "SRC-009", "SRC-010" ] }, { "id": "assign-party-role", "name": "Assign party role", "description": "Record owner, keeper, operator or custodian role.", "inputs": [ "Vehicle", "Party", "Role", "Authority" ], "outputs": [ "Role assignment" ], "preconditions": [ "Party is resolved" ], "effects": [ "Preserves role distinctions" ], "source_refs": [ "SRC-004", "SRC-005", "SRC-007", "SRC-009" ] }, { "id": "record-lifecycle-event", "name": "Record lifecycle event", "description": "Append manufacture, transfer, modification, service, incident or retirement.", "inputs": [ "Vehicle", "Event type", "Actor", "Evidence" ], "outputs": [ "Lifecycle event", "State reference" ], "preconditions": [ "Authority is known" ], "effects": [ "Preserves immutable history" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-007", "SRC-009", "SRC-010" ] }, { "id": "bind-registration-or-certificate", "name": "Bind registration or certificate", "description": "Reference an external governed record.", "inputs": [ "Vehicle", "External record", "Issuer" ], "outputs": [ "Governed record binding" ], "preconditions": [ "Issuer is resolved" ], "effects": [ "Adds status without replacing identity" ], "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "validate-vehicle-record", "name": "Validate vehicle record", "description": "Check identity, quantities, composition, state and lifecycle.", "inputs": [ "Vehicle record", "Mode profile" ], "outputs": [ "Validation report" ], "preconditions": [ "Pinned rules exist" ], "effects": [ "Reports conflicts without silent repair" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] }, { "id": "assess-operability-and-risk", "name": "Assess operability and risk", "description": "Derive readiness, restrictions and safe actions.", "inputs": [ "Vehicle", "Configuration", "Condition", "Context" ], "outputs": [ "Operability assessment", "Restrictions" ], "preconditions": [ "Fresh evidence exists" ], "effects": [ "Never equates existence with operability" ], "source_refs": [ "SRC-004", "SRC-008", "SRC-009" ] }, { "id": "publish-vehicle-projection", "name": "Publish vehicle projection", "description": "Produce an access-filtered projection.", "inputs": [ "Vehicle version", "Profile", "Access scope" ], "outputs": [ "Projection", "Digest", "Loss report" ], "preconditions": [ "Policy permits disclosure" ], "effects": [ "Exports data without changing identity" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008" ] } ], "composition": [ { "target": "Vehicle Type, Component, System, Sensor and Energy Storage models", "relation": "REFERENCE", "purpose": "Resolve designs and installed whole-part configuration without importing their lifecycle.", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-008" ] }, { "target": "Party, Place, Journey, Movement, Cargo, Registration, Certificate, Maintenance, Incident, Evidence and Provenance models", "relation": "REFERENCE", "purpose": "Connect operational and governance context while retaining external mastership.", "required": false, "source_refs": [ "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-009" ] }, { "target": "UNECE R.E.3 and EU 2018/858", "relation": "ALIGN", "purpose": "Support road-vehicle categories, types, variants, versions, construction and approval profiles.", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "target": "ISO 3779 and NHTSA vPIC", "relation": "ALIGN", "purpose": "Support road-vehicle instance and manufacturer identity while preserving jurisdiction and source limits.", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "target": "IMO, ICAO and European rail vehicle registers", "relation": "ALIGN", "purpose": "Support permanent or registration identifiers and authority-specific lifecycle projections across maritime, aviation and rail modes.", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "target": "SSN and SOSA", "relation": "ALIGN", "purpose": "Support systems, deployments, capabilities, sensors, observations, actuations and operating ranges without collapsing the vehicle into telemetry.", "required": false, "source_refs": [ "SRC-008" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Dimension identity, owner, vehicle steward and namespace", "Vehicle, type, component, party, place, journey, registration, maintenance, evidence and event registries", "Master-system mappings for VIN, IMO, aircraft, rail and local asset identifiers", "Authority, safety, access, retention, telemetry and publication policies" ], "namespace_guidance": "Mint vehicle, configuration revision, observation and lifecycle-event identifiers in the adopting Dimension namespace only when no authoritative external identifier exists; preserve types, components, parties, locations, journeys, registrations, certificates and evidence as typed references.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md", "Dimension-local vehicle, component, registration, maintenance, telemetry and provenance registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by authoritative mode-specific vehicle identifier, issuing authority and scheme, never by registration mark, plate, name, type, timestamp or hash alone.", "Keep instance, type, variant, component, party role, journey, registration, certificate, observation and maintenance event distinct." ], "patch_rules": [ "Additive extensions declare target bundle, layer or finding, mode and jurisdiction profile, source, authority, units, safety and interoperability impact.", "Identity, physical-boundary or relation-semantics changes require an explicit successor, migration map, rollback path and continued resolution of prior records." ], "compatibility_rules": [ "Consumers may ignore unknown additive fields only when vehicle identity, composition, quantities, operating limits, safety, access and lifecycle meaning remain intact.", "Road, rail, maritime, aviation, sensor and registry projections pin source and target versions and disclose transformed, omitted or non-round-trippable values." ] }, "artifact_rules": { "identity_priority": [ "Authoritative mode-specific permanent vehicle identifier from its master registry or manufacturer scheme.", "Governed globally resolvable vehicle IRI qualified by scheme and issuing authority.", "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 manufacture, registration, effective, phenomenon, result, ingestion, service, transfer, incident and retirement times distinct.", "serial_naming_rule": "Name serial artifacts as {vehicle-id}--{artifact-kind}--{assertion-or-event-id}; never use a mutable registration mark, date, filename or hash alone as vehicle identity.", "integrity_rule": "Store digest, media type, byte length, issuer, source and profile versions, effective time, provenance, assurance, licence and access marking for every retained serial artifact." }, "policies": [ "The adopting Dimension declares who may register, classify, inspect, configure, operate, maintain, certify, transfer, disclose and retire vehicle records.", "Every quantity states unit, tolerance, method, condition, source and whether it is design, declared, observed, estimated or derived.", "Agents never infer ownership from custody, registration from an identifier, compliance from a certificate reference, or operability from vehicle existence.", "Vehicle types, components, parties, journeys, shipments, registrations, titles, permits, certificates, maintenance work and telemetry remain in their owning systems and are referenced.", "Automated agents may read, validate, reconcile and append low-risk observations within policy, while control actions, safety overrides, ownership changes, restricted tracking disclosure and destructive retirement require accountable authority." ], "crud": { "read": [ "Resolve active Dimension, vehicle identity, mode profile, current configuration, requested valid time, evidence freshness and access scope; return the minimum permitted projection." ], "create": [ "Create stable instance identity, source authority, class, physical boundary, initial configuration, provenance and explicit unknowns before operational use." ], "update": [ "Append an observation, event or successor configuration with actor, authority, reason, RFC 3339 time, evidence and before-and-after validation; never overwrite a cited fact or event." ], "delete": [ "Apply registration, safety, incident, legal-hold and retention policy; prefer retirement or tombstone, preserve identity and history, and never cascade into referenced components, parties, journeys, certificates or evidence." ] }, "roles": [ { "name": "Dimension owner", "responsibilities": [ "Own namespace, mastership, autonomy, access, retention and federation rules." ] }, { "name": "Vehicle owner or asset steward", "responsibilities": [ "Own intended use, asset policy, disposition and accountability." ] }, { "name": "Manufacturer or integrator", "responsibilities": [ "Own build identity, type references, configuration and conformity evidence." ] }, { "name": "Registrar or approval authority", "responsibilities": [ "Own registration, number allocation, approval, restriction and certificate lifecycle." ] }, { "name": "Keeper, operator or custodian", "responsibilities": [ "Own possession, operation, condition reporting and operational compliance within role." ] }, { "name": "Inspector or maintainer", "responsibilities": [ "Own inspections, diagnostics, service work and configuration changes." ] }, { "name": "Safety and compliance authority", "responsibilities": [ "Govern hazards, limits, permits, incidents, recalls and emergency controls." ] }, { "name": "Data and telemetry steward", "responsibilities": [ "Own sensor mappings, observation quality, sensitive tracking, provenance and retention." ] } ], "access": { "default_rule": "Deny mutation, control and disclosure of precise live location, occupants, owner data or security-sensitive configuration unless active Dimension, role, purpose and field policy grant it; expose the minimum necessary projection.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Emergency safety access must be purpose-bound, time-limited, attributable, independently reviewed and unable to erase original telemetry, incidents, configuration or audit evidence." ], "audit_requirements": [ "Log actor, agent, role, purpose, vehicle and configuration identity, action, policy and mode profile, RFC 3339 timestamp with offset, affected scope, requested and effective authority, evidence and outcome." ] }, "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, vehicle mastership, safety, control, location-privacy, access, retention and federation policies.", "Read this model AGENTS.md, pinned spec.yaml and required type, component, party, place, journey, registration, certificate, maintenance, evidence, observation and incident model instructions before mutation or action." ] } }, "coverage": { "claim": "A source-grounded reviewable draft of an individual multimodal Vehicle across current road, rail, maritime and aviation identity regimes, physical structure, propulsion, capacity, affordances, recognition, observed state, lifecycle, safety, provenance and exchange, without a claim of universal vehicle-class, jurisdiction, certified crosswalk or autonomous-system completeness.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Permanent identifiers, mutable registrations, serials, fleet labels and aliases are separated." }, { "dimension": "classification and definition", "status": "covered", "notes": "Mode, powered status, purpose, regulatory class, type and instance boundaries are explicit." }, { "dimension": "direct physical properties", "status": "covered", "notes": "Geometry, mass, materials, construction, systems, energy and condition include units and method." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Appearance, marks, signals, pose, telemetry, method, time, uncertainty and confusing matches are represented." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Carriage, towing, movement, control, boarding, loading and service include prerequisites, limits and hazards." }, { "dimension": "composition", "status": "covered", "notes": "Structure, propulsion, energy, controls, sensors, safety systems and payload interfaces use typed whole-part references." }, { "dimension": "lifecycle", "status": "covered", "notes": "Manufacture, commissioning, configuration, registration, transfer, modification, service, incident and retirement preserve history." }, { "dimension": "relationships", "status": "covered", "notes": "Types, components, parties, places, journeys, cargo, registrations, certificates, observations and events remain distinct references." }, { "dimension": "temporal", "status": "covered", "notes": "Manufacture, effective, registration, phenomenon, result, ingestion, service, incident and retirement times remain distinct." }, { "dimension": "spatial", "status": "covered", "notes": "Coordinate frame, geometry, pose, location, route or network, altitude or depth and uncertainty are explicit." }, { "dimension": "provenance", "status": "covered", "notes": "Manufacturer, issuer, observer, method, source, revision, event and projection provenance are retained." }, { "dimension": "ownership", "status": "covered", "notes": "Owner, keeper, operator, custodian, occupant, maintainer and authority roles are separated." }, { "dimension": "validation and quality", "status": "covered", "notes": "Identity, unit, composition, cycle, range, safety, profile, observation and lineage checks are explicit." }, { "dimension": "access", "status": "covered", "notes": "Precise location, occupants, ownership, security configuration and telemetry use purpose-bound field access." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Retirement and tombstones preserve identity, safety, incident, maintenance and compliance history without cascading." }, { "dimension": "interoperability", "status": "covered", "notes": "Road, rail, maritime, aviation, sensor and registry profiles pin source versions and disclose loss." } ], "known_omissions": [ "Autonomous driving, remote operation, unmanned aircraft, spacecraft, bicycles, micro-mobility and specialized industrial vehicles require detailed profiles.", "Vehicle type, component, party, journey, shipment, registration, certificate, maintenance, incident and telemetry lifecycles remain in neighboring masters.", "Certified per-mode field crosswalks, unit profiles, conformance fixtures, safety cases and jurisdiction-specific retention rules remain future work." ], "conflicts": [ "VIN, IMO number, aircraft registration and rail vehicle number differ in permanence, issuer, format, applicability and relationship to mutable marks.", "Road categories, rail registers, maritime schemes and aviation classifications are mode-specific and cannot be combined into one universal legal class.", "Design capability and approval evidence do not prove current condition, operability, authority to operate or suitability for a particular task." ], "regional_assumptions": [ "EU road and rail rules are authoritative only for their legal scope and are included as profiles, not universal law.", "UNECE vehicle construction vocabulary is road-focused and does not define maritime, aviation or all special modes.", "IMO and ICAO identity schemes apply to specified classes and do not replace national registers or ownership records." ], "adversarial_checks": [ "Reject a vehicle identity based only on a mutable plate, registration mark, fleet label, name or current owner.", "Reject quantities without unit, method, condition, source and design-versus-observation status.", "Reject operability or compliance inferred from a type, registration or certificate reference without fresh condition and scope evidence.", "Reject ownership inferred from keeper, operator, custodian, occupant or registration roles.", "Reject automated control or safety-critical action that exceeds active Dimension authority, operating envelope or verified vehicle state." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "entity", "status": "accepted as an individual physical vehicle", "rationale": "The model represents one physical conveyance or mobile machine. Vehicle types, models, variants, components, parties, journeys, cargo, registrations, approvals, certificates, maintenance work and telemetry observations remain distinct linked objects or records." }, "decisions": [ { "concept": "Multimodal base model", "disposition": "accepted with explicit mode profiles", "rationale": "Road, rail, maritime and aviation vehicles share instance, physical-system, capability, state and lifecycle concerns, while each mode retains its own identifiers, categories, authorities and conformance rules." }, { "concept": "Vehicle instance identity", "disposition": "accepted as scheme-qualified and authority-qualified", "rationale": "VIN, IMO number, aircraft registration, European vehicle number and local asset identifiers differ in scope and permanence, so no mutable plate, mark, name, owner, timestamp or hash is universal identity." }, { "concept": "Vehicle and vehicle type", "disposition": "accepted as separate linked identities", "rationale": "Type, model, variant and version describe shared design and approval assertions, while the Vehicle record describes one physical instance and the configuration that applied at a stated time." }, { "concept": "Installed components and systems", "disposition": "accepted as versioned external parts", "rationale": "Engines, batteries, sensors, control systems and assemblies can have independent identity and lifecycle, so installation records establish whole-part configuration without importing their master records." }, { "concept": "Design, declared and observed values", "disposition": "accepted as distinct assertions", "rationale": "Every quantity records unit, tolerance, condition, method, time and source and states whether it is design, declared, measured, estimated or derived." }, { "concept": "Technical capability, current operability and authority", "disposition": "accepted as distinct states", "rationale": "A design capability, approval or certificate does not prove that the current configuration is operable, safe, permitted or controlled by the requesting agent." }, { "concept": "Owner, keeper, operator, custodian and occupant", "disposition": "accepted as time-bound party roles", "rationale": "Possession, operation, custody and presence never establish legal ownership, and none of these roles determines vehicle identity." }, { "concept": "Registration, approval, certificate and maintenance", "disposition": "accepted as external governed lifecycles", "rationale": "Each record retains its issuer, scope, validity, status, evidence and lifecycle and references the vehicle rather than becoming an intrinsic vehicle property." }, { "concept": "Direct physical properties and recognition", "disposition": "accepted as first-class coverage", "rationale": "Geometry, dimensions, mass, balance, materials, construction, appearance, markings, signals and distinguishing features support machine recognition and physical reasoning in addition to contextual history." }, { "concept": "Observations, telemetry and provenance", "disposition": "accepted as source-qualified event records", "rationale": "Sensors, procedures, phenomenon time, result time, quality, freshness and provenance remain explicit so current state is not confused with specification or stale evidence." }, { "concept": "Safety-sensitive actions", "disposition": "accepted with fail-closed authorization", "rationale": "Control, override, tracking disclosure, ownership change and destructive retirement require active Dimension policy, accountable authority, operating-envelope checks and auditable evidence." }, { "concept": "Approved registry composition", "disposition": "held pending relation governance", "rationale": "The approved relation ledger contains no outgoing WM-OBJ-007 rows, so proposed sibling composition remains draft." } ], "publicationHolds": [ "Claude and Grok timed out during their bounded attempts, so independent external review is absent and explicitly waived for this published reviewable draft.", "The approved relationship ledger contains no outgoing relation rows for WM-OBJ-007, so proposed links to vehicle type, component, system, sensor, party, place, journey, cargo, registration, certificate, maintenance, incident, evidence and provenance models remain draft.", "Autonomous, remote, unmanned, space, bicycle, micro-mobility and special industrial vehicle profiles require specialist review.", "Certified per-mode field crosswalks, unit profiles, conformance fixtures, safety cases and jurisdiction profiles remain unverified.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Develop specialist road, rail, maritime, aviation, space, industrial, bicycle, micro-mobility, autonomous and remotely operated vehicle recipes.", "Approve sibling model identifiers and relation cardinalities for types, components, systems, sensors, energy stores, parties, places, journeys, cargo, registrations, certificates, maintenance, incidents, evidence and provenance.", "Create deterministic unit, configuration, identity, state, access, deletion, safety and projection fixtures for each supported transport mode.", "Validate jurisdiction-specific registration, approval, inspection, tracking, retention and control-authority policies with domain experts." ] }, "statistics": { "sources": 10, "bundles": 7, "layers": 16, "findings": 32, "questions": 96, "artifacts": 32, "functions": 12 } }