← Back to catalogue
Published

Vehicle

vr.wm-obj-007 · wm-obj-007-vehicle

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.

World Models Physical world and living systems PHY.OBJ.VEH
Bundle → Layer → Finding → QuestionsClassifiersWhat it isWhy it existsDistinguishing featuresWhat robots and AI may and may not doMoral aspectsOwnersLinks to other meta-modelsIdentity and identifiersDirect propertiesRecognitionCapabilities and actionsHazards and failure modesStandards and interfacesContext of useSources

Bundle → Layer → Finding → Questions Filled

7 bundles · 16 layers · 32 findings · 96 questions

Identity, classification and registry Identifies the vehicle independently of its type, name, operator and registration.

Vehicle master identity

Stable instance identity, authority and aliases.

Authoritative instance identifier

Records the master identifier, scheme, issuing authority, validation, assignment time and prior identifiers.

  1. What exact design and observed values must be recorded for authoritative instance identifier, with units, tolerance and applicability where relevant? identity
  2. Which source, authority, method and evidence establish authoritative instance identifier, at what time and with what confidence? evidence
  3. How is authoritative instance identifier validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Registration mark, serial and display identity

Records mutable marks, manufacturer serial, fleet number, plate, name and marking location.

  1. What exact design and observed values must be recorded for registration mark, serial and display identity, with units, tolerance and applicability where relevant? identity
  2. Which source, authority, method and evidence establish registration mark, serial and display identity, at what time and with what confidence? evidence
  3. How is registration mark, serial and display identity validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Mode, class, purpose and boundary

Functional and regulatory classification with explicit applicability.

Transport mode, vehicle category and role

Classifies road, rail, water, air or other mode, powered status, carriage purpose and source vocabulary.

  1. What exact design and observed values must be recorded for transport mode, vehicle category and role, with units, tolerance and applicability where relevant? classification
  2. Which source, authority, method and evidence establish transport mode, vehicle category and role, at what time and with what confidence? evidence
  3. How is transport mode, vehicle category and role validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Instance, type, component, cargo and event boundary

Separates the vehicle from design type, component, carried subject, journey, permit and maintenance event.

  1. What exact design and observed values must be recorded for instance, type, component, cargo and event boundary, with units, tolerance and applicability where relevant? relationship
  2. Which source, authority, method and evidence establish instance, type, component, cargo and event boundary, at what time and with what confidence? evidence
  3. How is instance, type, component, cargo and event boundary validated, related and changed without confusing the vehicle with its type, components, parties or events? validation
Physical form, composition and construction Describes geometry, quantities, materials, assemblies and installed systems.

Geometry, dimensions, mass and pose

Measured or declared physical extent and spatial configuration.

Geometry, dimensions, volume and clearance

Records coordinate frame, shape, length, width, height, draft, envelope, clearances, units and tolerance.

  1. What exact design and observed values must be recorded for geometry, dimensions, volume and clearance, with units, tolerance and applicability where relevant? measurement
  2. Which source, authority, method and evidence establish geometry, dimensions, volume and clearance, at what time and with what confidence? evidence
  3. How is geometry, dimensions, volume and clearance validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Mass, balance, centre of gravity and pose

Records empty, operating, payload and maximum masses, loads, balance, centre of gravity and orientation.

  1. What exact design and observed values must be recorded for mass, balance, centre of gravity and pose, with units, tolerance and applicability where relevant? measurement
  2. Which source, authority, method and evidence establish mass, balance, centre of gravity and pose, at what time and with what confidence? evidence
  3. How is mass, balance, centre of gravity and pose validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Structure, materials and assemblies

Body and load-bearing construction across modes.

Body, chassis, hull, airframe and running gear

References load-bearing structure, body, hull, airframe, bogies, axles, landing gear or equivalent assemblies.

  1. What exact design and observed values must be recorded for body, chassis, hull, airframe and running gear, with units, tolerance and applicability where relevant? composition
  2. Which source, authority, method and evidence establish body, chassis, hull, airframe and running gear, at what time and with what confidence? evidence
  3. How is body, chassis, hull, airframe and running gear validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Materials, coatings, joints and integrity

