R / 03 / Active programme
An operating system whose claims begin at boot.
Yuva explores a no_std Rust unikernel and micro-VMM with machine-checked leaves, fail-closed evidence, and a strict distinction between what is proved, measured, and still unknown.
Research question
Can a small agent-native compute substrate make its most important security and integrity claims verifiable from boot?
Workstreams
The programme is worked as a system.
Minimal compute substrate
Reduce the trusted computing base through a no_std Rust unikernel and tightly bounded virtualization responsibilities.
Verified leaves
Apply machine checking to small, consequential components where a precise claim can be stated and tested.
Boot evidence
Carry measurement and fail-closed decisions through the boot path instead of treating attestation as a later report.
Agent-native boundaries
Explore isolation, capability, scheduling, and evidence primitives suited to supervised autonomous workloads.
Evidence gate
What would move the claim forward?
Research maturity advances through named evidence, not through the passage of time or the confidence of the presentation.
- 01Reproducible build path
- 02Machine-checked leaf properties
- 03Fail-closed boot evidence
- 04Architecture claim ledger
Current boundary
The limit is part of the result.
Yuva is a research substrate, not a production operating system. Proved leaves, measured properties, intended architecture, and unknowns are labelled separately.