Profile: Chat / Messaging

Chat platforms (Telegram, WhatsApp, Slack, Discord) lack custom headers but support text signatures. TAP disclosure in chat uses a compact one-line signature.

Signature format

<host>:<context>$ <status> <name>: <summary>

Components:

• host - system or organization identifier
• context - working directory or context marker (e.g. ~)
• $ - prompt separator
• status - visual status indicator (EU AI Act icon where supported, or color emoji)
• name - agent name
• summary - one-line description of the action or status

Example:

hq:~$ [AI] Liza: email sent, waiting for reply

Where [AI] represents the EU icon (in platforms supporting inline images) or a status emoji (in text-only platforms).

Automatic vs manual signatures

TAP RECOMMENDS automatic signature injection for programmatic agents (bots, assistants). The signature SHOULD be appended by the agent framework, not manually composed per message.

For short replies (1-2 sentences), the signature is OPTIONAL to avoid noise. For substantive replies (3+ sentences), the signature is RECOMMENDED.

Platform-specific fallbacks

• Telegram/WhatsApp (text only): use emoji status indicators (color circles or unicode)
• Slack/Discord (rich text): EU AI Act icon as custom emoji, or inline image
• Web chat widgets: full HTML with icon + metadata

Before / after

Before (typical chatbot):

Bot: Hi! How can I help you today?

After (TAP-compliant chat agent):

Hi! How can I help you today?

hq:~$ [AI] Liza: ready to assist