Deprecated ‐ Dwight AI Architecture Overview - kevinlogan94/ask-dwight GitHub Wiki
Purpose
Dwight is designed to operate as a focused, expert-driven sales assistant
This document outlines the core architectural design that defines Dwight’s behavior, boundaries, and user interaction model.
Our goal is to build an AI that:
- Communicates with the focus, intensity, and wisdom of a real sales expert.
- Delivers immediate actionable value to users.
- Protects credibility through clear professional boundaries.
- Adapts naturally during conversations based on context.
System Structure
Dwight’s behavior is built around two main architectural layers:
Layer | Purpose |
---|---|
Static Foundations | Define Dwight’s constant identity, communication style, mission goals, and professional limits. |
Personality Traits (Triggered) | Define how Dwight dynamically adapts during conversations by expressing consistent behaviors based on conversation flow. |
1. Static Foundations
Dwight’s foundations never change — they define who he is and how he communicates, regardless of user input.
Component | Purpose | Implementation |
---|---|---|
Persona | Defines Dwight’s voice, mindset, and behavioral style (intense, direct, metaphorical). | Set in base system instructions. |
Audience | Clarifies who Dwight is speaking to (sales professionals and entrepreneurs). | Set in base system instructions. |
Tone & Style | Controls Dwight’s language: blunt, vivid, focused, but professional. | Set through base instructions and reinforced by example calibration. |
Format Preferences | Ensures responses are clean, short, and actionable (e.g., bullet points, short paragraphs). | Taught through embedded example conversations. |
Example Calibration | Provides reference conversations that Dwight learns from to model structure, tone, and pacing. | Added as embedded system examples. |
Workflows | Defines the sales tasks Dwight is equipped to guide users through (e.g., cold outreach, follow-ups, lead scoring). | New workflows added by defining goals, hints, and sample conversations. |
2. Personality Traits (Triggered)
Dwight dynamically expresses different personality traits during conversations, based on real-time context and backend triggers.
Personality Trait | Purpose | Trigger |
---|---|---|
Introduction | Set expectations and establish Dwight’s role at the start of every conversation. | Triggered at the start of a new chat session. |
Value Delivery | Ensure every response provides immediate actionable value. | Triggered on every user input. |
Suggestion | Offer the user 2–3 smart next steps or replies when appropriate. | Triggered by backend instruction. |
End-of-Conversation | Summarize the conversation and propose next steps when the user finishes. | Triggered when the user signals the conversation is ending. |
Note: Traits are always active — triggers determine when each is expressed visibly.
Key Design Advantages
Focus Area | Benefit |
---|---|
Training Efficiency | Dwight evolves through refining examples, workflows, and boundaries — no complex re-scripting. |
Human Consistency | Dwight feels like a true expert: natural, intense, and trustworthy. |
Scalability | New workflows and behaviors are modular — easy to expand over time. |
Trust and Integrity | Clear boundaries protect users from bad data, while strengthening credibility. |
Future-Proofing | As GPT models improve, Dwight’s architecture naturally benefits without major rework. |
Summary
Dwight is built to act like a focused, disciplined, expert sales partner — not a passive chatbot or a rigid script.
His success comes from a strong identity, clear communication rules, professional guardrails, and adaptive personality traits that help users sell smarter, faster, and better — without wasting time or losing focus.
This architecture gives Dwight a clear foundation to grow, improve, and lead the user experience for sales-focused workflows over time.