> 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/faia-flags.md).
# FAIA Flags
FAIA Flags provide a high-level classification of AI involvement in digital content. Every FAIA declaration carries exactly one Flag, describing the overall nature of the resulting work no matter how many AI systems or activities were involved in producing it.
The Flags offer a simple, consistent way to communicate whether content was created entirely by humans, produced with meaningful AI assistance, or generated predominantly by AI. They focus on the resulting work rather than the individual production steps. More detailed information about AI involvement is expressed separately through Activity Codes and System Attribution.
### Human-Created Content (HCC)
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.
### AI-Assisted Content (AAC)
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.
### AI-Generated Content (AIG)
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.
## Design Principles
The three FAIA Flags are mutually exclusive, so the overall classification stays unambiguous. They deliberately remain high-level and do not identify individual AI-supported activities or specific AI systems. Those are represented separately through Activity Codes and System Attribution, letting a declaration combine a simple overall classification with more detailed workflow and technical information.
Together, the three vocabulary components provide a structured, interoperable, and machine-readable framework for describing AI involvement across media types, sectors, and workflows.
One optional point you could add, if you want the flag-to-activity relationship signposted here: in the vocabulary, Transformation and Analysis are reserved for AIG. That nuance might belong on the Activity Codes page instead, to keep this section purely high-level. Your call.
---
# 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/faia-flags.md?ask=&goal=
```
`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.