AI-generated content
Check an AI content mark
Plans (PDF, Word), the COMEX report, the attack graph report, the exercise file and the lesson-learned PDF sheet identified as containing AI-generated content carry a signed, machine-readable mark. Basis: Article 50(2) of Regulation (EU) 2024/1689. Drop a file to read it.
PDF, Word, Excel or PowerPoint, up to 10 MB. The file is read in memory and then forgotten: it is not stored, logged or passed to anyone.
What this mark does not say
- Other exports can carry text of AI origin without a mark: reports built in the browser, group reports, the .md file of a lessons-learned review, the evidence bundle. Text copied by hand carries none either.
- The mark sits in the file's properties, not in the text. Copying, printing or converting the file can make it disappear.
- Text displayed on screen in the application does not carry this mark: only exported files do.
- The mark attests what ResiPlan had on record when the file was exported, not that a model wrote every word.
- It states that the document contains AI-generated content, not which passages. It says nothing about whether the content is accurate.
- "Version approval recorded" means an administrator of the organisation approved this version in ResiPlan after the last AI write. ResiPlan does not observe that the text was read. The content stays flagged as AI-assisted.
- Files exported before this mark was introduced do not carry it.
Format of the mark
A third party can check a mark on its own machine, without going through this page.
- PDF: an XMP metadata stream (Iptc4xmpExt:DigitalSourceType = http://cv.iptc.org/newscodes/digitalsourcetype/compositeSynthetic, signature in rpai:Signature, namespace https://www.resiplan.eu/ns/ai-content-mark/1.0/) and custom keys of the document information dictionary, added as an incremental update.
- Word, Excel, PowerPoint: custom properties (docProps/custom.xml), including AIGenerated, DigitalSourceType, AIApprovalRecorded and, for the signature, AIMarkSignature.
- Signature: compact JWS (RFC 7515), EdDSA on Ed25519 (RFC 8037). Its payload holds the content_sha256 digest.
- PDF digest: SHA-256 of the whole file, with the characters of the signature replaced by "0". Office digest: SHA-256 of the sequence, sorted by path, of each part (path, a zero byte, SHA-256 of its uncompressed content), with the same replacement in docProps/custom.xml.