Begin with the working path
The quick start follows one evidence chain from a qualified build snapshot to an inspectable result. It is the shortest route for a first local run and the reference workflow for later automation.
Prepare the evidence
Capture the exact sources, build profile, index, toolchain, and analysis world in one immutable manifest.
Run the analysis
Validate first, then scan. Keep canonical JSON and distinct exit outcomes intact.
Explain one result
Pass the exact subject identity from scan output back to why against the same manifest.
Choose the detail you need
Use the CLI guide when you need commands and sequencing. Open the rule catalog when you need an English condition description, its current qualification, the relevant evidence family, or the shared boundary that can force an unknown result.
The two surfaces describe the same analysis contract: the guide teaches the workflow; the catalog makes individual rules inspectable.
Read every rule as a contract
Catalog snapshot 4558458d contains 138 RuleIDs and 141 conditions. Of those conditions, 33 have an accepted bounded status; 108 conditions remain outside that accepted boundary.
Those numbers describe the reviewed catalog snapshot, not a claim that every rule is generally available or equally mature.
138 RuleIDs
Stable identifiers make rules addressable without reducing them to display names.
141 conditions
Conditions expose the semantic question each rule is actually allowed to answer.
33 conditions accepted within scope
Acceptance applies only inside the documented profile and evidence boundary.
Follow evidence, not intuition
The absence of known references does not prove that code is unused. Missing index membership, a different build profile, an open analysis world, or unmodeled dynamic behavior can change a negative answer into unknown.
That is why explanations stay attached to the same immutable manifest and exact subject identity as the scan.
Know the publication boundary
The English quick start is available without an account and describes the current advisory local workflow. There is no public binary, hosted project workflow, or blocking findings gate in this publication.
The English catalog and individual rule pages live on the separate documentation site. They preserve the same snapshot, identifiers, accepted-subset labels, and explicit unknown handling; five accepted conditions also publish their reviewed narrow scope in English.