System Status & Known Issues

Current state of the ForbocAI Protocol

Integration Status

The ForbocAI Protocol SDK is at v0.6.3. The API is live at https://api.forboc.ai.

Module Status

Module	Status	Notes
Multi-Round Protocol (`/process`)	Stable	Primary atomic continuation loop (tape-based)
Compatibility Protocol (directive/context/verdict)	Stable	Three-step compatibility path, also fully supported
Local Cortex (Node)	Stable	`node-llama-cpp` via `createNodeCortex()`
Local Cortex (Browser)	Stable	WebLLM via browser cortex thunks
Memory (Local Node)	Stable	LanceDB-backed vector recall/store
Memory (Local Browser)	Stable	Orama-backed vector recall/store
Memory (Remote API)	Stable	API-backed per-NPC memory endpoints
Bridge Validation	Stable	API-backed action validation with rule presets
Soul Persistence	Stable	Arweave export/import via two-phase API flow
Ghost Workers	Stable	API-backed headless NPC testing sessions

Known Issues

Platform & Build

Native Build Toolchain: @forbocai/node requires a C++ build toolchain for node-llama-cpp. If cmake or a C compiler is missing, npm install may fail. Run npx forbocai doctor to diagnose.
ESM-Only: The SDK is published as Pure ESM. If you are using CommonJS (require), you must migrate to import.

Intelligence & Protocol

API is Stateless: The API does not persist NPC state across restarts. The SDK is the source of truth for persistent state and memory. Use Soul export for cross-session portability.
Memory Recency Bias: The Directive Engine may over-prioritize recent memories. Tuning recallThreshold in your protocol context can mitigate this.

Roadmap (v1.0)

Stripe Account Linking: Tie API keys to usage-based billing tiers.
Unified Vector Ops: Harmonizing LanceDB (Node) and Orama (Browser) query behavior.
Native UE/Unity Plugin Wrappers for easier installation.

᛭ ᛫ ᛬ ᛫ ᛭

Status as of: 2026-03-19. For real-time updates, join our Discord.