Conformance Suite
Forge supports six SDKs, so behavioral parity needs executable checks rather than documentation promises.
Levels
| Level | Scope |
|---|---|
| L0 Core Runtime | Schema validation, lifecycle transitions, topology routing, and tool tiers. |
| L1 Accountable Runtime | Local development identity, identity derivation, ACT authorization, delegation, glyph determinism, and Brew resolution. |
| L2 Full Runtime | WASM execution, on-chain or durable deployment, full lineage verification, and resource governance. |
Repo locations
| Path | Purpose |
|---|---|
forge-rs/conformance/scenarios/ |
End-to-end runtime scenarios. |
forge-rs/conformance/vectors/ |
JSON vectors for deterministic behavior. |
forge-rs/conformance/harness/* |
Language harnesses for Rust, TypeScript, Go, Python, Swift, and Kotlin. |
forge-rs/conformance/reference_runner.py |
Reference runner for scenario validation. |
What conformance protects
Conformance checks should catch:
- an SDK accepting invalid lifecycle transitions
- a provider reference parsing differently across languages
- a tool tier bypassing approval
- identity derivation drift
- glyph rendering drift
- Brew resolution drift
- missing cross-language scenario support
Release rule
A feature is not cross-SDK behavior until its scenario or vector passes in the target SDKs. Rust reference support alone should be documented as Rust-first.