Solution · AI Labs & Model Builders
Ship models with the transparency your customers will demand.
System cards, GPAI transparency duties, incident reporting and downstream-deployer assurance — generated from the same record, kept current.
MOD-008Foundation model · v3.4
GPAIOwner · Head of Research
Parameters
34B · dense
Training compute
>10^25 FLOPs · disclosed
Evaluations
14 internal · 6 third-party
Known limitations
Documented · 8 entries
EU AI Act GPAI · mapped Deployer pack · live Eval refresh due · 14 days
DERIVED FROM ONE RECORDv2026.06
The sector problem
Transparency artefacts and deployer asks live in different files.
Each enterprise customer asks the same questions in their own format. Each regulator asks for an artefact in a different shape.
The underlying truth is one model record. Hael writes once and renders many.
MOD-008One record · four audiences
Enterprise diligenceQuestionnaires · auto-answered
Regulator (EU AI Office)GPAI technical documentation
CustomersModel card · deployer pack
Research communityPublic system card
What matters here
What a model builder needs to ship governance with the model.
01
System and model cards
Generated from the model record — training data scope, evaluations, known limitations, intended use — every line cited and held open where evidence is missing.
Card
MOD-008 · v3.4 · sourced
02
GPAI transparency duties
EU AI Act GPAI obligations mapped to the model: technical documentation, copyright policy, training-data summary — kept current.
GPAI
Art. 53 · 4 / 4 mapped
03
Downstream assurance
Read-only deployer view: the artefacts a customer needs to do their own classification and DPIA, served from your record.
Deployer pack
14 enterprises subscribed
MOD-008 · v3.4
One record
EU AI Act GPAIArt. 53 · Annex XI
NIST AI RMFMap · Measure · Manage
ISO/IEC 42001Lifecycle controls
Deployer (downstream)Read-only pack
EVERY AUDIENCE · ONE SOURCE4 views
Through-line
One model record. Every audience that depends on it.
Researchers, customers, regulators and incident-reporting bodies all read from the same record, in the shape each one needs.
When a control or eval changes, every downstream artefact moves with it.
Proof
A model card, sourced.
MOD-008 · public system card
Sourced
Intended use and out-of-scope useMOD-008 · Registry
Training data scopeMOD-008 · Documents §2
Evaluations and benchmarksEval suite · 2026-05-30
Known limitationsIncident log · 8 entries
Carbon and compute disclosureHeld open · v3.5 refresh
EVERY LINE CITEDv2026.06