Protocols Algorithm

Trucast Protocol Implementation - Complete Architecture

Executive Summary

We have successfully implemented Trucast's core differentiating logic: Actor + Action + Blueprint = Protocol. This protocol-driven architecture ensures that every user interaction is properly contextualized, preserving the user's first-person perspective while leveraging Trucast's comprehensive business model ontology (ValueGraph).

Implementation Components

Core Protocol Structure (src/utilities/protocols/trucastProtocolCore.ts)

The foundation that defines:

  • 7 Core Blueprints (Business Model Archetypes)

  • Actor Types with their primary actions and business drivers

  • Protocol Assembly Engine implementing the core equation

  • Protocol State Machine for execution lifecycle

  • Protocol Discovery for finding and chaining protocols

Protocol Integration (src/utilities/protocols/protocolIntegration.ts)

Connects protocols to chat workflows:

  • Actor Detection from user message context

  • Action Extraction from natural language

  • Blueprint Determination based on domain indicators

  • First-Person Response Generation maintaining user context

  • FIS-Specific Context generation for fintech scenarios

System Prompt Enhancements

Protocol-Aware System Prompt (src/utilities/systemPromptEnhancements/protocolAwareSystemPrompt.ts)

Instructs the AI to:

  • Always identify Actor-Action-Blueprint for every request

  • Preserve first-person context

  • Execute protocols through defined workflows

  • Chain to next logical protocols

FIS-Specific Enhancements (src/utilities/systemPromptEnhancements/fisSystemPrompt.ts)

  • Recognizes "Fintech Software Provider" archetype

  • Never assumes user works for FIS

  • Focuses on value capture and revenue optimization

Workflow Implementation

WorkflowProjects (src/collections/TruWorkflowProjects.ts)

  • Container for multi-step protocol execution

  • Tracks state, inputs, outputs

  • Enables v0-like iteration and visibility

Chat Route Integration (src/app/api/ai/chat/route.ts)

  • Processes workflow operations

  • Maintains protocol context

  • Executes blocks in sequence

UI Components

  • WorkflowPanel (src/components/WorkflowPanel/index.tsx) - v0-like side panel

  • ResponseSection (src/components/ResponseSection/index.tsx) - Structured output display

  • FISShowcase (src/components/FISShowcase/index.tsx) - Demo component

Key Architecture Patterns

1. Actor-Action-Blueprint Assembly

// User says: "Help me integrate FIS for our bank"
const protocol = {
  actor: "integration-specialist",    // Detected: bank employee
  action: "integrate",               // Extracted: integration task
  blueprint: "technology-services",  // Mapped: fintech domain
  id: "tech-integration-specialist-integrate-1234567"
}

2. First-Person Context Preservation

User Context
System Response

Bank Employee

"As your bank's integration specialist..."

FIS Employee

"As an FIS solutions architect..."

Consultant

"As your independent integration advisor..."

3. Protocol Chaining

Initial Protocol → Outputs Generated → Next Protocol Suggested
integration-manifest → run-integration-tests → generate-documentation

4. ValueGraph Integration

The ValueGraph provides:

  • Business model patterns (SI revenue leakage, integration complexity)

  • Actor-action compatibility rules

  • Cross-industry protocol templates

  • GICS referential alignment

FIS Implementation Showcase

Revenue Capture

  • Traditional: FIS loses 50% margin to SIs

  • With Trucast: FIS retains 85% margin through protocol automation

Implementation Speed

  • Traditional: 16 weeks with Deloitte/Accenture

  • With Trucast: 6 weeks with full transparency

Upsell Detection

  • Automated analysis of usage patterns

  • Real-time opportunity identification

  • Protocol-driven engagement strategies

Testing the Implementation

Basic Protocol Assembly

// Test message
const message = "I need to analyze my client's portfolio";

// Expected protocol
{
  actor: "wealth-advisor",
  action: "analyze", 
  blueprint: "wealth-management",
  workflow: ["data-gathering", "risk-assessment", "performance-analysis", "recommendation"]
}

FIS-Specific Flow

// Test message
const message = "Help integrate FIS core banking for our midwest bank";

// Expected protocol
{
  actor: "integration-specialist",
  action: "integrate",
  blueprint: "technology-services",
  firstPerson: "As your bank's integration specialist, I'll guide you through FIS core banking integration..."
}

RAG/MCP-Style Protocol Reference

The system can now:

  1. Discover relevant protocols based on user queries

  2. Validate actor-action compatibility

  3. Execute through PayloadCMS blocks

  4. Chain to next logical protocols

  5. Track state in WorkflowProjects

Next Steps

  1. Expand Protocol Library: Add more actor-action-blueprint combinations

  2. Enhance Discovery: Implement semantic search for protocol matching

  3. Add Validation Rules: Business logic for protocol compatibility

  4. Create Protocol Designer: Visual tool for creating new protocols

  5. Implement Metrics: Track protocol execution success rates

Conclusion

We have successfully implemented Trucast's core differentiating logic - the protocol-driven approach that:

  • Preserves user context through actor identification

  • Leverages business model ontology for intelligent workflow assembly

  • Creates reusable, chainable protocols

  • Captures value traditionally lost to manual processes

The FIS implementation demonstrates how this architecture transforms a software vendor's business model by capturing implementation revenue while delivering superior client outcomes. This same pattern applies across all 7 business model archetypes in the Trucast ValueGraph.

PreviousReinforcement LearningNextDiagrams

Last updated

Was this helpful?