Skip to content

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

207 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

AI Inference on Intel Xeon 6

Red Hat × Intel — Heterogeneous Compute, Modular Optimization

        ▲ Red Hat            ▲ Intel
       ╱ ╲                  ╱ ╲
      ╱   ╲                ╱   ╲
     ╱     ╲              ╱     ╲
    ╱ OpenShift ╲        ╱ Xeon 6  ╲
   ╱  Platform   ╲      ╱   Gaudi   ╲
  ╱───────────────╲    ╱─────────────╲

Polyglot multi-agent AI platform for enterprise inference across Healthcare and Financial Services verticals. Routes each request to the right-sized model on the right hardware — CPU at $0/token for simple tasks, GPU/accelerator tier for complex reasoning. The system decides for you in <1ms (after embedding model warm-up).

Pillar Technology Role
Intel Xeon 6 CPU + Gaudi GPU via MAAS/LiteLLM Heterogeneous compute — $0 CPU + $/token GPU
Red Hat OpenShift + AMQ Streams + vLLM Semantic Router Enterprise platform with intelligent routing at scale

Key Results

Metric Result Measured On Notes
Speculative decoding 6.52x speedup (measured on local model serving; remote inference via MAAS adds network overhead per speculative token) Oberon (local OVMS) Local serving only
Heterogeneous routing <25ms decision MAAS Semantic router → CPU or GPU tier
MCP tools vs LLM ~450x faster MAAS (July 2026) Drug interaction lookup (9ms vs ~4s LLM)
Semantic routing <1ms per decision After warm-up Embedding similarity, no LLM call
Multi-model fusion ~11.6s (3+judge) MAAS (July 2026) 3-model panel + judge with consensus/contradictions
Classification CPU ~650ms MAAS (July 2026) granite-2b-cpu, qwen25-3b-cpu
Full pipeline ~7.8s MAAS (July 2026) classify → NER → interactions → summarize
BitNet edge 0.4GB, ~70ms/tok Oberon 1.58-bit ternary weights, self-contained pod

Architecture

┌──────────────────────────────────────────────────────────┐
│  React 19 Frontend (Zustand + React Flow + Motion)       │
│  PipelineFlow · AgentTopology · RoutingFlow              │
└─────────────────────┬────────────────────────────────────┘
                      │
        ┌─────────────┼─────────────┐
        │             │             │
   Semantic      Healthcare     FinServ
   Router        Agent          Agent
   (<1ms)        (Python)       (Quarkus)
        │             │             │
        │        ┌────┼────┐        │
        │        │    │    │        │
        │     MCP  Kafka  PostgreSQL
        │   Gateway Streams  audit log
        │   (8 tools)        │
        │        │            │
        └────────┼────────────┘
                 │
          ┌──────┼──────┐
          │      │      │
        CPU    GPU    Edge
       OVMS   LiteLLM  BitNet
    (9 models) (tier)  (0.4GB)
  • Healthcare Agent — Python/FastAPI + LangGraph 4-node pipeline with adaptive cache, heterogeneous routing, speculative decoding, multi-model fusion
  • FinServ Agent — Java/Quarkus with LLM fraud scoring + rule-based signals
  • Orchestrator — Go, A2A workflow coordination, agent discovery (zero inference)
  • Semantic Router — Embedding-based complexity routing (<1ms after warm-up), heterogeneous CPU→GPU
  • MCP Gateway — 8 federated tools via JSON-RPC 2.0
  • Edge Agent — BitNet b1.58 2B4T, self-contained pod (0.4GB, no MAAS dependency)

Hands-On Lab (~2 hours)

Choose-your-own-adventure structure. Students measure, configure, and deploy — not just observe.

Section Content Time
Orient + Baseline Login, discover models, measure defaults, choose your path ~25 min
Choose Your Path (pick 2-3) Right-Size Models, Engineer Down, Route & Split, Scale & Cost ~20 min each
Build (pick 1-2) Custom Routing Config, Fusion Panel, MCP Tools, Load Harness ~20 min each
Capstone Write Helm values, deploy optimized stack, validate, write CTO recommendation ~25 min

Each module ends with Verify checklists and Learning Outcomes.

Models

RHDP (5 MAAS models, $0/token):

Model Role
granite-4-0-h-tiny-cpu Speculative draft, fast classification
granite-2b-cpu NER, fraud scoring, speculative target
qwen25-3b-cpu Classification, summarization
phi3-mini-cpu Complex reasoning
granite-3-2-8b-instruct-cpu Fusion judge + heterogeneous "GPU" tier

Oberon (Intel lab, 10 local models via OVMS + bitnet.cpp):

Model Params Role
granite-350m 350M Speculative draft
granite-4-0-h-tiny-cpu ~1B Ultra-fast classification
granite-2b-cpu 2B NER, fraud scoring, speculative target
granite-2b-int8 2B INT8 optimization comparison
qwen25-3b-cpu 3B Classification, summarization
granite-4.1-3b 3B Next-gen classification
phi3-mini-cpu 3.8B Complex reasoning
granite-3-2-8b-instruct-cpu 8B Fusion judge
granite-4.1-8b 8B Simulated GPU tier
bitnet-2b4t 2B Edge inference (1.58-bit ternary)

15 Pluggable Modules

