Profile: Display
The Display profile defines how TAP provenance is surfaced at first exposure to a person. It does not replace Core or any other profile; it provides a single normalized disclosure field that implementations render however they choose.
The display field
A TAP record MAY include a display field with one of the
following values:
human- no AI contribution is disclosed for this content unit.ai-involved- AI materially participated in creation.ai-generated- content is generated by AI in full (except prompting).ai-modified- a pre-existing human work was materially modified by AI.
In YAML front matter:
tap:
display: ai-involvedIn data-* attributes:
<article data-tap-display="ai-involved" data-model="claude-opus-4-8">In git trailers:
TAP-Display: ai-generatedHow it maps to external icon systems
The display value tells implementations WHAT to
disclose. HOW to render it (which icon, which label, which style) is the
implementation's choice. Recommended mappings:
- EU Basic icon ->
ai-involved - EU Fully AI-Generated ->
ai-generated - EU Partially AI-Modified ->
ai-modified - Industry sparkle ->
ai-involved(generic cue, non-normative)
An implementation MAY pull icons from:
- a public icon set (e.g.
emergenti.dev/icons/) - EU official assets
- its own platform-native icons
- the user's profile/preferences
TAP prescribes the semantic state, not the visual rendering.
Relationship to legal disclosure
TAP does not replace law-mandated or platform-mandated visible AI disclosures. Where a jurisdiction requires a visible label (e.g. EU AI Act Article 50), a TAP implementation:
- MAY use that external label as its Display rendering
- MUST NOT claim that TAP alone satisfies external obligations
- SHOULD keep richer TAP provenance available beneath the visible disclosure
Design principle
The Display profile is intentionally shallow. It answers: "What should the user understand immediately?" The rest of TAP answers: "Who did what, with which model, in which role, and how confidently is that recorded?"