Trust · Claims matrix
Every claim should name the evidence that earns it.
A source test, a packaged artifact, a hosted CI run and a live deployment answer different questions. RuleOak deliberately keeps those layers separate.
| Evidence | Can support | Cannot by itself support |
|---|---|---|
| Source/static checks | Syntax, contracts, manifests, deterministic logic | Installed-native or live-service behavior |
| Workspace tests | Behavior exercised by the test harness | Universal compatibility or production reliability |
| Hosted CI | Execution on declared hosted runners | End-user device/store acceptance |
| Pack/install smoke | Distributed package shape and installability | Every downstream environment |
| Signed/native artifact | Exact build identity on a target platform | Store publication unless store evidence exists |
| Store/deployment evidence | Actual public endpoint or listing at that time | Independent security certification |
| Independent review | Findings within the reviewed scope | Unreviewed components or future versions |
Rules for public wording
- Never turn a skipped or timed-out check into PASS.
- Never use source qualification as shorthand for store/deployment truth.
- Never describe an adapter as universally compatible without external evidence.
- Never turn a standards crosswalk into certification.
- Never let model-generated analysis certify the source it produced.