Backend Plan Audits #
Inspection data for contract-carrying kernel plans.
The planner chooses capsules. The audit layer records what that choice means for trust boundaries:
which provider was selected, which device it targets, how its shape, layout, value, and VJP
obligations are supported, and whether a capsule has the trustedExternal classification. A
checked LibTorch capsule still executes foreign code. These classifications distinguish the
declared evidence, not whether Lean has proved the implementation. Audits are stored inside
numerical certificates and compared on replay, so they must have decidable equality.
Audit row for one selected backend kernel.
- op : BackendOp
- capsuleName : String
- provider : Provider
- device : Device
- trustLevel : TrustLevel
- vjpMode : VJPMode
- shapeContract : ContractDescriptor
- layoutContract : ContractDescriptor
- valueContract : ContractDescriptor
- vjpContract : ContractDescriptor
- numericalPolicy : NumericalPolicy
Instances For
Instances For
Build an audit row from a selected planner kernel.
Instances For
The four contract descriptors of the selected kernel, paired with the field each one fills.
Instances For
Instances For
Capsule names selected by the plan, in plan order.
Instances For
Whether any selected capsule has the trustedExternal evidence classification.
Instances For
Audit a selected kernel plan.
Instances For
Whether any selected capsule has the trustedExternal evidence classification.
Instances For
Operation names whose selected capsules are trusted external.