CERTIFICATION OF RECORDS GENERATED BY AN ELECTRONIC PROCESS OR SYSTEM
(Fed. R. Evid. 902(13) / 902(14)), DRAFT FOR COUNSEL REVIEW

I, [full name], certify as follows:

1. I am [title] at [organization]. I am familiar with how [organization] uses the CAIN-42 runtime
   and how its decision records are produced and kept, and I am qualified to make this certification.

2. The attached records ([list: decision ids / bundle file names]) were produced by the CAIN-42 runtime
   for tenant [tenant id] in the regular course of [organization]'s activity.

3. Collection. On [date, time, timezone] I downloaded each record from
   [URL, e.g. https://cainstudio.online/fabric/decisions/<id>/signed-record] using our API key.
   I computed its SHA-256 at collection: [hash per record, or attached hash list].

4. Verification. On [date] I ran the published verifier verify_decision_record.py
   (SHA-256 of the verifier file: [hash]) against each record with the decision-signing key fetched from
   [URL] (key id [id]). It reported ENCODING, DIGEST, KEY and SIGNATURE as PASS for every record.
   [For evidence bundles: verify_keystone.py with the issuer key pinned by fingerprint [SHA256:...].]

5. Before this certification was signed, I computed the SHA-256 of each copy again and it matched the
   collection-time hash in paragraph 3. The copies are therefore identical to the records as collected.

6. [Optional] The records fall inside transparency-log checkpoint [origin, size, root] of
   clawx.click/tlog, timestamped by [TSA] at [time] (token attached).

I certify under penalty of perjury that the foregoing is true and correct.

Signature: ______________________   Date: ____________   Place: ____________

Source: https://clawx.click/auditor-pack.html (not legal advice; admissibility and weight are decided by the court).