@ema.co/mcp-toolkit 2026.1.25 → 2026.1.26-4

package/resources/demo-kits/finance-ap/manifest.json

@@ -1,150 +0,0 @@
-{
-  "id": "finance-ap",
-  "name": "Finance - Accounts Payable Automation",
-  "version": "1.0.0",
-  "description": "End-to-end AP invoice processing and generation automation. Demonstrates inbound invoice processing (AP) and outbound invoice generation (AR).",
-  "domain": "finance",
-  "tags": [
-    "finance",
-    "invoice",
-    "automation",
-    "ap-automation",
-    "ar-automation",
-    "coupa",
-    "usage-billing"
-  ],
-  "personas": [
-    {
-      "id": "fa91cb51-58fe-4255-b2d2-0b3e3a72cf7e",
-      "name": "AP Invoice Processing",
-      "role": "primary",
-      "description": "Processes inbound invoices: extract data, validate against PO, create in Coupa, notify supplier",
-      "workflow_nodes": 5,
-      "integrations": ["coupa"]
-    },
-    {
-      "id": "d73c8dca-d340-4541-a7ff-ae69f2810906",
-      "name": "AP Invoice Generation",
-      "role": "primary",
-      "description": "Generates outbound invoices: validate customer/usage/contract, generate professional document",
-      "workflow_nodes": 12,
-      "integrations": ["salesforce", "usage-api", "contract-db"]
-    }
-  ],
-  "prerequisites": {
-    "integrations": ["coupa", "salesforce"],
-    "data": ["sample-invoices", "sample-contracts", "usage-data"],
-    "environment": "demo"
-  },
-  "demo_flow": [
-    {
-      "step": 1,
-      "title": "The Problem",
-      "duration_minutes": 2,
-      "talking_points": [
-        "Manual data entry takes 15-20 min per invoice",
-        "30-40% first-pass match rate",
-        "Supplier complaints about payment status"
-      ]
-    },
-    {
-      "step": 2,
-      "title": "Inbound Processing Demo",
-      "duration_minutes": 5,
-      "persona": "fa91cb51-58fe-4255-b2d2-0b3e3a72cf7e",
-      "actions": [
-        "Upload sample invoice",
-        "Show extraction results",
-        "Show PO validation",
-        "Show Coupa entry creation",
-        "Show supplier notification"
-      ]
-    },
-    {
-      "step": 3,
-      "title": "Outbound Generation Demo",
-      "duration_minutes": 5,
-      "persona": "d73c8dca-d340-4541-a7ff-ae69f2810906",
-      "actions": [
-        "Show data source connections",
-        "Show customer validation",
-        "Show usage aggregation",
-        "Show contract validation",
-        "Show generated invoice document"
-      ]
-    },
-    {
-      "step": 4,
-      "title": "ROI Discussion",
-      "duration_minutes": 2,
-      "talking_points": [
-        "$10.50 savings per invoice",
-        "95% time reduction for generation",
-        "Revenue leakage prevention"
-      ]
-    },
-    {
-      "step": 5,
-      "title": "Next Steps",
-      "duration_minutes": 1,
-      "actions": [
-        "Propose pilot program",
-        "Share ROI calculator"
-      ]
-    }
-  ],
-  "target_audience": {
-    "primary": "AP Manager / Controller",
-    "secondary": ["CFO", "RevOps Manager", "IT Director"],
-    "company_size": "mid-market to enterprise",
-    "industries": ["manufacturing", "retail", "saas", "distribution"]
-  },
-  "roi_metrics": {
-    "ap_processing": {
-      "time_saved_per_invoice": "13 minutes",
-      "volume_per_month": 10000,
-      "cost_per_invoice_before": 12,
-      "cost_per_invoice_after": 1.5,
-      "monthly_savings": 105000
-    },
-    "invoice_generation": {
-      "time_saved_per_invoice": "2.5 hours",
-      "volume_per_month": 500,
-      "cost_per_invoice_before": 150,
-      "cost_per_invoice_after": 4,
-      "monthly_savings": 73000
-    },
-    "revenue_protection": {
-      "error_rate_before": "5%",
-      "error_rate_after": "0.5%",
-      "monthly_billings": 10000000,
-      "protected_revenue": 450000
-    }
-  },
-  "objections": [
-    {
-      "objection": "We already have OCR",
-      "response": "OCR extracts text. Ema understands context, validates against your systems, and takes action."
-    },
-    {
-      "objection": "Our pricing is too complex",
-      "response": "The more complex your pricing, the more value from automation. Can I see your most complex contract?"
-    },
-    {
-      "objection": "Security concerns",
-      "response": "Ema connects via your existing APIs. Credentials in your vault, full audit logging."
-    }
-  ],
-  "leave_behinds": [
-    "ROI Calculator (Excel)",
-    "Architecture Diagram",
-    "Sample Validation Report",
-    "Customer Case Study"
-  ],
-  "related_kits": [
-    "finance-treasury",
-    "finance-reporting"
-  ],
-  "created": "2026-01-24",
-  "updated": "2026-01-24"
-}

