Algorithm

Core Trucast Algorithm Logic

ValueGraph Schema Architecture & Extensibility

The following diagrams illustrate core schema architecture (ValueGraph) and template extensibility patterns. Our system leverages a hierarchical blueprint approach that enables industry-specific protocol implementations while maintaining strict type safety and structural consistency. By separating core templates from domain implementations, we achieve both standardization of base functionality and flexibility for specialized business logic.

The architecture supports complex business workflows through typed protocol chains, where each implementation inherits core capabilities while extending them with domain-specific actors, actions, and metrics. This approach allows business experts to define industry-specific processes while ensuring technical consistency and type safety throughout the system.

---

Figure 1: The Value Graph Schema System

valueGraph: your Business Logic

The Value Graph Schema System illustrates the core architectural components and their relationships. Core Templates (Actor, Action, Blueprint, Metric) form the foundation, with Protocol and Template schemas extending these base definitions. The diagram demonstrates how Protocols implement Blueprints while Templates extend them, creating a hierarchical schema system that enforces type safety and structural consistency across the platform.

---

Figure 2: Tailored Templates Extensibility

valueGraph extension: your Use Case

The Template Extensibility Pattern demonstrates how industry-specific implementations inherit from base templates. Primary and Secondary blueprints provide foundational structures, while specialized implementations (Financial Services, Healthcare, Technology) extend these with domain-specific features. This inheritance pattern, similar to Pydantic model extensions, enables consistent base functionality while allowing industry-specific customization of actors, actions, workflows, and metrics. The workflow templates ensure standardized process definitions across different domains.

---

Trucast core diagrams describe:

• Architectural relationships (Figure 1)

• Extensibility mechanisms (Figure 2)

• Practical implementation patterns

• Relationship to familiar patterns (JSON | Pydantic)

• A balance between standardization and customization

---

Diagrams:

PlantUML valueGraph template implementation

@startuml ValueGraph Template Extensibility

' Style skinparam packageStyle rectangle skinparam classAttributeIconSize 0

package "Base Templates" { abstract class BaseBlueprint { +id: string +type: string +domain: string +actors: string[] +actions: string[] +workflows: Workflow[] }

class PrimaryBlueprint extends BaseBlueprint { +domain: "primary" -- +Product Business +Service Business +Trade Business }

class SecondaryBlueprint extends BaseBlueprint { +domain: "secondary" -- +Brokerage Platform +Subscription Service +Marketplace Platform +Business Ecosystem } }

package "Industry Implementations" { class FinancialServices extends PrimaryBlueprint { +domain: "finance" -- +Financial Platform +Capital Markets +Investment Banking +Exchange Services }

class Healthcare extends SecondaryBlueprint { +domain: "healthcare" -- +Clinical Operations +Quality Management +Patient Care }

class Technology extends PrimaryBlueprint { +domain: "technology" -- +SaaS Operations +Feature Lifecycle +Performance Monitoring } }

package "Workflow Templates" { class WorkflowTemplate { +steps: Step[] +validation: string[] +dataTypes: DataType[] +metrics: Metric[] } }

' Relationships PrimaryBlueprint --* FinancialServices PrimaryBlueprint --* Technology SecondaryBlueprint --* Healthcare

FinancialServices --> WorkflowTemplate Healthcare --> WorkflowTemplate Technology --> WorkflowTemplate

note right of BaseBlueprint Base template defines core structure that all implementations must follow end note

note right of WorkflowTemplate Industry-specific implementations extend base templates with:

• Custom actors

• Domain actions

• Specialized workflows

• Industry metrics end note

@enduml

PlantUML valueGraph schema

@startuml ValueGraph Schema System

' Core Templates package "Core Templates" { class CoreActor { +id: string +type: string +role: string +capabilities: string[] +attributes: Record<string, number> +traits: string[] +relationships: string[] }

class CoreAction { +id: string +type: string +requirements: string[] +effects: string[] +metrics: string[] +constraints: string[] }

class CoreBlueprint { +id: string +type: string +domain: string +actors: string[] +actions: string[] +workflows: Workflow[] }

class CoreMetric { +id: string +type: string +unit: string +range: Range +thresholds: Threshold[] } }

' Protocol Schema package "Protocol Schema" { class Protocol { +name: string +description: string +primaryArchetype: string +secondaryArchetype?: string +blueprintType: string +actorType: string +actionType: string +steps?: ProtocolStep[] +metrics?: ProtocolMetric[] +metadata?: Metadata }

class ProtocolStep { +stepNumber: number +stepActionType: string +stepActorType?: string +metadata?: Metadata }

class ProtocolMetric { +type: string +value: number +threshold?: number +metadata?: Metadata } }

' Template Schema package "Template Schema" { class Template { +id: TaxonomyId +name: string +category: string +domain: string +defaultActors: string[] +defaultBlueprints: string[] +defaultActions: string[] +metrics: string[] +steps: TemplateStep[] }

class TemplateStep { +order: number +action: string +actor?: string +requiredData?: string[] +metrics?: string[] } }

' Relationships Protocol "1" -- "" ProtocolStep Protocol "1" -- "" ProtocolMetric Template "1" -- "" TemplateStep CoreBlueprint "1" -- "" CoreActor CoreBlueprint "1" -- "" CoreAction CoreBlueprint "1" -- "" CoreMetric

Protocol ..> CoreBlueprint: implements Template ..> CoreBlueprint: extends ProtocolStep ..> CoreAction: references TemplateStep ..> CoreAction: references

@enduml