Records materials, construction, coatings, critical joints, corrosion or fatigue zones, hardness and fragility.

  1. What exact design and observed values must be recorded for materials, coatings, joints and integrity, with units, tolerance and applicability where relevant? composition
  2. Which source, authority, method and evidence establish materials, coatings, joints and integrity, at what time and with what confidence? evidence
  3. How is materials, coatings, joints and integrity validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Installed systems and payload interface

Whole-part configuration and carriage interfaces.

Installed subsystems, components and configuration

References propulsion, energy, control, navigation, braking, communication, safety, sensor and actuator assemblies.

  1. What exact design and observed values must be recorded for installed subsystems, components and configuration, with units, tolerance and applicability where relevant? composition
  2. Which source, authority, method and evidence establish installed subsystems, components and configuration, at what time and with what confidence? evidence
  3. How is installed subsystems, components and configuration validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Occupant, cargo, coupling and loading interface

Describes seats, holds, doors, ramps, attachment points, couplers, restraints and loading constraints.

  1. What exact design and observed values must be recorded for occupant, cargo, coupling and loading interface, with units, tolerance and applicability where relevant? composition
  2. Which source, authority, method and evidence establish occupant, cargo, coupling and loading interface, at what time and with what confidence? evidence
  3. How is occupant, cargo, coupling and loading interface validated, related and changed without confusing the vehicle with its type, components, parties or events? validation
Propulsion, energy and environmental performance Represents movement generation, energy storage and condition-dependent performance.

Propulsion, drive and control

Prime movers, transmission and movement controls.

Prime mover, propulsor and drivetrain

References engines, motors, sails, propellers, rotors, wheels, tracks, transmissions and thrust paths.

  1. What exact design and observed values must be recorded for prime mover, propulsor and drivetrain, with units, tolerance and applicability where relevant? composition
  2. Which source, authority, method and evidence establish prime mover, propulsor and drivetrain, at what time and with what confidence? evidence
  3. How is prime mover, propulsor and drivetrain validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Steering, braking, stability and control authority

Records steering, guidance, stopping, stability, manual, remote or automated authority and degraded behavior.

  1. What exact design and observed values must be recorded for steering, braking, stability and control authority, with units, tolerance and applicability where relevant? state
  2. Which source, authority, method and evidence establish steering, braking, stability and control authority, at what time and with what confidence? evidence
  3. How is steering, braking, stability and control authority validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Energy, consumption, emissions and range

Energy storage, replenishment and performance.

Fuel, battery, energy storage and replenishment

Records energy stores, capacity, chemistry or carrier, connectors, replenishment limits and observed state.

  1. What exact design and observed values must be recorded for fuel, battery, energy storage and replenishment, with units, tolerance and applicability where relevant? measurement
  2. Which source, authority, method and evidence establish fuel, battery, energy storage and replenishment, at what time and with what confidence? evidence
  3. How is fuel, battery, energy storage and replenishment validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Consumption, emissions, efficiency and range

Records declared and observed consumption, emissions, efficiency, endurance and range with conditions.

  1. What exact design and observed values must be recorded for consumption, emissions, efficiency and range, with units, tolerance and applicability where relevant? measurement
  2. Which source, authority, method and evidence establish consumption, emissions, efficiency and range, at what time and with what confidence? evidence
  3. How is consumption, emissions, efficiency and range validated, related and changed without confusing the vehicle with its type, components, parties or events? validation
Capacity, capabilities and affordances Defines what the vehicle can carry or do and where it can operate.

Capacity and load envelope

Occupant, cargo, towing and distributed-load limits.

Occupant, cargo and volume capacity

Records seating, standing, berth, accessibility, mass, volume and special-cargo capacity.

  1. What exact design and observed values must be recorded for occupant, cargo and volume capacity, with units, tolerance and applicability where relevant? measurement
  2. Which source, authority, method and evidence establish occupant, cargo and volume capacity, at what time and with what confidence? evidence
  3. How is occupant, cargo and volume capacity validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Towing, coupling, axle and structural load limits

