Code evidence for the shop visit

Repair information starts with the code.

Each guide explains what a generic OBD2 record means, which evidence a qualified shop may test, what the code cannot prove, and what to bring to the appointment.

Axlyne does not publish a code page until a named human reviewer checks its sources, diagnostic boundaries, and visible copy.

Foundation source-checked August 4, 2026

Human-reviewed code guides

The index lists approved guides only. Drafts stay out of search and return no public detail page until review is complete.

Three launch guides are written and source-checked. They remain private until a named human reviewer approves the exact copy.

Read the record before choosing the test.

A code names an observation made by vehicle diagnostic logic. A qualified shop combines it with the exact vehicle, service information, measurements, inspection, and the conditions in which the record appeared.

The record
Exact code, status, timestamp, vehicle identity, freeze frame, readiness, and companion records when the vehicle returns them.
The boundary
No failed-part verdict, safety decision, price estimate, emissions certificate, code-clearing instruction, or replacement claim.
The handoff
A compact evidence packet and code-specific questions that help the shop start from recorded facts instead of a parts guess.

Source floor for every guide

Every launch guide cites the current SAE J2012 definition standard, the current SAE J1979 base standard and digital annex, California BAR guidance, and official U.S. EPA OBD material. Vehicle-specific service information still controls the shop test.

Continue with code evidence, the adapter guide, or the full Axlyne guide library.