Building safer foundations for digital systems

Evidence and practical material

Resource library

Choose a source by the question you need to answer. Every route distinguishes orientation, normative specifications, research evidence and implementation guidance.

Start by task

What are you trying to do?

LearnUnderstand CHERI

Start with a plain-language explanation, then use the glossary for unfamiliar terms.

 BuildRun or port software

Move from a platform choice to a reproducible development environment.

 EvaluateReview research evidence

Find academic papers by architecture, software, formal methods and system question.

 ExplainPrepare a briefing or lesson

Use talks for orientation, then anchor important claims in a written source.

Browse by source type

Core collections

The source type matters. A specification defines behaviour; a paper tests a claim; documentation helps complete a task; a presentation usually provides orientation.

Academic papersA curated bibliography spanning architecture, memory safety, compartments, embedded systems, temporal safety and formal assurance. SpecificationsMatch the architecture, ABI and revision implemented by your target. DocumentationFind maintained platform, compiler, operating-system and programming guidance. Reports and white papersProgramme outcomes, adoption evidence, industry perspectives and policy material. GlossaryA real A–Z reference for CHERI architecture, software and assurance terms. TrainingRole-based learning routes and hands-on progression. Videos and presentationsDated talks and demonstrations with routes back to written evidence. DownloadsOfficial release assets, repositories, licences, checksums and compatibility notes. Digital Security by Design archiveProgramme scope, funded work, final evaluation and historical context. Frequently asked questionsShort answers that lead to fuller explanations and primary sources.

Evidence discipline

Know what a source can support.

Record the publisher, date, version, architecture, software configuration and method before relying on a claim. A paper about one prototype or workload does not automatically describe every CHERI implementation.

  • Prefer the newest applicable specification, not simply the newest document.
  • Use peer-reviewed research for the claim it actually tested.
  • Verify product availability and support with the current provider.
  • Keep older work when it explains a foundational idea, and label it as historical.