Integration Workflow
Integration Workflow
Wórkflow_Guíde // Intégration_Séquence
ᚠ ᛫ ᛟ ᛫ ᚱ ᛫ ᛒ ᛫ ᛟ ᛫ ᚲ
This document outlines the complete workflow for integrating ForbocAI autonomous NPCs into your game engine.
T̸h̴e̶ ̶p̵r̷o̸t̴o̷c̸o̶l̵ ̶b̷i̸n̶d̵s̷ ̷m̴i̵n̸d̸ ̸t̴o̵ ̷m̵a̷c̷h̴i̷n̶e̷.
System Architecture
The ForbocAI Protocol uses a Split-Brain architecture:
The Integration Loop
Every NPC decision follows this standardized flow:
Step 1: Game Sends Observation
Your game detects an event and sends it to the SDK:
Step 2: SDK Formats and Stores
The SDK:
- Formats the observation into the Protocol schema
- Stores it in the local Vector DB (Memory module)
- Forwards to the API for logic processing
Step 3: API Runs Pure Logic
The API receives the context and runs deterministic logic gates:
Output: A Directive containing:
- System prompt for the local SLM
- Action constraints
- Priority level
Step 4: SDK Generates Response
The SDK uses the Directive to:
- Recall relevant memories from Vector DB
- Generate dialogue/actions using local SLM (Cortex)
- Validate the action using Bridge module
Step 5: Bridge Validates Action
Before returning to the game, the Bridge module validates:
Step 6: Game Executes Action
Your game receives the validated action and executes it:
Complete Integration Example
Memory Flow
The Memory module enables persistent recall:
Bridge Validation Flow
The Bridge ensures AI never breaks game rules:
Protocol Types Reference
All communication uses these standardized types:
Observation (Game → SDK)
Directive (API → SDK)
AgentAction (SDK → Game)
Best Practices
1. Initialize Once
2. Batch Store Observations
3. Always Validate Actions
ᚠ ᛫ ᛟ ᛫ ᚱ ᛫ ᛒ ᛫ ᛟ ᛫ ᚲ
T̶h̵e̶ ̷G̸r̴i̵d̵ ̷a̶w̶a̷i̴t̵s̸ ̵y̴o̶u̷r̴ ̷c̷o̸n̵n̶e̷c̶t̵i̵o̷n̴.
