How to read this specification
Sections 1–3 define the open-world architecture. Sections 4–16 cover movement, control, utility, parts, configuration, lifecycle, measurements, domains, packs, implementation and invariants. Sections 17–24 deepen semantics, identity, mechanism, control,…
Sections 1–3 define the open-world architecture. Sections 4–16 cover movement, control, utility, parts, configuration, lifecycle, measurements, domains, packs, implementation and invariants. Sections 17–24 deepen semantics, identity, mechanism, control, lifecycle, telemetry, vehicle-native agents and governance. Sections 25–44 define exact records, ledgers, runtime, schemas, math, telemetry, physics, safety, identity, markets, APIs and operations. Sections 45–54 add executable institutions, casework, title, insurance/repair, moderation, youth protection, management teams, tax, incident response and market integrity. Section 55 and Appendices N–Q define the v1.4 corrective profiles, migration, immutable release bundle and agent contract.
| Part | Purpose |
|---|---|
| 1–3 Substrate | Admission, durable identity, facets, type recipes, vocabulary governance |
| 4 Movement physics | Support, energy, conversion, force, interface, steering, stopping and stability |
| 5 Control | Human, remote, assisted, scripted, autonomous and mixed authority per function |
| 6 Utility | What the machine can carry, sense, transform, manipulate, produce or serve |
| 7–10 Whole machine | Systems, parts, interfaces, configurations, modifications, service, tests and failures |
| 11–12 Domains + types | Medium transitions, operating envelopes and a wide canonical recipe catalog |
| 13–16 Governance | Standards adapters, schema mechanics, difficult examples, invariants and rollout |
| 17–20 Semantic depth | Knowledge states, identity continuity, coordinates, rare mechanisms and control transitions |
| 21–24 Implementation depth | Digital thread, telemetry evidence, agents/markets, security and executable contracts |
| 25–28 Canonical contracts | Wire primitives, claims/evidence, immutable configuration graphs and lifecycle transactions |
| 29–32 Runtime + APIs | Telemetry/media ingestion, ledger/replay/scale, governed action/market execution and conformance |
| 33–36 Wire + computation substrate | Exact canonical bytes, digests, proofs, SQL append, registry evolution, units, frames, clocks and test equivalence |
| 37–40 Runtime semantics | Telemetry protocol, physics/capability compiler, control leases/safety and grounded vehicle-agent runtime |
| 41–44 Governed production system | Identity/privacy, auctions/accounting, HTTP/events/SDKs, deployment, SLOs, replay and release engineering |
| Appendices | 84 official references, 50 edge recipes, 256 implementation fixtures, wire/state matrices and KUN plus cross-domain traces |
Three precision rules
Support is not propulsion. Propulsion is not useful action. A regulatory label is not the physical type of the machine. Keeping those distinctions prevents almost every category failure in a universal vehicle system.v1.4 corrective release — record-core semantics remain stable while operational ordering, proof targets, confidential cursors, reboot-safe control, atomic external dispatch, executable institutions, migration, and release discovery become exact. See Section 55 and Appendices N–Q.