Proof features
- Lookups and buses
- Permutations and multi-table AIRs
- Preprocessed or periodic columns
- Recursion profiles
Compatibility profile v1
Narrow support is part of the product.
Guard v1 targets one frozen profile and remains release-gated until that profile is fully qualified. The free doctor exists to reject ambiguity before a purchase or long proof job.
Release-gated profile: the FRI configuration becomes production-supported only after specialist review and complete profile-specific correctness, resource, recovery, and external-workload evidence.
Supported v1 envelope
| Dimension | v1 support |
|---|---|
| Platform | Linux x86-64; local NVMe scratch; cgroup v2 test envelope |
| Framework | Plonky3 0.6.1; p3-uni-stark |
| Field and extension | Goldilocks; degree-two extension |
| Permutation | Poseidon2, width 8 |
| AIR contract | AirPackageV1 with current, next, public, and constant expressions |
| Operations | Addition, subtraction, multiplication |
| Limits | Degree ≤ 3; width ≤ 256; rows from 210 through 224 |
| Inputs | Declarative AIR package plus uploaded trace manifest within documented size limits |
Explicitly unsupported in v1
Alternative stacks
- Custom fields or hashes
- Arbitrary Plonky3 forks
- Other proving frameworks
- Unqualified FRI profiles
Platforms
- Windows production proving
- macOS production proving
- GPUs
- Network filesystems as scratch
Compatibility is fail-closed
A job with a missing or unknown field, unsupported feature, mismatched release, unsafe path, or out-of-envelope size is rejected. Guard never guesses that an adjacent profile is equivalent.
What the doctor returns
The doctor emits a versioned JSON report describing profile compatibility, estimated conventional and bounded RAM, estimated scratch, free-space headroom, detected platform, and any blocking reason. The report must be scrubbed before sharing; it is designed not to contain witness values or license material.