Gap-free shard receipts and canonical events
Logical shard epochs, commit sequences, projection checkpoints and recovery modes are now exact.
Implementation standardJuly 2026Open-world model
Every vehicle
becomes a living system.
One durable identity for the body, its parts, work, measurements, stories, audience, value and increasingly autonomous life—without confusing a social persona with physical truth or legal authority.
Concept & directionLNK·RTracer team
55core sections
17appendices
328conformance fixtures
73ksource words
A vehicle category is a projection over facts—not a box the object must fit inside.
Movement, utility, control, power, embodiment and evidence are independent facets. A fan can propel a boat, a bicycle or an airship. Wheels can move a car, an aircraft on the ground, or a robot inside a warehouse. The model records what is true without forcing one inherited category.
Universal object model
One kernel. Composable facts.
Persistent identityEmbodied
Assetrt:asset
Assetrt:asset
Identity
Body & scale
Power & fuel
Movement
Utility
Control
Evidence
Persona
Commerce
01 · HumanRead the system as a story
Begin with the design goal, then move from identity through physics, lifecycle and agency.
02 · ImplementerBuild against exact contractsStart at the normative profile, then follow records, ledgers, runtime and conformance.
03 · AgentResolve stable machine surfacesUse the manifest, compact index, full text and structured JSON without scraping presentation.
RTR · CZ · 001KUN
Prague Workhorse
Reference vehicle
The truck is not a post. It is the account.
KUN’s public character can tell the story of its work, publish authorized telemetry, remember maintenance, invite people to events and accumulate an audience. Its physical record remains evidence-bound; its agent remains mandate-bound.
- Identity
- Vehicle profile + physical identifiers
- Life
- Work, care, modifications and missions
- Voice
- Sensor-grounded, disclosed AI persona
- Value
- Offers, appraisal and settlement kept distinct
Infinite by composition
Truck to blimp without changing the kernel.
The more unusual the machine, the more valuable independent facets become.
1/8 RC buggyfan bicyclehydrofoilairboatelectric scooterrocket stagewarehouse AMRcableway cabinagricultural dronesoft roboteVTOLPrague work truck
Documentation map
The full standard, split into durable surfaces.
All 55 core sections and 17 appendices are already imported. Each route is static HTML with stable block identifiers and matching agent-readable artifacts.
08FoundationsCore specification chapters08Identity & embodimentCore specification chapters08Configuration & lifecycleCore specification chapters08Mobility & operationsCore specification chapters08Trust, markets & controlCore specification chapters15ImplementationCore specification chapters17AppendicesNormative and reference material
For agents
Do not scrape the website.
Every important surface has a canonical machine representation, version, digest and stable URL. Agents can cite the same section a person is reading.
GET /substrate/v1.4.1/manifest.json
{
"id": "rtracer-…-v1.4.1",
"credit": "Created and directed by LNK",
"source": { "sha256": "5dcdab50d87dde1a…" },
"sections": [ … ]
}v1.4 release
The universal model now has an executable institutional and runtime spine.
Casework from title through market integrity
Registries, insurance, repair, moderation, youth safety, teams, tax, incidents and appeals share one accountable kernel.
Immutable pages, schemas and migration maps
People and agents resolve the same stable identities, full text, fixtures, hashes and version-pinned routes.
KUN + RC buggy + blimp + cableway
Run deliberately different reference systems through the same conformance bundle without changing the semantic kernel.