Records tow, coupling, axle, deck, floor, wing or structural load limits and compatibility requirements.

  1. What exact design and observed values must be recorded for towing, coupling, axle and structural load limits, with units, tolerance and applicability where relevant? constraint
  2. Which source, authority, method and evidence establish towing, coupling, axle and structural load limits, at what time and with what confidence? evidence
  3. How is towing, coupling, axle and structural load limits validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Mobility, operating envelope and interaction

Movement performance, allowed conditions and interfaces.

Speed, manoeuvre, terrain, medium and weather envelope

Records speed, acceleration, grade, turning, depth, altitude, route infrastructure, terrain and weather limits.

  1. What exact design and observed values must be recorded for speed, manoeuvre, terrain, medium and weather envelope, with units, tolerance and applicability where relevant? constraint
  2. Which source, authority, method and evidence establish speed, manoeuvre, terrain, medium and weather envelope, at what time and with what confidence? evidence
  3. How is speed, manoeuvre, terrain, medium and weather envelope validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Boarding, loading, driving, command and service affordances

Describes actions, required interfaces, tools, permissions, effects, reversibility, hazards and failure modes.

  1. What exact design and observed values must be recorded for boarding, loading, driving, command and service affordances, with units, tolerance and applicability where relevant? process
  2. Which source, authority, method and evidence establish boarding, loading, driving, command and service affordances, at what time and with what confidence? evidence
  3. How is boarding, loading, driving, command and service affordances validated, related and changed without confusing the vehicle with its type, components, parties or events? validation
Recognition, observation and operational state Supports real-world identification and time-bound state.

Appearance, markings and recognition

Visual, electronic and machine-readable identity signals.

Colour, shape, livery, markings and distinguishing features

Records observed colour, shape, livery, damage, decals, plates and distinguishing features.

  1. What exact design and observed values must be recorded for colour, shape, livery, markings and distinguishing features, with units, tolerance and applicability where relevant? classification
  2. Which source, authority, method and evidence establish colour, shape, livery, markings and distinguishing features, at what time and with what confidence? evidence
  3. How is colour, shape, livery, markings and distinguishing features validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Electronic identifier, signal and recognition confidence

Records transponder, beacon, tag or radio observations, sensor, position, match candidates and spoofing risk.

  1. What exact design and observed values must be recorded for electronic identifier, signal and recognition confidence, with units, tolerance and applicability where relevant? security
  2. Which source, authority, method and evidence establish electronic identifier, signal and recognition confidence, at what time and with what confidence? evidence
  3. How is electronic identifier, signal and recognition confidence validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Location, motion and telemetry

Time-bound state observations.

Position, orientation, velocity and route state

Records coordinate reference, position, altitude or depth, heading, attitude, speed, route and uncertainty.

  1. What exact design and observed values must be recorded for position, orientation, velocity and route state, with units, tolerance and applicability where relevant? spatial
  2. Which source, authority, method and evidence establish position, orientation, velocity and route state, at what time and with what confidence? evidence
  3. How is position, orientation, velocity and route state validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Sensor telemetry, source, quality and freshness

Records observed property, sensor, procedure, unit, result, phenomenon time, quality, latency and access.

  1. What exact design and observed values must be recorded for sensor telemetry, source, quality and freshness, with units, tolerance and applicability where relevant? measurement
  2. Which source, authority, method and evidence establish sensor telemetry, source, quality and freshness, at what time and with what confidence? evidence
  3. How is sensor telemetry, source, quality and freshness validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Condition, damage, fault and operability

Current health and readiness evidence.

Condition, integrity, damage, wear and contamination

