Engineering · Release evidence
A release is a chain of evidence, not a single green badge.
Different environments prove different properties. RuleOak keeps those layers separate so a source-level PASS cannot silently become a device, store or production claim.
1 · Source identityExact archive/tree, manifest, hashes, modes and provenance.
2 · Source qualificationStatic checks, schemas, tests, invariants, security/publication gates.
3 · Build qualificationReal toolchain compilation/package generation from the exact source.
4 · Native/runtime evidenceInstalled behavior, lifecycle, accessibility, performance and recovery.
5 · Distribution evidenceSigning, store validation, purchase/entitlement/provider configuration.
6 · Deployment evidenceLive endpoint, hosted controls, public links and externally verifiable artifacts.
Evidence invalidation
When the source, configuration, platform behavior or another decision-critical input changes, evidence should be re-bound or re-run. “A similar build passed earlier” is useful history, but it is not automatically current evidence.
Historical evidence still has value
Prior evidence can inform scope, regression risk and targeted retesting when the relevant bytes/contracts are unchanged. It should be labelled as retained evidence rather than presented as a new execution result.
No false green: unavailable evidence remains pending/not-run. The report should show the gap rather than optimize for visual completeness.