> For the complete documentation index, see [llms.txt](https://faia.liccium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faia.liccium.com/technology/vocabulary.md).

# Vocabulary

The FAIA Vocabulary provides a structured, machine-readable model for describing AI involvement in digital content creation. Rather than relying on a single label, FAIA combines complementary vocabulary elements that describe the overall nature of a work, the role AI played during its creation, and the AI systems involved.

The vocabulary is designed to support interoperable AI attribution across different media types, workflows, publishing environments, platforms, and technical systems.

FAIA semantic resources are published as open vocabularies and ontologies using persistent identifiers and Semantic Web standards, including JSON-LD or RDF.

Together, these components support transparent, consistent, and interoperable disclosure of AI involvement across media types, workflows, and application domains.

<figure><img src="/files/gXXT6x4Sfgv7aQeZCM93" alt=""><figcaption></figcaption></figure>

### FAIA Flags

FAIA Flags provide a high-level classification of the resulting content. Every FAIA declaration contains exactly one Flag describing whether the work is Human-Created, AI-Assisted, or AI-Generated.

The Flags communicate the overall degree of AI involvement while remaining independent of the specific tools or workflow used.

[Learn more about FAIA Flags →](/technology/vocabulary/faia-flags.md)

### Activity Codes

Activity Codes describe how AI contributed during the content lifecycle. Unlike the FAIA Flags, multiple Activity Codes may be associated with a single declaration to describe different forms of AI involvement.

FAIA defines a set of generic Activity Codes – Co-Creation, Contribution, Enhancement, Refinement, Transformation, and Analysis – that apply across media types. It also supports the integration of domain-specific activity vocabularies, allowing communities to adopt established classifications within the broader FAIA framework. The first supported example is the STM AI Classification for scholarly publishing.

[Learn more about Activity Codes →](/technology/vocabulary/activity-codes.md)

### System Attribution

System Attribution records the AI system used during content creation or modification and, where available, the version involved. Identifying the AI system provides additional transparency, reproducibility, and context, particularly as different systems and releases may differ substantially in capabilities and behaviour.

[Learn more about System Attribution →](/technology/vocabulary/system-attribution.md)

### Relationship Between the Vocabulary Components

The three vocabulary components complement one another:

* FAIA Flags answer: "What is the overall nature of this content?"
* Activity Codes answer: "How did AI contribute during its creation?"
* System Attribution answers: "Which AI system and version were used?"

Together they provide a structured vocabulary for describing AI involvement in a way that is understandable to both humans and machines.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://faia.liccium.com/technology/vocabulary.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.