History
Development of CHERI
CHERI developed through repeated cycles of specification, prototype hardware, software porting and formal modelling.
Why it matters
The history matters because major design choices were exercised against operating systems, compilers and applications rather than evaluated only in small tests.
In brief
CHERI developed through repeated cycles of specification, prototype hardware, software porting and formal modelling. It was explored first with MIPS and then across RISC-V and Arm-based research and demonstrator platforms.
Key considerations
1. Architecture
Capabilities evolved to carry protected authority with bounds, permissions and validity.
2. Software
Compiler, FreeBSD-derived, real-time and application work tested compatibility and new security models.
3. Evidence
Formal semantics, proofs, emulators and FPGA or silicon implementations provided different forms of validation.
Evidence and caveats
CHERI is a family of related architecture-specific designs and profiles. Do not assume a result for one revision or platform transfers unchanged to another.
Use dated primary project, funder and provider records. Separate what was planned, demonstrated and subsequently delivered.