Conformance and fixtures
Exact ANVIL test inputs and honest verification boundaries.
Forge includes conformance inputs and language harnesses. A fixture catalog records what can be checked; a release report records what was actually executed and passed.
Download exact fixtures
The fixture manifest lists every copied JSON file and its SHA-256 hash. Paths retain the original layout:
/conformance/vectors/L0-core-runtime/— core runtime inputs./conformance/vectors/L1-accountable-runtime/— accountable runtime inputs./conformance/scenarios/— integration scenarios.
Use URLs from the manifest for individual files; directories are not API endpoints.
Run from source
forge-rs/conformance/README.md describes the harness contract. The source includes reference_runner.py and separate Rust, TypeScript, Python, Go, Swift and Kotlin harnesses. Match each run to its language version, feature profile and fixture hashes.
The unpublished forge-conformance-harness is workspace tooling. It is not an SDK installation dependency.
Record evidence
A useful report includes the source revision, dependency lockfile, selected features and target, fixture hashes, exact command, exit status, passed/failed/skipped scenarios, and any environment assumptions. Keep source coverage, unit tests, cross-language conformance and deployed journeys separate.
This documentation publication verifies its own page/export build. It does not assert that all six runtimes passed conformance or that remote deployments are active.