Meta Frontier AI Framework — vendor disclosure form

1. Vendor identification

2. AI system identification

3. Provision-specific questions

1. Foundation Models / GPAI. Does the offered system meet the threshold for a general-purpose / foundation model under Meta Frontier AI Framework (Framework applies to Meta frontier-model releases (Llama family))? If yes, identify the specific obligations you will satisfy and the evidence you will provide.

   (Cite: Framework applies to Meta frontier-model releases (Llama family))

2. Transparency Obligations. Provide the documentation required under the transparency obligations of Meta Frontier AI Framework (Open-weight release + framework publication is itself a transparency posture; trade-off discussed in framework text) — including (as applicable) model card, system card, training-data summary, evaluation results, and known limitations.

   (Cite: Open-weight release + framework publication is itself a transparency posture; trade-off discussed in framework text)

3. Catastrophic & Existential Risk. Has the offered system been evaluated against catastrophic-risk thresholds (e.g., CBRN information uplift, autonomous replication) consistent with Meta Frontier AI Framework (Framework critical-risk tier — commit to halt training pre-mitigation if reached)? Provide the evaluation report or its public-disclosure equivalent.

   (Cite: Framework critical-risk tier — commit to halt training pre-mitigation if reached)

4. Open-Weight Frontier Release. Are the model weights powering the offered system released under an open-weight licence? If yes, identify the licence + any restrictions under Meta Frontier AI Framework (Framework's distinctive feature — explicit defence of open-weight release as governance posture; halt-training commitment if 'critical risk' threshold reached without mitigations).

   (Cite: Framework's distinctive feature — explicit defence of open-weight release as governance posture; halt-training commitment if 'critical risk' threshold reached without mitigations)

4. Documentation enclosures expected

Tick each enclosure attached to the vendor response. Missing enclosures should be explained in the “Variances” field below.

• Transparency documentation (per-instrument schema)
• Training-data summary / provenance log
• Safety / capability evaluation results
• Vendor company registration + insurance certificates
• Sub-processor / supply-chain list (including model upstream)

5. Vendor attestation

The undersigned, on behalf of the vendor, attests that the disclosures above are true and complete to the best of their knowledge at the date signed, and undertakes to notify the buyer in writing within 30 days of any material change to those disclosures.