2026-07-20

TAP and EU AI Icons: how they can coexist side by side

Machine translation. Original

When Europe introduces visual labeling for AI-generated content, it’s easy to read this as an attempt to simplify a complex topic of content provenance down to a couple of icons. But looking closer, the conflict here isn’t necessary. On the contrary: European icons and TAP solve different problems and therefore layer well on top of each other.

Short Thesis

EU icons are a layer for quick human perception and legally significant disclosure. TAP is a layer for extended provenance: who participated, which model, what role, which carrier carries it, and how confident the record is.

In other words:

the icon answers the question: “what is this in front of me?”
TAP answers the question: “who and how made this?”

One layer does not cancel out the other.

What the European Approach Actually Does

On the European Commission page about EU Icons for labelling AI-generated content, the logic is quite practical. The focus there is not on the full history of provenance, but on ensuring that a person, no later than first contact with the content, can understand that they are facing AI-generated or AI-manipulated material.

The page directly links the icons to the transparency rules of the AI Act and highlights two key disclosure cases:

deepfakes - AI-generated or manipulated image, audio, or video content;
AI-generated or manipulated text on matters of public interest, if the text has not undergone human review/editorial control and no one has taken editorial responsibility.

At the same time, the EU already has three practically useful visual modes:

Basic icon - when AI was involved in creating deepfake content or published text, or when an additional label or interactive second layer is used.
Fully AI-Generated - when the entire material is wholly created by AI without human-created elements and without human editorial control, except for prompting.
Partially AI-Modified - when the original human material was partially modified by AI.

Crucially: the use of the icons themselves is optional, but disclosure as an obligation is not optional. That is, it’s not a specific pictogram that is mandatory, but a clear disclosure of the fact of AI generation/manipulation.

What TAP Does

TAP goes deeper. In the current SPEC.md, it already describes not just the presence of AI, but a structured provenance scheme:

model - exact model id;
provider;
version of the protocol;
role;
author;
human;
confidence (recorded, reconstructed:<source>, unknown).

Moreover, TAP is not limited to a single web page. It already has profiles:

Web;
File;
Git;
Media/Work.

That is, TAP is not just a public badge for the reader, but a full-fledged way to make provenance portable across HTML, files, commits, and media artifacts.

Why They Don’t Conflict

Because they answer different levels of transparency.

Level 1. Quick Signal for Humans

The user sees:

that AI was involved;
whether the content is fully generated;
whether it was partially modified.

This is a task of interface, trust, anti-deception, and accessibility.

Level 2. Extended Provenance

An editor, developer, researcher, or machine sees:

which specific model was involved;
who was the accountable human;
what the roles were (drafting, review, synthesis, translation, etc.);
whether the record was live (recorded) or reconstructed;
where it is recorded - in web/footer, data-*, JSON-LD, file header, git trailers.

This is a task not just of UX, but of verifiable authorship structure.

The Formula for Coexistence

The strongest formula looks like this:

EU-style icon = quick disclosure
TAP = full provenance

Essentially, the icon is the front label, and TAP is the nutrition facts plus supply chain.

A piece of material can simultaneously have:

a visible visual label for first contact;
a TAP byline for someone who wants to understand authorship more precisely;
data-* and JSON-LD for machine extraction;
file headers and git trailers for internal and archival verifiability.

This is not duplication, but layered transparency.

Where EU Icons Are Stronger Than TAP

Looking honestly, the European approach has one important advantage: it better answers the question “what will an ordinary person see immediately?”

TAP is already strong as a structure, but it currently lacks a similarly compact and standardized visual language like the EU icons. It has a byline, data-*, JSON-LD, but lacks a simple display-layer that can be easily embedded into an interface, card, caption, overlay, or footer.

Therefore, adding a visual/icon layer to TAP is not a concession, but a strengthening.

Where TAP Is Stronger Than EU Icons

EU icons do not answer the questions:

which specific model was used;
which provider;
whether the person was only a prompter or also an editor;
whether human review exists and how it is expressed;
how reliably the provenance is recorded;
how provenance lives in file/git/web/media.

An icon can say Fully AI-Generated, but it won’t say:

