Skip to main content

​
Overview

When a user submits a prompt in nuwacom Chat or with an Agent, the system applies multiple layers of guidelines and knowledge sources. This article explains the order of precedence and how conflicts are resolved.

​
Order of Precedence

When a prompt is submitted, the system applies elements in this order (highest to lowest priority):
  1. Prompt/Agent Instruction (System Instruction): Custom Agent instructions or default system behavior. If chatting with an agent and the instructions are available, it takes it. If not, it uses the default nuwacom prompt.
  2. Tone of Voice: Writing style guidelines are applied after system instructions.
  3. Workspace Guideline (Company Guidelines): Workspace-level rules and policies. This applies to all users in the workspace.
  4. Project Guideline: Project-specific rules and constraints. More specific than workspace guidelines
  5. Private Memory: User-specific stored information. Stores personal preferences and context.
  6. Context Knowledge (Attached Files/Documents): Files attached to Chat or Agent. This often has the highest priority for context.
  7. Knowledge Base: When the knowledge-base tool is enabled on the frontend and there are matching info in the knowledge-base, it is then added.
  8. Web (External Information): Results from external web search.

​
Conflict Resolution

Some elements can override earlier ones when they conflict. Example:
  • Workspace Guideline: “Always use formal language”
  • Tone of Voice: “Use casual, friendly tone”
  • Result: Tone of Voice takes precedence

​
Information Sources: Tool-Provided Data Wins

When gathering information, those provided by tools (from Context Knowledge, Knowledge Base, or Web) always takes priority over the model’s training data.

​
Exceptions and Special Cases

If specific documents are attached to an Agent, the knowledge base search tool may be disabled to avoid redundancy.

​
Agents vs. Direct Chat Interactions

​
Agents

  • Can have custom System Instructions that override default behavior
  • Context is merged with agent-specific knowledge first, then request context
  • Some tools may be conditionally enabled based on agent configuration

​
Direct Chat

  • Uses default system instructions unless an Agent is selected
  • All workspace and project guidelines apply

​
Why This Matters

This hierarchy ensures:
  • Consistent behavior: System instructions set the foundation
  • Flexibility: Workspace and project guidelines add organizational constraints
  • Personalization: Private Memory provides user-specific context
  • Accuracy: Information retrieval tools gather current, relevant data in a defined order
The system prioritizes user instructions and tool-provided information while respecting organizational guidelines and maintaining a consistent tone.

​
Best Practices

  1. Set workspace guidelines for organization-wide policies
  2. Use project guidelines for project-specific requirements
  3. Define tone of voice at the workspace or project level for consistency
  4. Attach specific documents when you need precise information
  5. Enable knowledge base search for broader workspace knowledge
  6. Use web search for real-time or external information needs