Conformance

What the SeedSpec 0.4 conformance suite covers and what a passing result does not claim.

Run the bundled suite

The CLI and corpus are bound to the same coordinated release.

npx --yes @seedspec/cli@0.4.2 conformance
npx --yes @seedspec/cli@0.4.2 conformance --json --output conformance-report.json

The report records the exact release, suite version, corpus digest, and case results.

What passing establishes

Valid and invalid 0.4 package structures produce the expected result.
Manifest merging and external section expansion are deterministic.
Success anchors and local references are checked consistently.
Portable package digests are stable and content-sensitive.
Unsafe paths, unsupported versions, and broken references fail.

What it does not establish

That the specification is complete, clear, or useful.
That an agent will implement it correctly.
That the publisher controls the declared identity or metadata.
That package content is safe to execute.
That two packages compose without product-level conflicts.

Conformance is narrow so independent tools can agree without claiming semantic quality or implementation correctness.

Sources