Specifications

CHERI specifications define the behaviour implemented by processors, tools and software; readers must match the document, architecture and revision to their target.

For

All audiences, with rapid routes for specialists

Last reviewed

2026-08-05

Review cycle

Review every 6 months

What you’ll find

Specifications define the behaviour that implementations, tools and software rely on. CHERI material includes architecture-specific ISA documents, language and ABI guidance, platform profiles and system-integration work.

Choose the right route

1. Architecture

Select the specification for Morello, CHERI-RISC-V, CHERIoT or another named target; do not treat them as one binary interface.

2. Software contract

Use the matching C/C++ programming model, ABI and operating-system documentation.

3. Status

Record whether a document is research, draft, stable, released or ratified, together with extensions and errata.

How to use this page

A reader should be able to identify the normative document, its status and the exact version implemented by a platform.

Check before relying on an item

The newest document is not always the one implemented by your hardware or toolchain. Match versions before interpreting behaviour.

Check publisher, date, version, scope and status. Follow summaries to the primary specification, artefact, data or project record.

Source material

Explore next

Create a one-page specification manifest for your target covering architecture, ABI, compiler, OS and platform revisions.

Understand how specifications fit together