Reference

These documents describe Metewand's implemented interfaces, compatibility contracts, and runtime behavior. Start with the getting started guide for a complete first run.

Commands and workflows

Create a benchmark, check and plan it, verify its workers, and run it. After execution, inspect its status and identities or export results for analysis. All commands provide versioned machine output.

Contracts and planning

Problem contracts define validity and independent evaluation. Public schemas, canonical JSON, and typed identities fix the language-neutral representation. Configuration expansion, logical planning, and scheduling define how a manifest becomes an ordered set of attempts.

Compatibility versions records the current contract versions, the pre-MVP stability policy, and verification guidance for extensions.

Sources, execution, and storage

Source resolution and the artifact store connect declared inputs to verified content. The runtime records timing envelopes, measurements, and execution controls. Durable publication and the run store preserve completed results and support explicit recovery.

Worker protocol and SDKs

The worker protocol defines communication between Metewand and worker processes. The Python SDK and R SDK provide callback dispatch, serialization, output helpers, and structured errors. Shared conformance suites check their compatibility with the Rust implementation.

The sidebar lists the complete reference. The repository's design also describes planned interfaces; the roadmap tracks implementation progress.