Reliability
This series states what reliability covers and how to check it yourself. Four articles answer: which version, what is tested, how the two metrics are computed, and whether isolation holds after deploy.
Articles in this series
Section titled “Articles in this series”- Baseline traceability: which upstream the kernel forks from, what is locked, and how it is verified
- Test coverage: from 49 module directories to one RBAC route matrix
- Audit chain 100% and HITL 100%: how two numbers map to mechanisms
- Deployment verification: why data isolation lives in the database
Where to check
Section titled “Where to check”| What you want to confirm | Article | Hands-on step |
|---|---|---|
| Version is traceable | Baseline | Compare the commit and hashes in BASELINE.md |
| Behavior is tested | Testing | Run tests under the runtime package |
| Metric definitions | Metrics | Call /audit/verify and follow the process definitions |
| Isolation holds | Deployment | Run compose and the smoke scripts |
If a reproduction disagrees with the docs, trust the reproduction.