Implementation
The Liccium Platform
The FAIA attribution framework is integrated into the Liccium platform as a plugin. This enables creators, researchers, publishers, and platforms to declare AI involvement directly within their content authentication workflows. Designed to be intuitive yet technically robust, the plugin supports transparency, compliance, and interoperability by making AI contributions to content creation verifiable and persistently linked to the original work.
How does it work?
1. Select the Type of AI Involvement
Users can choose from a set of standardised Flags that reflect the degree and nature of AI’s contribution. These include the following categories:
HCC
Human-Created Content
Content created, generated and edited exclusively by humans or human-controlled instruments. While digital tools such as word processors, image editors, or audio software may be used, no generative AI systems are involved at any stage of the creative or editorial process.
AAC
AI-Assisted Content
Content where a human or a human-controlled instrument remains the primary creator and AI systems contributed during the creation process to various degrees. This may include AI-generated input that humans or human-controlled instruments accept or reject, generation of content fragments that humans or human-controlled instruments integrate into larger works, or refinement steps performed under direct human supervision and editorial control.
AIG
AI-Generated Content
Content generated predominantly or entirely by an AI system, where the AI serves as the main creative agent. Human input is limited to initiating prompts, selecting among AI-generated outputs, or making minor adjustments that do not materially alter structure, substance, or expressive intent. The resulting content is accepted largely as produced by the AI, with no substantive human editing or creatorship.
These flags provide high-level signals of AI involvement. It is intended for use in content metadata, declarations, digital packaging, or registry records.
Be aware that the framework is still in development!
2. Provide Contextual Metadata
To increase transparency and support downstream processing, FAIA supports additional metadata describing what was done, who did it, and how:
a. AI Contribution
Specifies the operation performed on or to the content. FAIA supports activity codes from:
STM (for publishing workflows)
FAIA (generic cross-media activity types)
b. System Attribution
If the activity was performed by an AI system, the following fields may be included to support reproducibility and audit:
Provider – The organization offering the AI system (e.g.
"OpenAI")Model – Underlying model (e.g.
"GPT-4o")
Be aware that the framework is still in development!
3. Bind to the ISCC Code
All FAIA declarations are cryptographically bound to the International Standard Content Code (ISCC), a content-derived identifier and ISO standard (ISO 24138). This ensures that attribution metadata remains uniquely and persistently associated with the content – even if the asset is modified and redistributed.
4. Generate Verifiable, Timestamped Declarations
Every declaration is digitally signed using Verifiable Credential (VC) or DID keys of the creator. The declaration is stored as a tamper-evident JSON-LD file (nanopublication), including a trusted timestamp. This guarantees the authenticity and integrity of the AI attribution data.
5. Register in the Liccium Registry
The declarations are published to a public, decentralised registry operated by Liccium, making them:
Publicly resolvable using content identifiers like the ISCC
Searchable for researchers, platforms, and compliance tools
Auditable under regulatory regimes such as the EU AI Act (e.g. Article 50 disclosure obligations)
This registry ensures lasting transparency and verifiability in content attribution and provenance.
Last updated