Trust and provenance
Evidence model
A KERNARY workflow is only as trustworthy as the immutable relationship between its source, build, target, measurement and approval records.
Plans, builds, tests and approvals are append-only records. Corrections produce new versions linked to the prior record so an engineer can reconstruct why a release candidate exists.
Evidence object
{
"apiVersion": "kernary.dev/v1alpha1",
"kind": "TestEvidence",
"metadata": {
"id": "evidence://testrun/9183/can-loopback",
"createdAt": "2026-08-20T12:43:04Z",
"actor": "tool://kernary-test/hil-runner"
},
"subject": {
"source": "git:abc123",
"build": "build://orbit-controller/2387",
"board": "board://imx93-orbit/rev-b/bay-07",
"fixture": "fixture://can-loopback/v3"
},
"result": {
"verdict": "pass",
"assertions": { "passed": 18, "failed": 0 }
},
"provenance": {
"serialLog": "sha256:…",
"measurements": "sha256:…"
}
}Evidence strength
| Level | Example | Confidence |
|---|---|---|
| Assertion | Agent or engineer hypothesis | Useful for planning, not completion |
| Static | Binding validation or source analysis | Proves structural constraints |
| Build | Pinned build completed with manifest | Proves reproducible compilation |
| Simulation | QEMU or Renode suite passed | Proves software-level behaviour |
| Physical | Versioned board and fixture passed | Strongest target-specific evidence |
| Fleet | Observed outcome across a deployment cohort | Strongest operational evidence |
Querying evidence
kernary evidence query \
--project orbit-controller \
--subject build://orbit-controller/2387 \
--type source,build,simulation,physical,approval \
--format treeThese docs are part of the product design. Interfaces remain proposals until an implementation is published.