Adopted
RustCrypto and the dalek crates for SHA-2, AES-GCM, ChaCha20-Poly1305, Ed25519 and X25519; rustls and rustls-webpki for TLS and X.509; wasmi for WebAssembly.
Engineering
A written plan, recorded decisions, automated tests on every change and audits with evidence. Failures are not hidden: they are reproduced, studied and fixed with a test.
Principles
Compare, then reuse or improve
Not writing every line: studying the established implementations and their failures, measuring ours against them for compatibility and for how fast the system runs, and keeping the winner (ADR 0063). Adopted code must carry a permissive licence; GPL and proprietary code are not accepted.
RustCrypto and the dalek crates for SHA-2, AES-GCM, ChaCha20-Poly1305, Ed25519 and X25519; rustls and rustls-webpki for TLS and X.509; wasmi for WebAssembly.
The kernel, its drivers and services; the SSH server, with ML-KEM and key re-exchange; TCP, with its transmission rebuilt; ECDSA and RSA verification, HMAC, HKDF and the kernel generator, which measured faster.
Decisions
Each decision that shapes the system is recorded as an ADR with its context, the alternatives considered and the consequences.
Measured, not guessed
Figures from QEMU with TCG on the development machine, p50. They compare builds with each other; they do not predict real hardware.
Process
main, develop and feature, fix and hotfix branches. Small commits with descriptive messages; the whole QEMU suite must pass before anything reaches main.
Important milestones are audited and the findings recorded with evidence. Hotfix versions (0.1.1, 0.3.1, 0.4.1, 0.5.1, 0.8.1) carry the fixes.
Record, reproduce, study from several angles, confirm with evidence, fix with a test, audit, close. In strict mode a component halts at its first unexpected failure instead of looping.
Incident 0001 — transaction errors on the laptop’s USB stick — was investigated with three independent studies, strict-mode dumps and measurements on the host before any fix was accepted.