Why I built it
Vehicle data is difficult to trust when transport state, capture identity, and later interpretation are mixed together.
What exists
Capture and Journal operate as a private diagnostic family with attended hardware evidence and deliberately separated ingestion authorities.
How it works
A device-side capture path produces bounded artifacts and receipts; a local journal records provenance, review state, and diagnostic interpretation.
- Device and vehicle capture
- Sanitized capture receipts
- Local diagnostic journal
- Simulated and attended validation paths
My role
Designed the hardware-facing capture flow, transport controls, evidence receipts, journal model, and recovery procedures; directed the implementation and validated it against real hardware and simulator paths.
What I checked
- physicalAttended hardware capture and device workflow
- runtimeLocal capture and journal authorities exercised
What stays bounded
- No VIN or personal vehicle history is public
- Diagnostic support is not a repair guarantee
- Capture and journal authorities remain distinct
What is missing
- The private core is vehicle- and device-dependent and is not packaged as a general consumer product.
Next
Release a synthetic diagnostic bundle and provenance specification.
Later ideas, not current features
- Produce a public-safe parser and simulator subset
- Expand redaction tooling
- Recruit a narrowly defined design partner