# Implementation

## The Liccium Platform

The FAIA attribution framework is integrated into the [**Liccium platform**](https://liccium.com/) 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.

<figure><img src="/files/Bs5dmBoKj6z2xMQHqhMa" alt=""><figcaption><p>Liccium application</p></figcaption></figure>

## 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:

<table><thead><tr><th width="139.49609375" align="center">Flag</th><th width="196.65625">Name</th><th>Description</th></tr></thead><tbody><tr><td align="center">HCC</td><td>Human-Created Content</td><td>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.</td></tr><tr><td align="center">AAC</td><td>AI-Assisted Content</td><td>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.</td></tr><tr><td align="center">AIG</td><td>AI-Generated Content</td><td>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.</td></tr></tbody></table>

These flags provide high-level signals of AI involvement. It is intended for use in content metadata, declarations, digital packaging, or registry records.

*<mark style="color:red;">Be aware that the framework is still in development!</mark>*&#x20;

### **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**&#x20;

If the activity was performed by an AI system, the following fields may be included to support reproducibility and audit:

* **System** – The AI system or engine used to generate or modify the content
* **Version** – The particular version of the AI system used.

*<mark style="color:red;">Be aware that the framework is still in development!</mark>*&#x20;

### **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.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://faia.liccium.com/technology/implementation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.