LLMO Validator

Reference validator for the LLMO specification.

This page is the reference validator for llmo.json documents. It checks a document against the published JSON Schema and reports which conformance tier the document achieves (Minimal, Standard, Strict) per §5.1 through §5.3 of the LLMO specification.

The validator runs entirely in your browser. Nothing is uploaded.

Input

Loading AJV from esm.sh...

Self-test: strict conformance test vector

Click Load strict test vector above to populate the textarea with the strict test vector from /spec/v0.1/test-vectors/signed-strict.json, then click Validate. Expected: an amber Strict (partial, paste mode) badge. Every document-internal Strict-tier check (X1 signature shape, X4 domain-ownership) passes; the two URL-mode-only checks (X2 JWKS retrievability, X3 Cache-Control) are skipped because paste mode cannot fetch the JWKS. Any lower tier is a regression.

The strict test vector is embedded in this page as a <script type="application/json"> block (CORS on llmo.org/spec/v0.1/* prevents a live fetch from this origin). See README for the update workflow.

Current limitations and future work

  1. Signature verification is not performed by this tool in v0.1 due to cross-origin constraints on fetching external JWKS from client JavaScript. Implementers verify signatures using the procedure in §4 and the JWS signing-input reference at /spec/v0.1/test-vectors/signed-strict-payload.json.
  2. URL-mode validation depends on the target domain permitting cross-origin requests. Most domains do not. Paste mode is the reliable path.
  3. A server-side validator built as a self-hostable service (for example, on Cloudflare workerd or an equivalent open runtime) is a reasonable future project. It would unblock signature verification, remove the CORS dependency, and allow headers like Cache-Control on the JWKS response to be observed directly. Out of scope for this version.