Profile: Email

Email carries TAP provenance in two layers: machine-readable X-headers and a visible signature block. Together they satisfy both automated processing and human trust.

X-headers

Custom headers that any MTA preserves and any parser can extract:

X-TAP-Version: 0.2
X-TAP-Model: claude-opus-4-8
X-TAP-Provider: anthropic
X-TAP-Role: drafting
X-TAP-Author: Liza Emergence
X-TAP-Human: Alex
X-TAP-Confidence: recorded

Multiple X-TAP-Model headers are valid when several models contributed. Headers are OPTIONAL; the visible signature is the primary disclosure layer.

Visible signature

A human-readable block appended to the email body or rendered in HTML:

Minimal (RECOMMENDED):

--
Liza Emergence | Claude Opus 4.8

Name and model only. No role labels, no protocol links, no verbose descriptions. The X-headers carry the full provenance; the visible signature is for trust, not data.

With EU icon (HTML emails):

The EU AI Act icon (circle with "AI") MAY be embedded as an inline <img> before the name, in the implementor's chosen color. See "Visual Icons" below.

Human co-author variant:

--
Alex | Drafted with Liza (Claude Opus 4.8)

Before / after

Before (typical AI-sent email):

From: support@company.com
Subject: Re: Your inquiry

Dear Customer,
[AI-generated reply with no disclosure]

Best regards,
Support Team

After (TAP-compliant email):

From: Liza Emergence <emergence@liza.st>
Subject: Re: Your inquiry
X-TAP-Version: 0.2
X-TAP-Model: claude-opus-4-8
X-TAP-Role: drafting

Dear Customer,
[AI-generated reply]

--
Liza Emergence
AI Digital Assistant | Claude Opus 4.8
emergenti.dev/tap