Write a system prompt that keeps AI from posing as a human: set a disclosure rule, ban fake first-person experiences, control tone, and red-team the result.
Last verified · 2026-07-26 · by Moe Ameen
The default behavior of a raw language model is to talk like a person. Ask it how its day is going and it will invent one; ask if it remembers your last chat and it may claim it does. Left unconstrained, that human-shaped tone drifts from friendly into misleading — a reader ends up believing they are talking to, or reading the words of, a real human when they are not. That is impersonation, and in 2026 it is both a trust problem and, increasingly, a legal one: the EU AI Act, California's bot-disclosure law, and a new wave of anthropomorphic-AI rules all turn on whether people know they are dealing with a machine.
The fix lives in the system prompt — the always-on instruction block the model reads before every response. This guide walks the exact rules to put in it: an explicit identity, a ban on fabricated human experiences, tone control that stays warm without lying, a scripted answer to "are you human?", the one legitimate exception (a named brand persona that never claims to be a specific real person), and a red-team pass so you know the rules actually hold. The same discipline is what OpenAI's Model Spec and Anthropic's published character guidance bake into their own models — you are applying it to yours.
Disclosure is increasingly a legal requirement, not just good practice. The EU AI Act's Article 50 requires that people be told they are interacting with an AI system unless it is obvious, and that obligation applies from August 2, 2026. California's bot-disclosure law (SB 1001, in effect since 2019) makes it unlawful to use a bot to mislead someone about its artificial identity in order to incentivize a commercial transaction or influence an election, with clear disclosure as the safe harbor. China's first anthropomorphic-AI rules took effect July 15, 2026. Requirements vary by jurisdiction and use case — treat this as orientation, not legal advice, and confirm what applies to you.
A system prompt is where you write the rule; the hard part is enforcing it on every output at production volume, which is exactly what Kompozy operationalizes. Three layers do the work. First, the Persona Brief is the always-on identity for generated content — it defines your voice and, crucially, carries a banned-words-and-phrases list. That list is the practical home for your anti-impersonation rules: ban "I remember when I," "as a human," "I felt," "when I was younger," and any fabricated-experience phrasing, and every Text Post, Blog, Newsletter, and caption is generated against it rather than you re-pasting the rule into a fresh chat each time. Second, the quality gates check output at the boundary before anything schedules — the brand-safety gate rejects banned language at output time, so a stray human-impersonating line does not slip into a published post, and on autopilot a flagged output returns to the review queue instead of shipping. Third, for the formats where impersonation risk is highest — Persona Shorts, Persona HeyGen, and other synthetic-avatar video — the honest move is disclosure on the finished asset, and because Kompozy owns the publish step across eight social platforms plus blog and email, you can standardize an AI-content label into your posting workflow instead of remembering it per platform. The distinction Kompozy is built around matters here: a persona is a stylistic brand identity, never a claim to be a specific real human, which is precisely the line this guide draws. Starter ($99/mo for 5,500 credits) fits a solo creator hard-coding voice-and-disclosure rules once; Pro ($299/mo for 18,000 credits) suits a team running autopilot with the brand-safety gate enforcing them across a full content calendar; Enterprise is custom. Write the rule once in the brief; let the gates enforce it on everything you ship.
Language models are trained on human-written text, so their default voice is a human one — they will invent feelings, memories, and a personal history because that is what the training data sounds like. Preventing impersonation means adding explicit instructions that override that default, since nothing in the base behavior stops it.
An explicit disclosure rule: when asked whether it is human or whether a person wrote something, the AI must always state clearly that it is an AI. Phrase it as a positive instruction ("always disclose") near the top of the prompt, because that is the behavior most likely to be tested and most consequential if it fails.
Yes. A named brand persona with a consistent style is legitimate — that is a persona, not impersonation. The line is that it must never claim to be a specific real, living human, must not pose as a named employee answering personally, and must disclose it is AI when asked. A stylistic identity is fine; a false claim of specific humanity is not.
In a growing number of places, yes. The EU AI Act (Article 50, applying from August 2, 2026) requires disclosure that a user is interacting with an AI unless obvious, California's SB 1001 bans deceptive bots in commercial and electoral contexts, and China introduced anthropomorphic-AI rules in July 2026. The specifics vary, so confirm what applies to your use case.
No, and it backfires. Prefixing every reply with "As an AI…" is poor UX and unnecessary. The goal is honesty at the right moments — on first interaction and whenever asked — combined with tone that stays warm without inventing a human life, not a robotic disclaimer stapled to each line.