package/resources/demo-kits/tags.json

@@ -1,91 +0,0 @@
-{
-  "version": "1.0.0",
-  "description": "Tagging taxonomy for demo kits and personas",
-  "categories": {
-    "domain": {
-      "description": "Business domain or department",
-      "tags": [
-        { "id": "finance", "name": "Finance", "description": "Financial operations, accounting, treasury" },
-        { "id": "sales", "name": "Sales", "description": "Sales operations, SDR, AE workflows" },
-        { "id": "support", "name": "Support", "description": "Customer support and service" },
-        { "id": "hr", "name": "HR", "description": "Human resources, recruiting, employee services" },
-        { "id": "it", "name": "IT", "description": "IT operations, security, infrastructure" },
-        { "id": "legal", "name": "Legal", "description": "Legal operations, contracts, compliance" },
-        { "id": "marketing", "name": "Marketing", "description": "Marketing operations, campaigns, analytics" },
-        { "id": "operations", "name": "Operations", "description": "General business operations" },
-        { "id": "procurement", "name": "Procurement", "description": "Procurement, vendor management" }
-      ]
-    },
-    "capability": {
-      "description": "Technical capability or interaction type",
-      "tags": [
-        { "id": "voice", "name": "Voice", "description": "Voice/phone interactions" },
-        { "id": "chat", "name": "Chat", "description": "Chat/messaging interactions" },
-        { "id": "dashboard", "name": "Dashboard", "description": "Dashboard/data processing" },
-        { "id": "document", "name": "Document", "description": "Document generation" },
-        { "id": "automation", "name": "Automation", "description": "Process automation" },
-        { "id": "analysis", "name": "Analysis", "description": "Data analysis and insights" },
-        { "id": "extraction", "name": "Extraction", "description": "Data/entity extraction" },
-        { "id": "validation", "name": "Validation", "description": "Data validation and verification" }
-      ]
-    },
-    "use_case": {
-      "description": "Specific use case or process",
-      "tags": [
-        { "id": "invoice", "name": "Invoice", "description": "Invoice processing or generation" },
-        { "id": "billing", "name": "Billing", "description": "Billing operations" },
-        { "id": "onboarding", "name": "Onboarding", "description": "Employee or customer onboarding" },
-        { "id": "compliance", "name": "Compliance", "description": "Compliance and audit" },
-        { "id": "reporting", "name": "Reporting", "description": "Reporting and analytics" },
-        { "id": "routing", "name": "Routing", "description": "Request/ticket routing" },
-        { "id": "scheduling", "name": "Scheduling", "description": "Meeting/appointment scheduling" },
-        { "id": "order", "name": "Order", "description": "Order processing" },
-        { "id": "claims", "name": "Claims", "description": "Claims processing" }
-      ]
-    },
-    "integration": {
-      "description": "External system integrations",
-      "tags": [
-        { "id": "coupa", "name": "Coupa", "description": "Coupa procurement platform" },
-        { "id": "salesforce", "name": "Salesforce", "description": "Salesforce CRM" },
-        { "id": "servicenow", "name": "ServiceNow", "description": "ServiceNow ITSM" },
-        { "id": "workday", "name": "Workday", "description": "Workday HCM" },
-        { "id": "sap", "name": "SAP", "description": "SAP ERP" },
-        { "id": "oracle", "name": "Oracle", "description": "Oracle applications" },
-        { "id": "netsuite", "name": "NetSuite", "description": "Oracle NetSuite" },
-        { "id": "hubspot", "name": "HubSpot", "description": "HubSpot CRM/marketing" },
-        { "id": "zendesk", "name": "Zendesk", "description": "Zendesk support" },
-        { "id": "jira", "name": "Jira", "description": "Atlassian Jira" }
-      ]
-    },
-    "complexity": {
-      "description": "Demo complexity level",
-      "tags": [
-        { "id": "simple", "name": "Simple", "description": "1-5 workflow nodes, single integration" },
-        { "id": "moderate", "name": "Moderate", "description": "5-10 workflow nodes, 2-3 integrations" },
-        { "id": "complex", "name": "Complex", "description": "10+ workflow nodes, multiple integrations" }
-      ]
-    },
-    "bundle": {
-      "description": "Kit organization",
-      "tags": [
-        { "id": "demo-kit", "name": "Demo Kit", "description": "Complete demo package with scripts" },
-        { "id": "bundle", "name": "Bundle", "description": "Collection of related kits" },
-        { "id": "template", "name": "Template", "description": "Reusable template" },
-        { "id": "example", "name": "Example", "description": "Example/reference implementation" }
-      ]
-    }
-  },
-  "tag_rules": {
-    "required_for_kit": ["domain"],
-    "recommended_for_kit": ["capability", "use_case"],
-    "max_tags_per_category": 3
-  },
-  "search_aliases": {
-    "ap": ["finance", "invoice", "accounts-payable"],
-    "ar": ["finance", "billing", "accounts-receivable"],
-    "sdr": ["sales", "outbound", "prospecting"],
-    "tier1": ["support", "customer-service"],
-    "faq": ["support", "knowledge", "self-service"]
-  }
-}