modules/
├── Per-Record Efficiency
│   ├── semantic-routing         LIVE     right model per request in <1ms (after warm-up)
│   ├── conditional-pipeline     LIVE     skip unneeded inference steps
│   └── mcp-tools                LIVE     database lookup vs LLM call (85x faster)
├── Model Optimization
│   └── model-optimization       LIVE     INT8, AMX, optimized variants
├── Fleet-Scale Throughput
│   ├── batch-processing         LIVE     AMQ Streams parallel processing
│   ├── replica-scaling          LIVE     agent + model serving replicas
│   └── llmd-inference           ROADMAP  disaggregated prefill/decode
├── Compounding Over Time
│   └── adaptive-classification  LIVE     cache learns from LLM results
├── Heterogeneous Compute
│   ├── benchmarking             LIVE     model × task × hardware matrix
│   ├── heterogeneous-routing    LIVE     CPU→GPU intelligent routing
│   ├── multi-model-fusion       LIVE     3-model panel + judge synthesis
│   ├── speculative-decoding     LIVE     draft/target speedup (local serving)
│   └── edge-inference           LIVE     BitNet 0.4GB self-contained pod
└── Analysis
    ├── cost-analysis            LIVE     CPU vs GPU vs Cloud comparison
    └── scale-testing            LIVE     concurrent load, throughput ceiling

Quick Start

cp .env.example .env              # Add LITELLM_API_KEY
source .env && export LITELLM_API_BASE LITELLM_API_KEY
make up                           # Start PostgreSQL + Redpanda + all agents

# Test endpoints
curl -s http://localhost:8081/health
curl -s http://localhost:8081/api/v1/modules
curl -s http://localhost:8081/api/v1/speculative/status

# Run the pipeline
curl -s -X POST http://localhost:8081/api/v1/pipeline \
  -H "Content-Type: application/json" \
  -d '{"text": "DISCHARGE SUMMARY: 72-year-old male with Type 2 Diabetes on Metformin and Lisinopril."}' | jq .

# Run multi-model fusion
curl -s -X POST http://localhost:8081/api/v1/fusion \
  -H "Content-Type: application/json" \
  -d '{"task":"compliance","prompt":"Is this AML structuring? Three deposits of $9,500 in 48 hours."}' | jq .

Testing

CDD → TDD → EDD methodology. 11-stage validation matrix + frontend smoke tests.

make test-contracts              # Stage 0: 122 contract tests
make test-unit                   # Stage 2: 54 healthcare + 14 router + 13 finserv + 3 Go + 29 frontend
make test-modules                # Stage 8: 13 module manifest + Helm tests
make test-smoke                  # 19 live endpoint tests (no NaN, no empty, no crash)
make test-platform               # ALL stages — platform green light

Demo Variants

Variant Story Technology
AI Inference Can I afford AI at scale? CPU inference, heterogeneous routing, 15 modules
Secure AI Can I trust it with my data? Intel TDX, Confidential Containers, hardware attestation
VMs + AI Can I run AI alongside VMs? OpenShift Virtualization, BitNet edge inference

RHDP Catalog

3 catalog items under ai-quickstarts/ai-lab-xeon6-inference-*:

Item Purpose
ai-lab-xeon6-inference-cluster Base cluster infra (operators via GitOps)
ai-lab-xeon6-inference-tenant Base AI lab — all modules enabled
ai-lab-xeon6-inference-secure-tenant + Confidential Containers (TDX)
ai-lab-xeon6-inference-virt-tenant + OpenShift Virtualization + BitNet

Project Structure

contracts/           # CDD: OpenAPI, AsyncAPI, MCP, A2A schemas
services/
  healthcare-agent/  # Python/FastAPI + LangGraph + speculative + fusion + routing
  finserv-agent/     # Java/Quarkus + LLM fraud scoring + Kafka
  orchestrator/      # Go + A2A client + workflow engine
  semantic-router/   # Python + sentence-transformers + heterogeneous routing
  mcp-gateway/       # Python/FastAPI + 8 JSON-RPC tools
  edge-agent/        # BitNet b1.58 2B4T (bitnet.cpp, self-contained)
modules/             # 15 pluggable optimization modules with manifests + lab content
infrastructure/
  podman-compose.yaml  # Local dev stack (8 services)
  helm/              # Helm chart for OpenShift with module flags
  oberon/            # Intel lab overrides (10 OVMS models + LiteLLM)
frontend/            # React 19 + Zustand + React Flow + Motion
content/             # Showroom lab (base variant)
content-secure/      # Showroom (TDX variant)
content-virt/        # Showroom (Virtualization variant)
tests/               # Validation matrix (11 stages) + benchmark rubric + smoke tests

Container Images

All built on push to main via GitHub Actions (--platform linux/amd64).

quay.io/redhat-gpte/triforce-healthcare-agent:latest
quay.io/redhat-gpte/triforce-finserv-agent:latest
quay.io/redhat-gpte/triforce-orchestrator:latest
quay.io/redhat-gpte/triforce-mcp-gateway:latest
quay.io/redhat-gpte/triforce-semantic-router:latest
quay.io/redhat-gpte/triforce-frontend:latest
quay.io/redhat-gpte/triforce-edge-agent:latest

License

Apache-2.0

About

Triforce — Red Hat + IBM + Intel multi-agent AI platform. Polyglot (Python/Go/Java), LangGraph, Kagenti A2A/MCP, Intel Xeon 6 CPU inference, Kafka, PostgreSQL.

Resources

Stars

Watchers

Forks

Releases

Packages

Used by

Contributors

Languages