# Synthetic execution-contract fixtures

These six documents demonstrate linked metadata. They do **not** describe a commissioned bench, implemented host-input provider or executed test. Numerical limits are invented fixture values, not recommended operating limits. External references use zero digests and must fail real evidence admission.

| Document | Demonstrates |
|----|----|
| [Procedure](procedure.json) | Configure a supply, enable it, measure and assert a scalar value |
| [Bench](bench.json) | Device/fixture identity, supply/return nets, shared protective resource and monitored signals |
| [Safety policy](safety-policy.json) | Separate allowed inputs, continuous conditions, bounded disable and final verification |
| [Commissioning](commissioning.json) | Exact document pins and categorised qualification evidence fields |
| [Run binding](run-binding.json) | A logical supply/output role mapped to a physical device/channel |
| [Run record](run-record.json) | Separate body result, terminal outcome and final safety assurance |

Hashes between these fixture files are real and checked. External identity, package-lock, input-contract and report references are synthetic. "Passed" values illustrate the record shape; they are not actual qualification or execution results. Both positive and rejected metadata cases are described in the [validation report](../../../../standards/execution/0.1.0/validation-report.md).