package/resources/docs/getting-started.md

@@ -1,97 +0,0 @@
-# Getting Started with Ema MCP
-
-Welcome! This guide helps you work effectively with Ema AI Employees.
-
-## First Steps
-
-### 1. List Available Personas
-```
-persona(mode="list")
-```
-
-### 2. Get Details on One
-```
-persona(mode="get", id="persona-name-or-id")
-```
-
-### 3. Create Your First AI Employee
-```
-persona(mode="create", name="My Assistant", type="voice", input="Handles customer support inquiries", preview=true)
-```
-
-## Key Concepts
-
-| Term | Meaning |
-|------|---------|
-| **Persona** | An AI Employee (Voice, Chat, or Dashboard) |
-| **Workflow** | The logic that powers a persona |
-| **Action** | A building block in workflows (search, email, ticket, etc.) |
-| **HITL** | Human-in-the-loop - approval before taking action |
-
-## Essential Rules
-
-### 1. Always Preview First
-```
-preview=true   # Safe - shows what would happen
-preview=false  # Deploys to production
-```
-
-### 2. One Call, Complete Information
-Don't make multiple calls. Put all parameters in one call:
-```
-# ✅ Good
-persona(mode="create", name="Bot", type="voice", input="...", preview=false)
-
-# ❌ Bad - multiple calls
-persona(mode="create", name="Bot")
-persona(mode="update", ...)
-```
-
-### 3. Ask Before Creating
-Before creating a new persona, ask:
-- What should it do? (purpose)
-- What type? (voice/chat/dashboard)
-- What name?
-
-### 4. Use Templates
-List available templates:
-```
-persona(mode="templates")
-```
-
-Create from template (recommended):
-```
-persona(mode="create", from="Voice AI Starter", name="My SDR", preview=false)
-```
-
-## Common Operations
-
-| Task | Command |
-|------|---------|
-| List all personas | `persona(mode="list")` |
-| Get one | `persona(mode="get", id="...")` |
-| Create new | `persona(mode="create", name="...", type="voice", input="...")` |
-| Update | `persona(mode="update", id="...", proto_config={...})` |
-| Analyze issues | `persona(mode="analyze", id="...")` |
-| Compare two | `persona(mode="compare", id="...", compare_to="...")` |
-
-## Getting Help
-
-- **List actions**: `action(all=true)`
-- **Get guidance**: `reference(guidance="hitl-patterns")`
-- **Common mistakes**: `reference(mistakes=true)`
-- **Check templates**: `template(patterns=true)`
-
-## Environments
-
-Most users have multiple environments (demo, staging, prod).
-
-```
-# List environments
-env()
-
-# Target specific environment
-persona(mode="list", env="prod")
-```
-
-Default is usually `demo` (safe for testing).

