Fetch the recorded public Run Card surface (content-negotiated).

One recorded evidence surface for a signed Run Card, projected without any principal/owner identifiers. The representation is chosen by ?format= then the Accept header (default text/html for browsers): no-JavaScript HTML, compact JSON, JSON-LD (visible claims == JSON-LD), a citation/answer packet (Markdown), or a badge. All representations carry a deterministic content-addressed ETag with a public, revalidated cache and Vary: Accept, and are derived from the same revalidated stored snapshot as the JSON endpoint.

Inputs. Path, query and header fields are listed below. No request body is required.

Outputs. See each status below for its media type, schema and headers. A missing record or unavailable capability is not a successful empty result.

Errors. Read the status and Content-Type before decoding. Document, image, redirect and file routes need not return JSON errors.

Rate limits. Public read budgets apply by client IP and route group. This operation can have a smaller route-specific budget. Read Retry-After on 429 or retryable 503 responses.

Example setup. Use an identifier returned by the matching list, search or create operation. Sample identifiers are not a promise that a record exists.