Recent records
The operator can review recently created Crank evidence without hunting through unrelated phone storage.
My Garage • local evidence records
My V.A.U.L.T.
V.A.U.L.T. is Crank’s local record layer: reports, routes, captures, diagnostic logs, vehicle/equipment records and support packages remain under the operator’s control until they choose to export or share them.
Local-firstAsset-awareExport by choiceRecord stewardship
Current capability map
What this section does.
This page describes the capability architecture represented in the current Crank development build. Interface wording may continue to be polished, but the functions below are the working product structure.
Diagnostic reports
Reader reports, code evidence and other diagnostic records can be retained locally.
A.I.R.O.N. logs
Technician Data Logger CSV evidence stays with the vehicle packet and can be reopened later.
CrankScope records
Vibration evidence and related support packages remain associated with the measured asset.
Drive / Map records
Routes, trip records and map-track evidence can be cataloged and reopened.
Experience Recorder files
Session reports, raw GPS/motion data and event evidence can be retained as a coherent record.
Motorheads runs
Performance reports, charts and route evidence have a dedicated history lane.
Galleries / captures
Photos and related media can be reached from the same controlled record ecosystem.
Support packs
Scrubbed support packages can be generated when troubleshooting the app itself.
Storage stewardship
Setup, storage-health and cleanup tools are separated from record browsing so large evidence collections remain manageable.
Operating flow
How it fits together.
Step 1Crank creates evidence
Step 2Save locally
Step 3Catalog by asset / lane
Step 4Review later
Step 5Export / share intentionally
Crank truth boundary: V.A.U.L.T. is not a hidden cloud synchronization layer. Crank’s design starts from local operator-controlled records and explicit handoff when the user chooses to share.