Skip to content
Luiz Hogrefe

Open Template Library

One semantic source, three readable forms

Pilot catalogue · prototype

Governance documents, data declarations and checklists usually exist in several copies: a PDF for people, a schema for systems, a prompt for tools. The copies drift. This library is built to prevent that.

The library on anylai.eu

The idea

A template is written once, as a semantic source. From that source three forms are generated: a machine-readable form for validation, an AI-readable form for tools that assist, and a human-readable form for the people who sign off.

Because all three come from one source, a change is made once and cannot contradict itself across forms.

One source, three forms

One source, three forms
Semantic source
version · provenance · lifecycle
  • Machine-readable
    schema for validation
  • AI-readable
    context for assisting tools
  • Human-readable
    document for sign-off
Registry

The semantic source is the only thing anyone edits.

Text description of the diagram

A single semantic source, carrying version, provenance and lifecycle status, is validated and then generated into three forms: machine-readable, AI-readable and human-readable. A registry records each published version.

What a template has to carry

  • Versioning

    Every published template has a version, and older versions stay resolvable.

  • Provenance

    Where each field's meaning comes from: a regulation, a standard or an internal decision.

  • Lifecycle

    A status such as draft, published or retired, so nobody relies on something withdrawn.

  • Validation

    The semantics validate, not only the syntax.

  • Registry

    One place that lists what exists, in which version and with which status.

  • Examples

    Filled examples that are themselves validated against the template.

Status: pilot catalogue

5published templates

Since 16 September 2026 the library is a pilot catalogue in the AnyLAI repository. A generator validates each source against COADF 2.2 controls that exist, produces the three representations, checks that they agree and locks every published version; the count on anylai.eu is read from the generated registry, not written by hand.

It is a prototype: five templates, English only. A template helps implement a control; it settles no legal question, and whether it applies depends on the system it is used in. An earlier planning figure for the size of the library is not repeated, because those templates were never built.

When a template counts

A template enters the published list only when it has all of the following:

  1. 1A canonical schema
  2. 2Substantive semantics that validate
  3. 3Machine, AI and human forms generated from the one source
  4. 4Tests
  5. 5A version and a lifecycle status
  6. 6A mapping to COADF principles or controls

The published templates

Each one maps to a COADF 2.2 principle and is published in version 1.0.0 with its human guide, AI contract and machine template.

Titles as published; the library is in English.

The idea at the scale of one field

Country of origin

Machine-readable

{
  "field": "countryOfOrigin",
  "type": "string",
  "pattern": "^[A-Z]{2}$",
  "required": true,
  "evidence": ["certificateOfOrigin"],
  "version": "0.1.0-sketch"
}

AI-readable

Field countryOfOrigin: ISO 3166-1 alpha-2. Never infer it from an address; if no certificate is attached, leave it empty and ask.

Human-readable

Country of origin: the country in which the goods were produced. Two-letter code. Required. Evidence: a certificate of origin.

An illustrative sketch of the three forms of a single field, written for this page. It is not one of the published templates.

Not to be confused with

COADF's governance templates, such as the AI agent charter, which are published with the framework, and the patterns of the COADF Engineering Companion.

  • COADFPublished framework

    A published framework for building AI-assisted software under explicit governance: eight principles, a control manifest and CI-enforced fences.

    COADF