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: production support requires the automated verifier, determinism, resource, recovery, fuzz, provenance, SBOM, signature, CLI, and OCI checks bound to the exact release. Specialist review and external workloads are advisory metrics.

Supported v1 envelope

Dimensionv1 support
PlatformLinux x86-64; local NVMe scratch; cgroup v2 test envelope
FrameworkPlonky3 0.6.1; p3-uni-stark
Field and extensionGoldilocks; degree-two extension
PermutationPoseidon2, width 8
AIR contractAirPackageV1 with current, next, public, and constant expressions
OperationsAddition, subtraction, multiplication
LimitsDegree ≤ 3; width ≤ 256; rows from 210 through 224
InputsDeclarative AIR package plus uploaded trace manifest within documented size limits

Explicitly unsupported in v1

Proof features

  • Lookups and buses
  • Permutations and multi-table AIRs
  • Preprocessed or periodic columns
  • Recursion profiles

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 Community doctor emits a versioned DoctorReportV1 describing profile compatibility, planned mode, estimated conventional and bounded RAM, scratch headroom, detected platform, and any blocking reason. Keep it local. Guard’s separately redacted SupportReportV1 is the only shareable support bundle.