Static readiness reports

Long-form HTML readiness reports are internal engineering artifacts. Do not copy them into the public web `public/` tree or serve them from the customer-facing site. Host them on a private artifact store, internal portal, or CI download instead.

Viewing reports

Open generated HTML from your local build output, CI artifact, or internal documentation system. The public product documentation explains policy only — it does not embed audit HTML.

Keeping sources aligned

Treat the repository or CI output as the source of truth. If a team needs a shared URL, use authenticated hosting — not unauthenticated static paths on the marketing or app origin.

Note

Reports describe posture at a point in time. They are not a substitute for live API verification — use gates, tests, and (in non-production) OpenAPI for authoritative behavior.

Markdown parity notes

Parity notes may ship as Markdown in your internal repo. View them locally or in your team’s doc tooling — they are not exposed as raw public URLs on this site.

Readiness report (resources) · API overview