Goal
Explore how the Compute Witness fixture contract could connect to the existing Rust ProofPath verifier without destabilizing the v0.1 JSON fixture contract.
Proposed scope
- Map job manifest fields to Rust verifier concepts.
- Map verifier decision outputs to compute receipt fields.
- Identify missing Rust types or adapters.
- Keep this as a spike unless the integration boundary is clear.
Acceptance criteria
- Short design note or draft adapter path is created.
- No broad rewrite of existing Rust verifier.
- v0.1 fixtures remain stable.
- Clear decision: proceed with adapter / defer / split into smaller tasks.
Why it matters
The Python validator is good for reviewability. A Rust integration path would make Compute Witness feel closer to the core ProofPath engine and more credible for production-oriented users.
Goal
Explore how the Compute Witness fixture contract could connect to the existing Rust ProofPath verifier without destabilizing the v0.1 JSON fixture contract.
Proposed scope
Acceptance criteria
Why it matters
The Python validator is good for reviewability. A Rust integration path would make Compute Witness feel closer to the core ProofPath engine and more credible for production-oriented users.