G7 Hiroshima AI Process Code of Conduct — 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 G7 Hiroshima AI Process Code of Conduct (Code applies to advanced AI)? If yes, identify the specific obligations you will satisfy and the evidence you will provide.

   (Cite: Code applies to advanced AI)

2. Deepfakes / Synthetic Content. Does the offered system generate or substantially modify audio / video / image / text in ways requiring disclosure or machine-readable provenance under G7 Hiroshima AI Process Code of Conduct (Code §5 (content provenance + watermarking))? Describe the disclosure + provenance mechanisms implemented and their robustness against removal.

   (Cite: Code §5 (content provenance + watermarking))

3. Transparency Obligations. Provide the documentation required under the transparency obligations of G7 Hiroshima AI Process Code of Conduct (Code §2 (publicly report capabilities, limitations)) — including (as applicable) model card, system card, training-data summary, evaluation results, and known limitations.

   (Cite: Code §2 (publicly report capabilities, limitations))

4. Catastrophic & Existential Risk. Has the offered system been evaluated against catastrophic-risk thresholds (e.g., CBRN information uplift, autonomous replication) consistent with G7 Hiroshima AI Process Code of Conduct (Code §1 + §3 — explicit risk-identification including CBRN)? Provide the evaluation report or its public-disclosure equivalent.

   (Cite: Code §1 + §3 — explicit risk-identification including CBRN)

5. Synthetic Content Provenance. Does the offered system generate or substantially modify audio / video / image / text in ways requiring disclosure or machine-readable provenance under G7 Hiroshima AI Process Code of Conduct (Code §6 — 'develop and deploy reliable content authentication and provenance mechanisms')? Describe the disclosure + provenance mechanisms implemented and their robustness against removal.

   (Cite: Code §6 — 'develop and deploy reliable content authentication and provenance mechanisms')

4. Documentation enclosures expected

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

• Content provenance + watermarking technical description
• Copies of submitted regulatory reports / registrations
• 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.