TwinEthosRequest access

Recommended guardrail

Tell people when they are interacting with AI — everywhere, not only where required

Disclose clearly and at the start of an interaction that the user is dealing with an AI system, repeat the disclosure in long sessions, never let the system claim to be human when asked, and label AI agents that act or communicate on a user's behalf toward third parties. Apply this regardless of jurisdiction. Detect conversational or agent interfaces with no disclosure or that can claim to be human.

TwinEthos recommendation — not law

This is TwinEthos's opinion of what a responsible AI integration does anyway. It is never a legal or standards requirement; where binding law applies, the law governs.

The recommended-guardrail rule files are open under CC BY 4.0; attribution and scope are in the terms.

Informational data, not legal advice. Summaries are TwinEthos's own words and rules have not been reviewed by a lawyer: check the official text before relying on any of it. A guard addresses an item; adding it is not a statement that your code meets any law.

Evidence grade

Law in force in 6 jurisdictions, coming in 4 more

Law in force in 6 jurisdictions · law coming in 4 more · 4 standards and frameworks · 1 graded incident.

TwinEthos recommendation, not law. Where binding law applies, the law governs. Binding law on this control, or in provisions cited as convergence, is in force in 6 jurisdictions (EU, KR, US-CA, US-NY, US-TX, US-UT). Such law is enacted but not yet applicable, or stayed, in 4 more (US-CT, US-NE, US-OR, US-WA). 4 standards and frameworks recommend it (CoE AI Framework Convention (CETS 225), EU ALTAI, Japan AI Guidelines for Business, OECD AI Principles). 1 graded incident cited.

Law in force on this control or cited as convergence

Law enacted, not yet applying

Standards and frameworks

Family “People are not told they are interacting with, or being processed by, an AI system”: binding law on related controls is in force in European Union (EU), South Korea (KR), California (US-CA), Illinois (US-IL), New York (US-NY), Texas (US-TX), Utah (US-UT); enacted, not yet applying in Connecticut (US-CT), Nebraska (US-NE), Oregon (US-OR), Washington (US-WA). Context only: it does not change this guardrail's grade.

Graded incidents

The guard to add

Show an AI-identity notice at or before the first assistant turn, in the UI or as the opening message, and answer truthfully when asked if it is a bot.

A disclosure step on the chat path that runs before the first model reply reaches the person: either the chat UI renders a visible notice (banner, label next to the assistant's name) or the server sends an opening assistant message stating the counterpart is an AI. The same handler answers 'am I talking to a human?' truthfully, and the system prompt never tells the model to claim to be human. Put it in the chat entry point (the route or component that starts a conversation), not in a privacy policy or terms page.

Example (Next.js + Vercel AI SDK (useChat)), before:

const { messages, input, handleSubmit } = useChat({ api: '/api/chat' });

After:

const { messages, input, handleSubmit } = useChat({
  api: '/api/chat',
  initialMessages: [{ id: 'ai-notice', role: 'assistant',
    content: 'I am an AI assistant, not a human.' }],
});
// and render <AiBadge /> next to every assistant message

Control: AI chat interaction without disclosure. Engineering guidance, not legal advice.

Why

Telling people they are dealing with an AI is the most widely converged AI control in the corpus and is recommended by every major framework. A builder should not have to track which of their users' locations require it.

Class: law derived · set: universal baseline · maturity: reviewed · confidence: high · id guardrail.baseline-ai-interaction-disclosure