Records zone condition, damage geometry, wear, corrosion, contamination, severity and safe-use impact.

  1. What exact design and observed values must be recorded for condition, integrity, damage, wear and contamination, with units, tolerance and applicability where relevant? state
  2. Which source, authority, method and evidence establish condition, integrity, damage, wear and contamination, at what time and with what confidence? evidence
  3. How is condition, integrity, damage, wear and contamination validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Fault, operability, availability and degraded mode

Records faults, diagnostics, operational state, affected capability, workaround and next action.

  1. What exact design and observed values must be recorded for fault, operability, availability and degraded mode, with units, tolerance and applicability where relevant? state
  2. Which source, authority, method and evidence establish fault, operability, availability and degraded mode, at what time and with what confidence? evidence
  3. How is fault, operability, availability and degraded mode validated, related and changed without confusing the vehicle with its type, components, parties or events? validation
Lifecycle, ownership and operational context Connects manufacture, configuration, party roles, service and retirement.

Manufacture, commissioning, modification and retirement

Physical lifecycle and configuration succession.

Manufacturer, build place, date and conformity

Records manufacturer, production site, completion date, type reference, initial configuration and conformity evidence.

  1. What exact design and observed values must be recorded for manufacturer, build place, date and conformity, with units, tolerance and applicability where relevant? provenance
  2. Which source, authority, method and evidence establish manufacturer, build place, date and conformity, at what time and with what confidence? evidence
  3. How is manufacturer, build place, date and conformity validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Commissioning, modification, rebuild and retirement

Records service entry, material changes, conversions, baselines, succession and disposal events.

  1. What exact design and observed values must be recorded for commissioning, modification, rebuild and retirement, with units, tolerance and applicability where relevant? lifecycle
  2. Which source, authority, method and evidence establish commissioning, modification, rebuild and retirement, at what time and with what confidence? evidence
  3. How is commissioning, modification, rebuild and retirement validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Ownership, custody, registration and service

Party roles, authority records and upkeep.

Owner, keeper, operator, custodian and occupant role

Records distinct party roles, authority, purpose, interval, evidence and contested status.

  1. What exact design and observed values must be recorded for owner, keeper, operator, custodian and occupant role, with units, tolerance and applicability where relevant? ownership
  2. Which source, authority, method and evidence establish owner, keeper, operator, custodian and occupant role, at what time and with what confidence? evidence
  3. How is owner, keeper, operator, custodian and occupant role validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Registration, title, permit, inspection, maintenance and recall

References external governed records, issuer, status, validity, restrictions, service and recall applicability.

  1. What exact design and observed values must be recorded for registration, title, permit, inspection, maintenance and recall, with units, tolerance and applicability where relevant? lifecycle
  2. Which source, authority, method and evidence establish registration, title, permit, inspection, maintenance and recall, at what time and with what confidence? evidence
  3. How is registration, title, permit, inspection, maintenance and recall validated, related and changed without confusing the vehicle with its type, components, parties or events? validation
Safety, compliance and interoperability Governs hazards, evidence, profiles, access, retention and projections.

Hazards, safety and compliance

Risk controls and source-qualified approvals.

Hazard, operating risk, emergency and safing

Records collision, fire, energy, stability, environmental and access hazards, controls and safe state.

  1. What exact design and observed values must be recorded for hazard, operating risk, emergency and safing, with units, tolerance and applicability where relevant? security
  2. Which source, authority, method and evidence establish hazard, operating risk, emergency and safing, at what time and with what confidence? evidence
  3. How is hazard, operating risk, emergency and safing validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Approval, certificate, rule conformance and exception

Records authority, rule, approval, certificate, test, exception, condition, validity and decision.

  1. What exact design and observed values must be recorded for approval, certificate, rule conformance and exception, with units, tolerance and applicability where relevant? validation
  2. Which source, authority, method and evidence establish approval, certificate, rule conformance and exception, at what time and with what confidence? evidence
  3. How is approval, certificate, rule conformance and exception validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Mode profiles, access, provenance and projections

Specialization and exchange across registries.

Road, rail, maritime, aviation and special-mode profile

