Datasource Schema & Configuration

{
  "entries": [
    {
      "name": "department",
      "type": "str",
      "optional": false
    },
    {
      "name": "priority",
      "type": "int",
      "optional": true
    },
    {
      "name": "version",
      "type": "str",
      "optional": false
    }
  ]
}

✅ "Customer Support FAQ"
✅ "Product Documentation v2"
✅ "Company Policies and Procedures"
❌ "DS1"
❌ "Data"

Pattern: [Topic] - [Type/Version]

Examples:
"Support Knowledge Base - Public"
"API Documentation - v3.0"
"HR Policies - 2024"
"Sales Materials - Current"

"Comprehensive knowledge base for customer support
team. Contains FAQ, troubleshooting guides, product
documentation, and common issues. Actively maintained
and updated weekly. Shared across all support agents."

By Department:
"sales", "support", "marketing", "engineering"

By Audience:
"public", "internal", "client-facing"

By Status:
"beta", "draft", "review-needed"

By Type:
"policies", "documentation", "procedures"

By Priority:
"critical", "important", "reference"

Original Owner: John Smith
Transition to: Sarah Chen
- Transfer access
- Document handoff
- Update metadata
- Notify team

Tags: marketing, sales, support, engineering
Owner: Department lead
Visibility: Team or Public

Tags: documentation, faq, procedures, policies
Description: Clearly state content type
Status: Active if current, Archived if old

Tags: customer-facing, internal, executive
Visibility: Private/Team based on audience
Owner: Audience representative

Status: Active (current), Archived (old), Deprecated (replace)
Last Updated: Recent = actively maintained
Owner: Clear responsibility

Pattern: [Audience] - [Topic] - [Version]

Examples:
"Customer Support FAQ - Public"
"Sales Materials - Current"
"HR Handbook - 2024"
"API Docs - v3.0"
"Internal Procedures - Draft"

Monthly Review:
□ Content still accurate? (Check Last Updated)
□ Owner actively maintaining? (Check Author/Status)
□ Used by agents? (Check Agent Count)
□ Any resources to archive? (Review old files)
□ Update metadata as needed?

Quick Reference Card:
- Purpose: What knowledge does it contain?
- Coverage: What topics are included?
- Audience: Who should use this?
- Owner: Who maintains it?
- Update Frequency: How often is it updated?
- Related Datasources: What complements it?
- Agents Using: Which agents reference it?

Weekly:
- Monitor for new submissions
- Quick quality check

Monthly:
- Review Last Updated date
- Check resource count
- Verify owner active

Quarterly:
- Full content audit
- Update metadata
- Archive old items
- Plan improvements

# Only search resources where department="engineering"
allowed_vectors = {
    "department": {"values": ["engineering"]}
}

# Invoke agent with filter
invoke_agent(
    agent_id="support_bot",
    input="How do I deploy?",
    allowed_vectors=allowed_vectors
)
# ↓ Agent only searches resources with department="engineering"

allowed_vectors = {
    "department": {"values": ["engineering", "devops"]},
    "version": {"values": ["2.0"]}
}
# ↓ Search only: department IN (engineering, devops) AND version=2.0

{
  "entries": [
    {"name": "department", "type": "str", "optional": false},
    {"name": "confidential", "type": "bool", "optional": true}
  ]
}

Resource 1: {"department": "sales", "confidential": false}
Resource 2: {"department": "engineering", "confidential": false}
Resource 3: {"department": "sales", "confidential": true}

allowed_vectors = {"department": {"values": ["sales"]}}
# ↓ Returns: Resource 1 and Resource 3 (both sales department)

allowed_vectors = {
    "department": {"values": ["sales"]},
    "confidential": {"values": [false]}
}
# ↓ Returns: Resource 1 only (sales + not confidential)