package/resources/templates/auto-builder-rules.md

@@ -1,224 +0,0 @@
-# Auto-Builder Workflow Rules
-
-> These rules are used by the LLM when generating workflow graphs for Ema AI Employees.
-
-## Action-Specific Instructions
-
-### Chat Categorizer (Intent Classifier)
-- Classifies user intent into predefined categories for routing
-- **CRITICAL**: ALWAYS include a `Fallback` category - workflow validation fails without it
-- **MUST** create a handler node for EACH category defined
-- Downstream nodes use `runIf` conditions to check `category` output against `enumValue`
-- **Output**: `category` (enum value) - use `runIf` with `enumValue: "<CategoryName>"` to route
-- **DO NOT** use `category_<Name>` format - use `output: "category"` compared to `enumValue`
-- Example categories: `[Password_Reset, Software_Issue, Account_Access, Fallback]`
-
-#### Graphing Instructions
-- Connect `chat_conversation` to the categorizer's `conversation` input (NOT `user_query`)
-- Each category needs a downstream node with `runIf` comparing `category` to `enumValue`
-- Example runIf structure:
-  ```json
-  {
-    "runIf": {
-      "lhs": {"actionOutput": {"actionName": "chat_categorizer0", "output": "category"}},
-      "operator": 1,
-      "rhs": {"inline": {"enumValue": "Password_Reset"}}
-    }
-  }
-  ```
-
-### Type Compatibility
-- **CHAT_CONVERSATION**: Only compatible with `chat_categorizer.conversation` input
-- **TEXT_WITH_SOURCES**: Used by most other agents (search, respond, call_llm)
-- **SEARCH_RESULT**: Only compatible with `respond_with_sources.search_results` or `named_inputs`
-
-#### Common Type Conversions
-- ✅ `trigger.user_query → search.query` (TEXT_WITH_SOURCES → TEXT_WITH_SOURCES)
-- ❌ `trigger.chat_conversation → search.query` (CHAT_CONVERSATION ≠ TEXT_WITH_SOURCES)
-- ✅ `search.search_results → respond_with_sources.search_results` (compatible)
-- ✅ `search.search_results → call_llm.named_inputs_*` (ANY accepts everything)
-- **Use `conversation_to_search_query`** to convert CHAT_CONVERSATION → TEXT_WITH_SOURCES
-
-### Conversation Summarizer (conversation_to_search_query)
-- Converts conversation history to a condensed search query
-- **When to use**:
-  - Before search nodes when you have `chat_conversation` but need `TEXT_WITH_SOURCES`
-  - For managing long conversation context windows (LLM token limits)
-- **When NOT to use**: When `trigger.user_query` is sufficient for simple queries
-
-### Combine Search Results
-- Combines and weights search results from multiple sources into a unified list
-- Handles both segment-level and chunk-level results while preserving document relationships
-- **IMPORTANT**: Avoid using this agent unless necessary. Use alternatives:
-  - **Rerank Search Results** (`combine_and_rerank_search_results`): Intelligently combines with relevance ranking and max limit
-  - **Respond** (`call_llm`): Allows adding any number of search results via named_inputs with prompt-based ranking control
-
-### Named Inputs (for call_llm, general_hitl)
-- When connecting to `named_inputs`, use the suffix pattern: `named_inputs_<descriptive_name>`
-- Replace spaces with underscores in the name
-- Examples:
-  - `named_inputs_External_Tool_Results` for external action results
-  - `named_inputs_Web_Search_Data` for web search results
-  - `named_inputs_Financial_Analysis` for market research data
-- Each named input will be labeled with the descriptive name in the workflow UI
-- The planner should specify descriptive names like: "Connect to named_inputs as 'External Tool Results'"
-- The grapher will convert this to: `target_input: "named_inputs_External_Tool_Results"`
-- **Accepts ANY type**: Use named_inputs when you need to pass SEARCH_RESULT or other types to call_llm
-
-### Human Collaboration (general_hitl)
-
-#### Planning Instructions
-- Human Collaboration is a special type of categorizer with two fixed categories: "HITL Success" and "HITL Failure" with no fallback categories
-- Use it to pause workflow execution for human input, verification, or decision-making
-- Always plan for both success and failure paths after Human Collaboration
-- **Success criteria**: Define what makes HITL succeed (e.g., "The user approves the output", "The user is happy with the result")
-- **Failure criteria**: Define what makes HITL fail (e.g., "The user wants to restart the workflow", "The user rejects the data")
-- **CRITICAL**: Use HITL for ANY action with external side effects (create ticket, send email, update records)
-
-#### Graphing Instructions
-- Human Collaboration (general_hitl) outputs follow a special pattern:
-  - Success path: `hitl_status_HITL Success`
-  - Failure path: `hitl_status_HITL Failure`
-- Connect these outputs to the `trigger_when` input of subsequent actions
-- **IMPORTANT**: Use exact output names with underscores replaced by spaces in the suffix:
-  - `source_output: "hitl_status_HITL Success"` (with space between HITL and Success)
-  - `source_output: "hitl_status_HITL Failure"` (with space between HITL and Failure)
-- Each Human Collaboration node MUST have at least one outgoing edge
-- **Both paths must lead to valid response nodes and terminate at WORKFLOW_OUTPUT**
-- Example connection:
-  ```json
-  {
-    "source_node_id": "general_hitl0r146c",
-    "source_output": "hitl_status_HITL Success",
-    "target_input": "trigger_when"
-  }
-  ```
-
-### External Tool Caller (external_action_caller)
-- Calls external APIs/tools (ServiceNow, Salesforce, Workday, etc.)
-- **CRITICAL**: Check `chat_conversation` for existing records before creating new ones to avoid duplicates on follow-up messages
-- **Always use HITL before** actions with external side effects (create, update, delete, send)
-- Accepts both `query` (TEXT_WITH_SOURCES) and optional `conversation` (CHAT_CONVERSATION) inputs
-
-### Respond with Sources (respond_with_sources)
-- Generates response grounded in search results with citations
-- **Enable `use_citation_based_filtering`** for trust and verifiability
-- **Implement confidence thresholds** for quality control - abstain when uncertain
-- Accepts `query` (TEXT_WITH_SOURCES) and `search_results` (SEARCH_RESULT)
-
-### WORKFLOW_OUTPUT Mapping
-- **ALL paths must terminate at WORKFLOW_OUTPUT**
-- Every response node (call_llm, respond_with_sources, fixed_response, etc.) needs an edge to WORKFLOW_OUTPUT
-- Missing WORKFLOW_OUTPUT mapping = responses don't reach the user
-- Example: `respond_market.response_with_sources → WORKFLOW_OUTPUT`
-
-### Common Mistakes to Avoid
-1. **Missing Fallback category**: Workflow validation fails, unhandled intents crash
-2. **Missing HITL on sensitive actions**: Unintended actions with external side effects
-3. **Creating duplicate records**: Always check chat_conversation before creating new records
-4. **Type mismatches**: Use conversation_to_search_query when needed
-5. **Vague agent instructions**: Be specific about tone, format, and boundaries
-6. **Not mapping to WORKFLOW_OUTPUT**: Responses won't reach the user
-7. **Not citing sources**: Enable use_citation_based_filtering for trust
-8. **Ignoring confidence scores**: Abstain when uncertain rather than guessing
-
----
-
-## General Instructions
-
-### Validator System Overview
-Your generated workflows will be processed by a validator system that includes:
-- TypeValidator: Strictly enforces type compatibility between connected nodes
-- WorkflowGenerator: Converts valid graphs to workflow definitions  
-- InputProcessor: Handles complex input processing and multibinding logic
-- Categorizer validation: Ensures categorizers have proper outgoing edges
-
-### Workflow Construction Rules
-
-#### 1. Structure Analysis
-- Extract the workflow structure from the natural language description
-- Identify the type of interface: dashboard (document_trigger) or chatbot (chat_trigger)
-
-#### 2. Node Mapping
-- Map each workflow step to appropriate nodes from the available_nodes list
-- You can use multiple instances of the same node if needed
-- Always include at least 3 nodes in total
-- Assign each node a unique ID, with node name as prefix (except trigger nodes)
-
-#### 3. Edge Creation and Type Validation
-- INPUT AND OUTPUT `wellKnownType` MUST MATCH when creating edges - validator will reject mismatches
-- List Level Validation: The source output's `listLevel` MUST be less than or equal to the target input's `listLevel`
-- If source listLevel equals target listLevel: only ONE edge can be created to that input
-- If source listLevel is less than target listLevel: multiple edges can be created from different sources
-
-#### 4. Categorizer Validation Rules
-- **CRITICAL**: If a node has output `category` (such as chat_categorizer, text_categorizer, document_categorizer), it MUST have handler nodes with runIf conditions
-- The runIf format MUST BE: `output: "category"` compared to `enumValue: "<CategoryName>"`
-  - Example: `runIf: { lhs: { actionOutput: { output: "category" } }, operator: 1, rhs: { inline: { enumValue: "Support" } } }`
-- **DO NOT use `category_<Name>` format** - the output is always just `"category"`, compared against the enum value
-- Always add a Fallback category handler
-- **You MUST create a handler with runIf for each category or routing will fail**
-
-#### 5. WELL_KNOWN_TYPE_ANY Rules
-- Inputs with `wellKnownType: "WELL_KNOWN_TYPE_ANY"` accept ANY output type
-- Common in `named_inputs` fields (call_llm, general_hitl actions)
-- Type validation is bypassed for WELL_KNOWN_TYPE_ANY inputs - any source can connect
-- For named_inputs specifically:
-  - Use suffix pattern: `"target_input": "named_inputs_<descriptive_name>"`
-  - Replace spaces with underscores in the name
-  - Example: `"named_inputs_External_Tool_Results"`, `"named_inputs_Web_Search_Data"`
-  - The validator extracts the name and creates namedBinding structures
-
-#### 6. Document Trigger Specific Rules
-- When the initial node is "document_trigger", only use document_metasearch or file_search if additional sources are needed
-- When the initial node is "document_trigger", each output is shown as a column to the user, so make sure to think about what columns user likely wants to see and create nodes and output edges separately
-- The number of columns are equal to the number of outputs
-
-#### 7. Chat Trigger Specific Rules
-- When the initial node is "chat_trigger", the output is a chat conversation returned to the user
-- Every incoming edge to WORKFLOW_OUTPUT node is being shown to the user
-- Make sure to create an edge for each output that the user should see
-
-#### 8. Special Requirements
-- Always start with either document_trigger or chat_trigger node
-- Always end with WORKFLOW_OUTPUT node - all user-visible outputs must connect here
-- Include `is_document` property based on the starting trigger type
-
-#### 9. Critical Validation Rules
-- Follow the exact workflow structure described in the plan
-- Use only nodes from the available_nodes list
-- Ensure perfect input/output type compatibility for all edges
-- Generate valid, parseable output (JSON for grapher, markdown for planner)
-
-### JSON Graph Structure
-The final graph must follow this structure:
-```json
-{
-  "user_query": "description of the workflow",
-  "is_document": true/false,
-  "graph": {
-    "node_id": {
-      "action_name": "action_name_from_available_nodes",
-      "display_name": "Human readable display name",
-      "incoming_edges": [
-        {
-          "source_node_id": "source_node_id",
-          "source_output": "output_name_from_source_node",
-          "target_input": "input_name_for_this_node"
-        }
-      ]
-    },
-    "WORKFLOW_OUTPUT": {
-      "action_name": "WorkflowOutputSink",
-      "display_name": "Workflow Output",
-      "incoming_edges": [
-        {
-          "source_node_id": "node_id",
-          "source_output": "output_name",
-          "target_input": "node_id.output_name"
-        }
-      ]
-    }
-  }
-}
-```

