Selected-asset carryover
The service workspace begins from the current asset instead of asking the operator to rebuild vehicle context from scratch.
My Garage • service research + procedure evidence
Service Command Center™
Service Command Center is Crank’s controlled service-procedure workspace: identify the exact application, determine supported coverage, preflight the live vehicle safely, preserve evidence and present verified manual procedure knowledge without turning guesses into commands.
Capability coverageRead-only preflightPacket ownershipProcedure evidence
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.
Capability Coverage Matrix
Crank separates what is supported, what is manual-only, what requires additional authority and what remains unverified.
Service preflight
A protected read-only gate can check identity authority, selected-packet ownership, reader channel, protocol, voltage, engine state, speed and other observable conditions before service work.
One OBD operation at a time
Long-running live-data consumers are coordinated so Service Command Center does not silently compete with a Deep Scan, Runtime Gauges or the A.I.R.O.N. logger.
Bounded read-only module inventory
Where the reader/protocol permits it, the current build can perform a deliberately constrained physical-endpoint inventory without opening programming, coding or write-command paths.
Evidence lifecycle
Selected, observed, verified and saved states are surfaced separately so a technician can see what was actually established.
Procedure research
Application-specific manual procedures can be researched using year/make/model/engine/trim/market and other applicability data without transmitting VIN.
Offline knowledge
Approved procedure knowledge can be cached locally for later use when connectivity is unavailable.
No invented service truth
When the exact configuration or authoritative procedure cannot be established, Crank leaves the value or procedure unresolved instead of filling the gap with a guess.
Operating flow
How it fits together.
Step 1Confirm selected asset
Step 2Review coverage
Step 3Run read-only preflight
Step 4Open verified procedure
Step 5Save evidence
Crank truth boundary: Service Command Center is intentionally conservative. Read-only discovery, manual procedures and evidence can be useful without enabling manufacturer-specific write commands that Crank has not verified.