COADF Engineering Companion
From architectural principles to concrete engineering patterns.
Non-normative
- Companion version
- 1.0
- Maps to COADF Core
- 2.2
- Status
- Current
- Last reviewed
COADF states the properties a governed AI system has to keep. This companion shows how several technology stacks can keep them, where each implementation tends to break, and how to prove that a property holds.
The stack changes. The architectural property does not.
Sections
- Engineering PatternsFive patterns, each built around one architectural property.
- Implementation ProfilesFour technology stacks, each mapped onto the same properties.
- Technology MatrixOne property per row, kept by a different technology in each column.
- Technology NotesShort corrections of common category errors.
- VerificationWhat each kind of test can prove, and what no test establishes.
How it relates to COADF Core
- COADF Core is the framework: technology-neutral principles, governance templates, controls and a regulatory map. It is the authority.
- The Engineering Companion is non-normative engineering guidance. Where it and COADF Core appear to differ, COADF Core prevails.
- Engineering Patterns state one architectural property each, with the strategies, failure modes and verification that go with it, independently of any technology.
- Implementation Profiles realise those properties in one technology stack each.
- Technology Notes correct common category errors.
- Reference examples are small, fresh and synthetic. They illustrate a property and are not production implementations.
What every page contains
Every pattern states its architectural property, why it matters, valid implementation strategies, failure modes, verification, alternative realizations and limitations.
Every profile adds the technology mapping, a reference pattern, trade-offs, and what the profile does not establish.
Which principles it covers
The patterns cover P-1, P-4, P-6, P-7 and P-8, and P-5 where the probabilistic boundary carries the extraction method. P-2 and P-3 appear only at the depth COADF itself publishes: attribute-level representation, review where it is required, the source beside the reviewed value, and a rejected value left empty. Where COADF withholds the operative detail of a principle, the Companion adds none of it.
Languages
The whole Companion is published in five languages: the navigation, the overview, the patterns, the profiles, the matrix, the notes and the verification page. The reference code is shown as it was tested, in every language.
Versions
The Companion is versioned independently of COADF Core. Companion 1.0 maps to COADF Core 2.2. Each profile carries its own version, and a change to a profile does not change COADF Core. A page's status is Current, Needs review or Archived.
Limitations
- Nothing in the Companion is required by COADF.
- The reference examples are illustrative. They were tested only in the reference environment a profile names, on the date it names.
- The Java and Spring profile and the TypeScript and Node profile contain no code in Companion 1.0. Their examples follow in a later revision, after review by practitioners in those ecosystems.
- Nothing here establishes regulatory compliance, certification or conformity assessment.
Rights
Publication rights reserved. No public licence is granted for the COADF Engineering Companion 1.0 or its reference examples at this time.