Alliance
Technical leadership
Technical leadership keeps architecture, software, system integration and assurance work aligned without collapsing legitimate implementation choices into a single design.
Remit
Technical leadership keeps architecture, software, system integration and assurance work aligned without collapsing legitimate implementation choices into a single design. It combines deep subject expertise with transparent review and practical attention to adopters.
Why this matters to participants
Adopters need to know where normative decisions are made, how competing proposals are evaluated and which technical outputs are stable enough to use.
Responsibilities and decision points
1. Architecture stewardship
Maintain clear relationships between shared CHERI principles, architecture-specific specifications and implementation profiles.
2. Cross-stack alignment
Surface dependencies between processors, operating systems, compilers, languages, libraries, tools and assurance evidence.
3. Open review
Record assumptions, alternatives, unresolved questions and decisions so contributors can inspect the reasoning.
Records, safeguards and limits
Technical leadership is not a substitute for standards-body authority, supplier support or independent product assurance. The status of each output should be explicit.
Use the Alliance’s current governance, membership and programme pages for organisational facts. Distinguish formal decisions from explanatory material.