Schema and discovery endpoints

Liskov serves generated JSON Schema for tooling:

GET /api/application-manifest/schema
GET /api/application-policy/schema

The first describes customer-authored proof.liskov.application-manifest V4. The second describes server-materialized proof.liskov.application-policy V4.

Use

Download from the same Liskov environment you target, cache by content digest, and configure your editor or validator to reject unknown fields. Re-fetch when the published schema digest changes. The authoritative semantic validation is:

proof liskov application manifest validate --file PATH

JSON Schema can validate shape, enums, and many bounds. The Liskov validator also applies cross-field rules. Publication preflight additionally checks identity, artifact evidence, enabled capability, entitlement, and current server facts.

Compatibility

Do not infer support from a schema property alone. Typed-but-gated fields are listed in Capabilities and limits. V4 is the only public authoring contract.

These discovery routes do not announce a generally supported public REST API. Use Console and the public CLI for customer workflows unless another endpoint is explicitly documented as a stable product contract.