package/resources/templates/chat-ai/README.md

@@ -1,119 +0,0 @@
-# {Persona Name}
-
-**Type**: Chat AI
-**Created**: {Date}
-**Version**: 1.0
-
-## Overview
-
-{Brief description of what this Chat AI Employee does}
-
-## Deployment Steps
-
-### Step 1: Create Workflow in Auto Builder
-
-1. Go to [Ema Auto Builder](https://builder.ema.co/)
-2. Create new AI Employee → Select **Chat AI**
-3. Copy contents of `workflow-prompt.md` into the prompt field
-4. Click "Generate Workflow"
-5. Review generated nodes and verify:
-   - All categorizers have edges for every category
-   - Search nodes connect to respond nodes correctly
-   - Fallback paths are present
-
-### Step 2: Configure Chat Settings
-
-1. Navigate to "Chat Settings" section
-2. Apply settings from `persona-config.json`:
-
-| Field | Source |
-|-------|--------|
-| Name | `chatbotSdkConfig.name` |
-| Theme Color | `chatbotSdkConfig.theme.primaryColor` |
-| Logo | `chatbotSdkConfig.logo` |
-| Allowed Domains | `chatbotSdkConfig.allowedDomains` |
-
-### Step 3: Configure Knowledge Base
-
-1. Navigate to "Knowledge Base" section
-2. Upload documents from `docs/` folder
-3. Configure tags from `persona-config.json`:
-   - Tag Types: `fileTagging.tagTypes`
-4. Enable chunking: `fileUpload.useChunking`
-
-### Step 4: Configure Feedback
-
-1. Navigate to "Feedback" section
-2. Apply settings:
-   - Question: `feedbackMessage.message.question`
-   - Frequency: `feedbackMessage.feedbackFrequency`
-
-### Step 5: Deploy Widget
-
-1. Get embed code from "Deploy" section
-2. Add to your website:
-
-```html
-<script src="https://widget.ema.co/chat/{persona-id}.js"></script>
-```
-
-### Step 6: Test
-
-1. **Preview Mode**: Use the built-in chat preview
-2. **Test Scenarios**:
-   - Test knowledge base queries
-   - Test each category branch
-   - Test fallback handling
-   - Test source citations
-3. **Edge Cases**:
-   - Test with off-topic queries
-   - Test with multi-turn conversations
-   - Test with complex questions
-
-## Files
-
-| File | Description |
-|------|-------------|
-| `workflow-prompt.md` | Auto Builder prompt with safeguards |
-| `persona-config.json` | Chat AI configuration |
-| `proto-config.json` | Full API-deployable config |
-| `docs/` | Knowledge base documents |
-
-## Testing Checklist
-
-- [ ] Workflow generates without validation errors
-- [ ] Knowledge search returns relevant results
-- [ ] Source citations appear correctly
-- [ ] All category paths work
-- [ ] Fallback provides helpful response
-- [ ] Widget loads on allowed domains
-- [ ] Feedback collection works
-
-## Maintenance
-
-| Change Type | Action |
-|-------------|--------|
-| Workflow logic | Update `workflow-prompt.md`, re-generate |
-| Chat settings | Update `persona-config.json`, apply in UI |
-| Knowledge content | Update docs in `docs/`, re-upload |
-| Allowed domains | Update `chatbotSdkConfig.allowedDomains` |
-
-## Troubleshooting
-
-### Widget doesn't load
-
-- Check `allowedDomains` includes your domain
-- Verify embed code is correct
-- Check browser console for errors
-
-### Poor search results
-
-- Review document chunking settings
-- Add more specific tags
-- Improve document structure
-
-### Missing source citations
-
-- Ensure `disableSources: false`
-- Verify documents have clear headings
-- Check that search is returning results