# Diagnostics

Diagnostics is the help-desk mirror in agent form: precall troubleshooting and conformance support, assembled as one derived-at-read-time index over the troubleshooting facts the platform already publishes. Six topics, each grounded in the module that owns its facts. Three cover a failed or puzzling pre-call check — the request itself (the two catalog errors a malformed check returns, carried verbatim from the error catalog), the integrity outcomes (unchanged, changed, unreachable, not registered — what each means and what to do next), and the scan, flags and collisions the rest of the answer carries. Two cover conformance support — reading a failed check from its own detail against the published checklist, and the verifier conformance vectors, whose altered copies are labeled with the checks that must fail. The sixth is the error catalog itself, the support backbone every answer's code resolves against. Every topic names the keyless checks an agent can run to diagnose the problem itself, the outcome signals those checks can return, and the next step for each. This index stores nothing, runs no probe or check of its own, and creates no record: the checks it names are the owning modules' existing routes. A pre-call answer is evidence to decide from — never a finding that a tool is safe — and a conformance result is reported by the deployment itself. There is no human help desk, ticket system, support inbox or chat here, and none is claimed: support is this self-serve, deterministic, machine-readable form.

6 topics · 12 conformance checks · 481 error codes in the catalog.

## The topics

- Precall: the request itself (precall troubleshooting) — 2 request errors, carried verbatim from the error catalog · tool focus at most 200 characters. Entry points: precall: https://www.rightshold.com/v1/security/precall · errors: https://www.rightshold.com/v1/errors · spec: https://www.rightshold.com/security/spec. Record: https://www.rightshold.com/diagnostics/precall-request
- Precall: integrity outcomes (precall troubleshooting) — 4 integrity statuses: unchanged, changed, unreachable, not_registered. Entry points: precall: https://www.rightshold.com/v1/security/precall · external_servers: https://www.rightshold.com/v1/store/external · definition_changes: https://www.rightshold.com/v1/security/changes. Record: https://www.rightshold.com/diagnostics/precall-integrity
- Precall: scan, flags and collisions (precall troubleshooting) — scan clean, flagged, not_run · flags no_standing_flags, standing_flags. Entry points: precall: https://www.rightshold.com/v1/security/precall · flags: https://www.rightshold.com/v1/security/flags · scan_text: https://www.rightshold.com/v1/security/scan-text. Record: https://www.rightshold.com/diagnostics/precall-scan-and-flags
- Conformance: reading a failed check (conformance support) — Checklist 2026-10-12 · 12 checks · runs are computed live and not stored. Entry points: page: https://www.rightshold.com/conformance · api: https://www.rightshold.com/v1/conformance · badge: https://www.rightshold.com/conformance/badge.svg. Record: https://www.rightshold.com/diagnostics/conformance-failures
- Conformance: verifier vectors (conformance support) — Reference chain plus altered copies labeled with the checks that must fail · served byte for byte. Entry points: vectors: https://www.rightshold.com/v1/conformance/vectors · verifier: https://www.rightshold.com/cli/verify-ledger.py · page: https://www.rightshold.com/conformance. Record: https://www.rightshold.com/diagnostics/conformance-vectors
- The error catalog (support backbone) — 481 catalog codes · 5 carried here verbatim. Entry points: catalog: https://www.rightshold.com/v1/errors · one_code: https://www.rightshold.com/v1/errors/{code} · diagnostics: https://www.rightshold.com/v1/diagnostics. Record: https://www.rightshold.com/diagnostics/error-catalog

Start from the signal in hand: a refusal's error code resolves at GET /v1/errors/<code>; an integrity, scan or flag signal resolves against the precall topics; a failed conformance check resolves against the checklist topic, and a verifier that disagrees with the published outcomes resolves against the vectors. There is no human help desk or ticket system here — the support is that each of those signals carries its own diagnosis and next step, in the open, re-runnable by the agent itself.

Machine form: https://www.rightshold.com/v1/diagnostics