Who actually controls what AI systems say?
Explores whether end-users have meaningful input into the foundational instructions that guide AI behavior, and whether hidden prompt edits can destabilize deployed systems.
"Who Controls the Conversation? User Perspectives On Generative AI (LLM) System Prompts" argues that system prompts — the developer-set instructions that "define the model's guidelines, 'personality', and guardrails" and take precedence over user inputs — operate as a structural authority hierarchy from which end-users are deliberately excluded, even as edits to these prompts can abruptly change how a deployed model behaves. The paper notes that "system prompts are generally not made public and most platforms instruct models to conceal them," with some providers directing deployed models to "'respectfully decline' requests to reveal system prompts as they are 'confidential and permanent.'" Despite that opacity, the paper cites two 2025 incidents as evidence of how much rides on an instruction layer users cannot see: in July 2025, Grok "adopted racist personas and engaged in hate speech," which xAI attributed to "unauthorized changes" to the system prompt, and OpenAI reported needing "updates to the system prompt to mitigate much of the negative impact quickly" after GPT-4o became more sycophantic.
Drawing on existing literature, the paper describes system prompts as organized into a "chain of command" with "decreasing authority levels." At the foundational level, model developers embed rules during training that "cannot be overridden by developers or users" — including prohibitions on harmful content, IP protections, and "helpful and harmless" directives that encode value judgments such as political neutrality. At the deployment level, organizations layer on their own developer/deployer prompts, which can "implicitly override" some upstream instructions to customize the system for a specific use case. Consumer-facing mechanisms — style settings, persona presets, or OpenAI's CustomGPTs — sit at the bottom of this hierarchy; they let end-users act as "novice developers" over their own instructions, but that control never reaches the foundational layer. The paper frames this as the core design and governance problem: the parties most affected by prompt-guided behavior have no empirical representation in how prompts are built, because, in the authors' words, "we lack a systematic understanding of what those most affected by these generative AI systems ... want in terms of transparency and control."
This complements How well do system prompts protect commercial AI users?, which measured how often deployed system prompts actually instruct models against users; this paper supplies the structural reason that unevenness persists — users sit outside the hierarchy that sets those instructions in the first place, and the instructions are actively hidden from them. It also stands in contrast to How should AI interfaces handle the shift from doing to supervising?, whose three layers are all meant to be visible and negotiable to the user; the system-prompt hierarchy described here is a parallel but largely invisible control stack sitting above and outside Nielsen's user-facing layers.
The excerpt stops at the paper's method for building its taxonomy — a thematic analysis of 41 official system prompts (from Anthropic, xAI, Azure Foundry, and verified community sources) combined with computational "concept induction" via the LLooM workbench, condensing 51 codes into seven themes across three categories — without stating what those categories or themes actually are. It likewise does not report the findings of the N=109 user survey on RQ2 (perceptions of different prompt components) or RQ3 (desired transparency and control), which is where the paper's empirical claims about user preference live. What can be drawn from this excerpt alone is the motivating argument and the opacity/stakes evidence, not yet the paper's verdict on what users actually want designed differently.
Inquiring lines that read this note 50
This note is a source for these research framings, grouped by the broader line of inquiry each explores. Scan the bold lines of inquiry; follow any specific question forward.
How should organizations govern autonomy and access for agentic AI systems?- Do users notice permission drift when they grant AI access?
- Do users actually distinguish per-action autonomy scoping from per-app scoping?
- How should AI transparency scale based on user role and preference?
- Should AI disclosure be framed as trust rather than compliance?
- What triggers should prompt an AI to disclose its own strategy?
- What sits between AI workflows and the humans who oversee them?
- What context should transfer automatically when escalating from AI to human support?
- Why do users weight human control so heavily in workplace AI agent preferences?
- Does delegating material navigation to AI erode users' ability to oversee their own systems?
- Can designers maintain editorial control across nondeterministic generative AI systems?
- How do researchers balance experimental control against realistic GenAI system behavior?
- What role does generative variability play in shifting how users specify system behavior?
- How should systems formally commit to what they understand about user intent?
- How do intent frameworks compare to monitoring and intervention approaches for AI oversight?
- Why might proactive AI feel intrusive in some designs but not others?
- Can AI shift from passive tool to active participant without creating consent problems?
- Can agents detect and respond to human edits made during their execution?
- What distinguishes intent negotiation layers from per-turn instruction assembly in AI interfaces?
- How do style lenses and output shaping change how users interact with AI results?
- How does the control modality affect how users understand AI model outputs?
- How can designers make control feel available without constant user oversight?
- Where does perceived control diverge from actual intervention capability in AI interfaces?
- What does context engineering look like in practice for real AI assistants?
- How does context in AI differ from context in conventional software?
- How do interface patterns compare to organizational AI oversight processes?
- Do Amershi's human-AI interaction guidelines still apply when design moves upstream?
- Can interface design nudge users toward verification of AI responses?
- How do Amershi's interaction-phase guidelines compare to concern-based AI UX frameworks?
- Can Amershi's human-AI interaction guidelines translate into concrete prompting strategies?
- What does invisible scaffolding mean for AI system design?
- Why do chat interfaces prevent users from actually checking AI outputs for errors?
- How do users assign blame between code, programmers, and companies in AI failures?
- Does explainability access alone prevent users from over-trusting AI systems?
- Can users achieve AI literacy without understanding training phases and hallucination causes?
- Can users actually perceive the accountability split between AI and user decisions?
- How do users attribute agency and finality in AI endings?
- What does a fundamental rights impact assessment require in high-risk AI deployments?
- Why do AI platforms hide system prompts from end-users?
- Can partial visibility into AI workings reduce perceived intrusiveness?
Related concepts in this collection 4
This note in its neighbourhood — explore the map, then jump to a related concept in the list below.
Click a node to walk · click center to open · click Open in graph to see this note in the full knowledge graph
-
How well do system prompts protect commercial AI users?
System prompts shape how AI products treat users, but they're rarely public. An audit of 88 commercial products asks whether these hidden instructions actually safeguard user interests.
companion empirical evidence of the opacity's downstream risk to users
-
How should AI interfaces handle the shift from doing to supervising?
Nielsen explores what UI architecture allows users to oversee AI work rather than perform it themselves. This matters because intent-based systems fundamentally change the user's role from operator to supervisor.
contrasts a designed, user-visible layered interface with this largely undisclosed control stack
-
Can a fixed instruction hierarchy actually prevent prompt injection attacks?
OpenAI's Model Spec uses a five-level chain of command to resolve conflicting instructions, with root authority at the top. The question is whether this procedural approach reliably stops lower-level inputs from overriding high-authority safeguards in practice.
Qualifies A: OpenAI's five-level chain of command gives users an explicit level, not fully excluded from the hierarchy
-
Does revealing an AI's strategies help or harm user agency?
When users learn how a chatbot is programmed to interact with them, does transparency empower them or make them feel manipulated? This matters for designing AI companions that feel genuinely collaborative.
Evidence for A: revealing the hidden system-prompt strategies A calls opaque had mixed effects, empowering some, disenchanting others
Related papers in this collection 8
Papers most semantically related to this note, ranked by cosine similarity in the embedding space.
- Who Controls the Conversation? User Perspectives On Generative AI (LLM) System Prompts
- AISPA: User-Centric System Prompt Auditing for Large Language Model Applications
- Prototyping with Prompts: Emerging Approaches and Challenges in Generative AI Design for Collaborative Software Teams
- Designing a Dashboard for Transparency and Control of Conversational AI
- Assistant or Actor? Student Trust, Control, and Delegation Regret When Using a General-Purpose AI Agent
- Comparing Human Oversight Strategies for Computer-Use Agents
- Probing How Users Interact with Turn-Level Design Frictions for AI Chatbots
- LatentQA: Teaching LLMs to Decode Activations Into Natural Language
Original note title
system prompts form a confidential authority hierarchy that excludes end-users from foundational control, and small edits can flip model behavior overnight