V.A.U.L.T. setup
Storage destinations, storage health, stewardship/cleanup and Map / Track recording setup.
My Garage • configuration / support / safety
Help / Setup
Help / Setup keeps configuration, storage, capture permissions, support, manuals and safety guidance in one deliberate place. Support handoff is evidence-aware: Crank can verify the public Full Internal ZIP state and refuses to launch an attachment-less share when a readable ZIP cannot be proven.
Storage setupCapture setupVerified support ZIPManual + safety
Current capability map
What this section does.
Support and configuration are kept separate from active diagnostic work, but the support path still follows Crank’s evidence doctrine: a report is not called share-ready until the ZIP that will actually be handed off is readable and verified.
Capture setup
Event snapshots, voice-control setup, screen/video capture configuration and recorder privacy boundaries.
Full Internal report pack
Internal diagnostic support can package the deeper system evidence used to separate Reader transport, focus ownership, Runtime freshness, report publication and other implementation-level behavior.
Verified public ZIP publication
When Android publication succeeds, Crank records a verified public ZIP state and path instead of merely assuming that a Downloads copy exists.
Local-only truth
If Android will not publish the public ZIP, Crank can report the pack as local-only rather than silently presenting a false public-success state.
Attachment fail-closed
SHARE THIS ZIP is designed to open the outgoing share/email path only after a readable ZIP attachment URI is verified. If Crank cannot prove the attachment, it does not intentionally open an attachment-less support email.
Start Here
A simple guide for choosing the right Crank lane before diving into technical detail.
Offline help / manual
Operator guidance can remain available without relying on a live network connection.
How-to resources
Public training and how-to links can be reached from the same help surface.
About Crank / Mission
The product mission and Dingfelder resources are separated from operational controls.
Safety / Privacy / Legal
Crank’s operating boundaries are surfaced as part of setup rather than buried behind a legal footer.
Reader help
Code-reader configuration and troubleshooting remain available without making the Reader Library the center of the whole product.
Operating flow
How it fits together.
Step 1Open Help / Setup
Step 2Choose configuration or guidance
Step 3Review boundary / setting
Step 4Apply intentionally
Step 5Return to My Garage
Crank truth boundary: Support output follows the same truth rules as vehicle evidence. “Report created” and “public ZIP verified” are different states, and an outgoing support handoff should not claim an attachment that Crank cannot actually read.