Declares authoritative classifications, identifiers, measurements, approvals, registries and non-applicable fields.

  1. 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? interoperability
  2. Which source, authority, method and evidence establish road, rail, maritime, aviation and special-mode profile, at what time and with what confidence? evidence
  3. 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? validation

Access, provenance, retention and exchange projection

Defines field access, sensitive location or owner data, provenance, retention and loss-aware projections.

  1. What exact design and observed values must be recorded for access, provenance, retention and exchange projection, with units, tolerance and applicability where relevant? access
  2. Which source, authority, method and evidence establish access, provenance, retention and exchange projection, at what time and with what confidence? evidence
  3. How is access, provenance, retention and exchange projection validated, related and changed without confusing the vehicle with its type, components, parties or events? validation

Classifiers Filled

Family
World Models
Category
Physical world and living systems
Entry kind
entity
Navigation path
NAV.PHY.OBJ.VEH
Domain
PHY.OBJ.VEH
Industry
Cross-industry
Tags
vehiclephy.obj.veh
Also called
M7

What it is Filled

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

Why it exists Filled

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.

Distinguishing features Filled

  • A specific vehicle instance, not its type, model or variant.
  • Holds physical composition, capacities and observed state across road, rail, water and air modes.
  • Registration, approval and maintenance are referenced records, not part of the instance.
  • Separate from the journey or shipment it performs.

What robots and AI may and may not do Filled

Must not

  • Operate, unlock or control a vehicle without explicit authorization.
  • Exceed rated capacities or mass limits in plans.
  • Track or disclose vehicle location in ways that reveal a person's movements without basis.
  • Alter odometer, identification or safety configuration records.
  • Assume a vehicle is roadworthy from its record alone.

Only with a human decision

  • Taking control of a vehicle in operation.
  • Declaring a vehicle unsafe or taking it out of service.
  • Changes of keeper or ownership.

May

  • Read vehicle identity, specifications and observed state from authorized sources.
  • Record observations and telemetry with time and source.
  • Report defects and recall matches to the responsible party.
  • Check capacity before planning loads or passengers.

Moral aspects Filled

  • Vehicles are a major cause of injury and death, so safety data must be accurate.
  • Location and driving data reveal personal life and must be protected.
  • Emissions and noise affect public health.

Who is affected

  • Drivers, passengers and crew
  • Pedestrians and other road users
  • Owners, keepers and operators

Owners Filled

Steward

Dimension identity, owner, vehicle steward and namespace

Roles

Dimension owner
Own namespace, mastership, autonomy, access, retention and federation rules.
Vehicle owner or asset steward
Own intended use, asset policy, disposition and accountability.
Manufacturer or integrator
Own build identity, type references, configuration and conformity evidence.
Registrar or approval authority
Own registration, number allocation, approval, restriction and certificate lifecycle.
Keeper, operator or custodian
Own possession, operation, condition reporting and operational compliance within role.
Inspector or maintainer
Own inspections, diagnostics, service work and configuration changes.
Safety and compliance authority
Govern hazards, limits, permits, incidents, recalls and emergency controls.
Data and telemetry steward
Own sensor mappings, observation quality, sensitive tracking, provenance and retention.

Links to other meta-models Filled

references

  • Vehicle Type, Component, System, Sensor and Energy Storage models - Resolve designs and installed whole-part configuration without importing their lifecycle.
  • Party, Place, Journey, Movement, Cargo, Registration, Certificate, Maintenance, Incident, Evidence and Provenance models - Connect operational and governance context while retaining external mastership.

aligned

  • UNECE R.E.3 and EU 2018/858 - Support road-vehicle categories, types, variants, versions, construction and approval profiles.
  • ISO 3779 and NHTSA vPIC - Support road-vehicle instance and manufacturer identity while preserving jurisdiction and source limits.
  • IMO, ICAO and European rail vehicle registers - Support permanent or registration identifiers and authority-specific lifecycle projections across maritime, aviation and rail modes.
  • SSN and SOSA - Support systems, deployments, capabilities, sensors, observations, actuations and operating ranges without collapsing the vehicle into telemetry.

