Technical Leadership

CHERI spans processor architecture, system-on-chip integration, compilers, operating systems, languages, compartment models, safety, and product assurance. No single discipline can set a credible adoption path alone.

A distributed model

The Alliance draws technical direction from member experts, working-group leads, implementation projects, researchers, and adopters. The Governing Board provides organisational oversight, while working groups turn defined problems into coordinated activity.

Technical leadership includes:

• identifying interoperability gaps and adoption blockers;
• maintaining roadmaps and prioritising shared work;
• connecting architecture choices to software and product needs;
• reviewing claims and making assumptions visible;
• coordinating with open-source projects, standards communities, and implementers;
• publishing reusable guidance, code, tests, and evidence where appropriate.

How to evaluate output

Every technical artifact should make its status clear. A discussion draft, working-group recommendation, experimental repository, released specification, and certified product record have different authority and stability.

Readers should check:

1. who maintains the work;
2. the architecture and versions it covers;
3. whether it represents group consensus or an individual contribution;
4. the test and review process;
5. known limitations and planned changes;
6. the licence or policy governing reuse.

Participate

The working-group directory is the starting point for current topics. Organisations can bring implementation experience, user requirements, review effort, or maintained contributions. The contact page is the right route when it is not clear which group fits.

Technical leadership does not remove healthy disagreement. Its purpose is to make choices, evidence, and trade-offs visible enough for the ecosystem to converge where commonality creates value.