Runtime & Integrations · Runtime Harness · M5
Evidence Approval (API)
Keeping generated artifacts from manufacturing authority.
The governance API enforces in code what Evidence
Approval states:
SyntheticDataset.status is always
proposed, an annotation is an authority input only with a
validation_record, and a benchmark cannot approve a threshold.
Generated evidence is accepted, recorded, and used — but it cannot grant itself gating power. The API makes the hopeful path impossible to take, not merely discouraged.
The enforced rules
| API | Behavior |
|---|---|
import_synthetic_dataset(..., declared_status=...) | Returns a SyntheticDataset whose status is always proposed — a hopeful declared_status is accepted but never honored. |
AnnotationImport.is_authority_input | True only when a non-empty validation_record is present. |
approve_threshold_from_benchmark(evidence) | Always raises GovernanceError; a benchmark provides BenchmarkEvidence.supports(...), never an approval. |
Propose, never approve
Only a host
AuthorityRecord or ApprovedThreshold confers gating power.
Everything a machine produced enters informational.