Schema Inventory

Schema lookup

Treat the schema string as the contract name. Do not infer it from the command spelling. Match on the string in the JSON document itself, then parse the payload that belongs to that version.

The tables below are organized by emitting family so you can work in either direction: from command to schema, or from saved report back to the command family that produced it.

Read the contract name from a saved report

jq -r '.schema' profile.json

Example result

lev.cli.inspect.performance/v1

Inspection and policy

This family covers environment inspection, performance reports, import analysis, trust scans, graph output, and workspace-level import summaries.

Command	Schema
`lev inspect --json`	`lev.cli.inspect/v1`
`lev inspect performance --json`	`lev.cli.inspect.performance/v1`
`lev inspect graph --format json`	`lev.cli.graph/v1`
`lev inspect build --json`	`lev.cli.inspect.build/v1`
`lev inspect dependencies --json`	`lev.cli.inspect.dependencies/v1`
`lev inspect environment --json`	`lev.cli.inspect.environment/v1`
`lev doctor --json`	`lev.cli.inspect.environment/v1`
`lev inspect declaration NAME --json`	`lev.cli.inspect.declaration/v1`
`lev inspect trust --json`	`lev.cli.inspect.trust/v1`
`lev check --json`	`lev.cli.check/v1`
`lev verify --json`	`lev.cli.verify/v1`
`lev inspect imports --json`	`lev.cli.shake/v1`
`lev shake --json`	`lev.cli.shake/v1`
`lev profile --json`	`lev.cli.profile/v1`
`lev workspace list --json`	`lev.cli.workspace.list/v1`
`lev workspace shake --json`	`lev.cli.workspace.shake/v1`

Dependencies and project state

These schemas describe dependency selection, revision state, and the explanations around why one revision was chosen over another.

Command	Schema
`lev deps outdated --json`	`lev.cli.outdated/v1`
`lev project audit --json`	`lev.cli.audit/v1`
`lev deps --json`	`lev.cli.deps/v1`
`lev deps tree --json`	`lev.cli.tree/v1`
`lev deps why NAME --json`	`lev.cli.why/v1`

Cache, toolchains, and tools

This family is mostly operational: cache integrity, remote cache movement, toolchain chunk publishing and installation, toolchain index work, and tool inventory or cleanup.

Command	Schema
`lev cache artifacts status --json`	`lev.cli.cache.artifacts.status/v1`
`lev cache artifacts verify --json`	`lev.cli.cache.artifacts.verify/v1`
`lev cache artifacts gc --json`	`lev.cli.cache.artifacts.gc/v1`
`lev cache remote push REMOTE --signing-key PATH --json`	`lev.cli.cache.remote.push/v1`
`lev cache remote pull REMOTE --public-key PATH --json`	`lev.cli.cache.remote.pull/v1`
`lev toolchain chunks publish TOOLCHAIN REMOTE --signing-key PATH --json`	`lev.cli.toolchain.chunks.publish/v1`
`lev toolchain chunks install TOOLCHAIN REMOTE --public-key PATH --json`	`lev.cli.toolchain.chunks.install/v1`
`lev toolchain index build DIRECTORY --signing-key PATH --public-key PATH --json`	`lev.cli.toolchain.index.build/v1`
`lev toolchain index list REMOTE --public-key PATH --json`	`lev.cli.toolchain.index.list/v1`
`lev toolchain index verify REMOTE --public-key PATH --json`	`lev.cli.toolchain.index.verify/v1`
`lev toolchain gc --json`	`lev.cli.toolchain.gc/v1`
`lev tool list --json`	`lev.cli.tool.list/v1`
`lev tool gc --json`	`lev.cli.tool.gc/v1`

Text-first commands

lev workspace build, lev workspace run, lev workspace sync, and lev workspace lock do not publish aggregate JSON output. They stream member-by-member work and rely on exit status plus text diagnostics instead. When the workspace operation is import analysis, lev workspace shake --json is the JSON-emitting entry point.