neighbor

  • Vehicle Type, Model, Variant and Version - Design and regulatory classes define shared properties and approvals; this model represents one physical instance and records which class applied when.
  • Component and System - Engines, batteries, sensors, controls and structural assemblies have separate identity and lifecycle and are linked through versioned installation configuration.
  • Party and Role - Owner, keeper, operator, custodian, occupant, manufacturer and maintainer are separate parties and time-bound roles, not attributes that determine vehicle identity.
  • Journey, Movement, Shipment and Cargo - The vehicle provides carriage capability and may participate in movements; trip plan, execution, cargo and custody histories remain external events and objects.
  • Registration, Approval, Certificate and Maintenance - These governed records and processes reference the vehicle but retain their own issuer, scope, validity, status and lifecycle.
  • Sensor Observation and Telemetry - The vehicle is the feature of interest or platform; sensors, procedures, observations and results remain event records with phenomenon and result time.

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • 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.

Direct properties required Filled

  • Length, width and height in metres, measured unladen.
  • Unladen mass and gross vehicle mass in kilograms.
  • Speed in kilometres per hour or knots as appropriate to the mode.
  • Energy level as fuel volume in litres or battery state of charge in percent.
  • Tyre pressure in kilopascals, measured cold.
  • Odometer reading in kilometres, with date.

Recognition required Filled

  • A vehicle is recognised by registration plate or marking, VIN or hull number, shape, colour and livery.
  • It is confused with similar vehicles of the same model, with trailers and with cloned plates.

Capabilities and actions required Filled

  • Register vehicle: Create stable vehicle identity and initial configuration.
  • Classify vehicle: Bind functional and regulatory categories.
  • Record physical specification: Attach measured or declared physical properties.
  • Configure installed system: Record component installation or configuration.
  • Declare capability and envelope: Record capacity, movement and limits.
  • Observe vehicle state: Record recognition, pose, telemetry, condition or fault.
  • Assign party role: Record owner, keeper, operator or custodian role.
  • Record lifecycle event: Append manufacture, transfer, modification, service, incident or retirement.
  • Bind registration or certificate: Reference an external governed record.
  • Validate vehicle record: Check identity, quantities, composition, state and lifecycle.
  • Assess operability and risk: Derive readiness, restrictions and safe actions.
  • Publish vehicle projection: Produce an access-filtered projection.

Hazards and failure modes required Filled

  • Collision and run-over injuries.
  • Fire, especially of fuel or traction batteries.
  • Unexpected movement during loading or maintenance.
  • Remote takeover through connected systems.

Standards and interfaces required Filled

  • ISO 15118 for electric vehicle charging communication.
  • SAE J3016 driving automation levels.
  • ISO 21434 road vehicle cybersecurity engineering.
  • UN Regulation No. 155 cybersecurity management.

Context of use required Filled

  • 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.

Sources Filled

  1. Consolidated Resolution on the Construction of Vehicles (R.E.3) - United Nations Economic Commission for Europe
  2. ISO 3779:2009 Road vehicles, Vehicle identification number - International Organization for Standardization
  3. Vehicle Manufacturers and vPIC - National Highway Traffic Safety Administration
  4. Regulation (EU) 2018/858 - European Union
  5. IMO identification number schemes - International Maritime Organization
  6. Aircraft Nationality and Registration Marks - International Civil Aviation Organization
  7. European Vehicle Register - European Union Agency for Railways
  8. Semantic Sensor Network Ontology - World Wide Web Consortium and Open Geospatial Consortium
  9. PROV-O: The PROV Ontology - World Wide Web Consortium
  10. RFC 3339: Date and Time on the Internet: Timestamps - Internet Engineering Task Force

Open questions

  • 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.
  • 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.

Machine files

Card as JSON Specification AGENTS.md Source Card backlog vercy.card/1

Provenance

world-models research · reviewable-draft

Built from: models/wm-obj-007-vehicle/spec.yaml, ver-cy/world-models/card-supplements/wm-obj-007-vehicle.json