Skip to main content

Veritas Integration

Veritas is SO1’s curated prompt library containing 255 validated prompts. Agents both consume prompts (for context and patterns) and produce prompt drafts (from learned patterns).

What is Veritas?

Veritas is a structured prompt library that provides:
  • Reusable prompt fragments for common tasks
  • Versioned and validated prompts
  • Domain-organized content
  • Bidirectional integration with agents
┌────────────────────────────────────────────────────────────────┐
│                        VERITAS LIBRARY                          │
├────────────────────────────────────────────────────────────────┤
│                                                                │
│   ┌─────────────┐  ┌─────────────┐  ┌─────────────┐           │
│   │    Task     │  │  Fragment   │  │    Chain    │           │
│   │   Prompts   │  │   Prompts   │  │   Prompts   │           │
│   │    (120)    │  │    (85)     │  │    (50)     │           │
│   └─────────────┘  └─────────────┘  └─────────────┘           │
│                                                                │
│   Organization: domain → purpose → version                     │
│                                                                │
└────────────────────────────────────────────────────────────────┘

Prompt Categories

Single-purpose instructions for specific tasks.Example ID: vrt-a1b2c3d4
{
  "id": "vrt-a1b2c3d4",
  "category": "task",
  "domain": "automation",
  "purpose": "n8n workflow design patterns",
  "version": "1.0.0",
  "content": "When designing n8n workflows, follow these patterns:\n1. Use webhook triggers for external events\n2. Include error handling nodes after each action\n3. Add retry logic with exponential backoff..."
}
Used by: Single agents for specific operations

Agent Configuration

Each agent declares its Veritas integration in YAML frontmatter:
veritas:
  consumes:
    - id: "vrt-a1b2c3d4"
      purpose: "Workflow design patterns"
    - id: "vrt-e5f6g7h8"
      purpose: "Error handling best practices"
  produces:
    - category: task
      output_path: "veritas/agent-prompts/automation/"

Consuming Prompts

Agents reference prompts by their Veritas ID:
FieldDescription
idUnique Veritas ID (format: vrt-xxxxxxxx)
purposeWhy this agent uses this prompt

Producing Prompts

When agents discover novel patterns:
FieldDescription
categoryType: task, fragment, or chain
output_pathWhere draft prompts are saved

Prompt Flow

                    ┌─────────────────┐
                    │  VERITAS CORE   │
                    │  (255 prompts)  │
                    └────────┬────────┘

              ┌──────────────┼──────────────┐
              │              │              │
              ▼              ▼              ▼
       ┌──────────┐   ┌──────────┐   ┌──────────┐
       │ Workflow │   │  Prompt  │   │  Hono    │
       │ Architect│   │ Refiner  │   │ Backend  │
       └────┬─────┘   └────┬─────┘   └────┬─────┘
            │              │              │
            └──────────────┼──────────────┘


                    ┌─────────────────┐
                    │  AGENT DRAFTS   │
                    │ (pending review)│
                    └────────┬────────┘


                    ┌─────────────────┐
                    │  HUMAN REVIEW   │
                    │   (approve/     │
                    │    reject)      │
                    └────────┬────────┘


                    ┌─────────────────┐
                    │  VERITAS CORE   │
                    │   (promoted)    │
                    └─────────────────┘

Prompt ID Format

Veritas IDs follow a consistent format:
vrt-xxxxxxxx

Where:
- vrt- : Veritas prefix
- xxxxxxxx : 8-character alphanumeric identifier
Examples:
  • vrt-a1b2c3d4 - Workflow patterns
  • vrt-wh001xyz - Webhook security
  • vrt-chain001 - Design chain

Prompts by Domain

Prompt IDPurposeUsed By
vrt-a1b2c3d4Workflow design patternsWorkflow Architect
vrt-e5f6g7h8Error handlingWorkflow Architect
vrt-wh001Webhook patternsWebhook Engineer
vrt-sec001Webhook securityWebhook Engineer
vrt-cron01Cron patternsSchedule Optimizer
vrt-tz01Timezone handlingSchedule Optimizer
Prompt IDPurposeUsed By
vrt-hono01Hono patternsHono Backend
vrt-zod01Zod validationHono Backend
vrt-next01Next.js patternsNext.js Frontend
vrt-react01React patternsNext.js Frontend
Prompt IDPurposeUsed By
vrt-meta001Meta-promptsPrompt Refiner
vrt-clarity01Clarity patternsPrompt Refiner
vrt-chain001Chain patternsChain Architect
vrt-flow001Data flowChain Architect
vrt-fragment001Fragment patternsFragment Curator
vrt-compose01CompositionFragment Curator
Prompt IDPurposeUsed By
vrt-incident01PlaybooksIncident Commander
vrt-comms01CommunicationsIncident Commander
vrt-triage01Triage patternsTriage Responder
vrt-symptoms01Symptom mappingTriage Responder
vrt-rca01RCA frameworksPostmortem Analyst
vrt-5whys015 Whys techniquePostmortem Analyst

Draft Prompt Schema

Agent-produced drafts must conform to this schema:
{
  "$schema": "veritas-draft-schema.json",
  "metadata": {
    "source_agent": "workflow-architect",
    "discovered_at": "2024-01-15T10:30:00Z",
    "context": "Learned while designing retry patterns"
  },
  "prompt": {
    "category": "fragment",
    "domain": "automation",
    "purpose": "Exponential backoff configuration",
    "content": "For retry logic, use exponential backoff:\n- Initial delay: 1 second\n- Multiplier: 2x\n- Max retries: 5\n- Max delay: 60 seconds"
  },
  "status": "draft"
}

Review Process

  1. Agent produces draft → saved to veritas/agent-prompts/
  2. Human reviews → checks accuracy, relevance, quality
  3. Approval → promoted to Veritas core with new ID
  4. Rejection → feedback provided, draft deleted or revised

Validation

Veritas integration is validated during agent checks:
./scripts/validate-agents.sh

# Checks:
# ✓ veritas.consumes defined
# ✓ Prompt IDs match format (vrt-xxxxxxxx)
# ✓ veritas.produces has valid category
# ✓ output_path exists