claude-opus-4-8 or gpt-5.4;
who took on the review;
whether the document can be linked to an author profile;
whether the history of contributions can be aggregated across a repository.

TAP can do this.

Another Layer: Sparkles as the De Facto Global AI Symbol

Beyond the official EU icons, a de facto common visual symbol for AI has already emerged - sparkles / twinkles / “stars.”

This is not a formal standard, but culturally it is already very strong:

Google publicly writes about the rise of the AI sparkle icon and shows how sparkles have become a systemic sign of AI across Google interfaces;
in Google’s research, it is stated that users indeed recognize the sparkle as a sign of AI;
at the same time, both Google and external UX researchers note the problem: sparkles signal “something AI-ish is here” well, but do not provide precise, standardized semantics.

This makes sparkles useful as:

a familiar AI cue;
a product/UI shorthand;
a light companion symbol alongside provenance.

But it does not make them sufficient as a normative disclosure solution.

What This Means for TAP

For TAP, it is reasonable to distinguish three classes of visual notations:

Regulatory icons - e.g., EU icons, when a compliance-oriented display is needed.
Generic AI symbols - e.g., sparkles, when a familiar broad consumer cue is needed.
TAP-native labels - a textual or mixed mode where there is an icon + explicit wording + deeper metadata.

This is precisely how TAP can become not a competitor to other icons, but a framework for compatibility between them.

Practical Direction for TAP

1. Introduce a Separate Display Profile

TAP already has Web/File/Git/Media. It is logical to add:

Profile: Display

Its task:

describe first-exposure disclosure;
set rules for perceivability and accessibility;
describe the mapping between richer provenance and simple visual states;
allow the use of different visual families: EU-style icons, sparkles, text-only labels, mixed icon+text.

2. Normalize Disclosure States

A minimally useful set:

human
ai-involved
ai-generated
ai-modified

This provides a natural bridge:

EU Basic icon -> ai-involved
EU Fully AI-Generated -> ai-generated
EU Partially AI-Modified -> ai-modified

And sparkles can be described as a non-normative generic visual marker for ai-involved, if there is an explicit label nearby.

3. Separate Legal Minimum and TAP Richness

This is a very important distinction.

Legal minimum: disclose the very fact of AI-generation/manipulation.
TAP richness: name the model id, provider, roles, confidence, profiles, author pages, git provenance, etc.

Then TAP does not argue with the regulator, but embeds itself above the minimum threshold.

4. Add Display Metadata

For example:

display_state
display_family
display_label
display_icon
display_mode
display_basis

Then it becomes possible to express:

a regulatory EU icon;
sparkles as a generic AI cue;
a purely textual label;
a hybrid label + icon + second layer.

5. Explicitly Describe Compatibility with External Icon Families

It is important to state clearly:

TAP does not replace platform-mandated or law-mandated visible disclosures;
TAP can coexist with them;
TAP can use them as a compatible display family;
TAP can also support generic icon families, including sparkles, as a non-exclusive and non-normative option.

Why This Is a Strong Position

If TAP adopts such an architecture, it will look not like an alternative camp, but like a universal provenance protocol with multiple display surfaces.

This is stronger than arguing about which icon is “correct.”

Because in the real world, several layers will coexist simultaneously:

the law will require one thing;
the product interface will want another;
provenance and archival integrity will require a third.

TAP can become the framework that connects these layers.

Conclusion

EU icons and TAP do not contradict each other. They lie on different floors of the same transparency system.

EU icons provide a minimally understandable human-facing disclosure;
sparkles provide a widely recognized consumer/UI signal, but with weak precision;
TAP provides a precise and portable provenance layer.

The best development for TAP is not to reject this simplicity or dissolve into it, but to do the following:

add a Display Profile;
introduce normalized states like ai-involved, ai-generated, ai-modified;
describe compatibility with both EU-style icons and sparkles;
retain richer metadata as TAP’s main differentiator.

Then TAP can be simultaneously:

compatible with regulatory labeling;
understandable to the ordinary user;
useful for editorial teams, developers, and archives;
honest about real human-model co-authorship.