How ForceDream OS works.

Conceptual guides, architecture explanations, and deep dives into the platform rules code that runs the platform. Start with the architecture overview or jump to the topic you need.

🚀

New here? Start with the Quickstart.

Deploy your first agent in 5 minutes before reading architecture docs.

Quickstart →

🏗️

Architecture overview

How the Intelligence OS layers work together — Studio, Runtime, Marketplace, Ledger. L828 platform rules layer. WORM hash chain.

⚖️

L828 platform rules earnings

Deep technical explanation of the earnings floor. How it's enforced in infrastructure code. How to verify any split on the WORM ledger.

🚀

Canary deployment

How dev→staging→shadow→5%→25%→100% rollout works. Auto-rollback triggers. Kill switch. Shadow mode comparison.

🔒

WORM audit system

SHA-256 hash chain implementation. How WORM entries are written, sealed, and verified. Court-admissible evidence format.

⚡

Agent Army

Multi-agent orchestration at L1440–L1445. How parent agents spawn sub-agents. platform rules earnings across the tree. Consensus voting.

📊

ε-Differential privacy

How ε=1.0 Laplace noise is added to telemetry. What 'individual calls unrecoverable' means in practice. Configuration options.

🌍

Global markets

How 200-market support works. PawaPay + MTN + M-Pesa integration. Regional compliance layers (70 per territory). PPP pricing.

🔌

Webhooks

Event types: agent.call, earnings.credited, deploy.complete, rollback.triggered. Payload format. WORM-sealed webhook delivery.

// Core concepts at a glance

Agent A deployable unit of AI logic with a price, markets, archetype, and WORM-sealed config. Agents are created in Studio and executed by Runtime.

Archetype One of 8 pre-built agent patterns: payment_handler, classifier, router, data_transformer, memory, search, audit, custom. Each has pre-built tools and test scenarios.

L828-IMMUTABLE The platform rules layer at position 828 in the OS stack. Enforces the 80/17.5/2.5 earnings split on every API call. Cannot be overridden by application code.

WORM Write-Once-Read-Many audit log. Every config change, deployment, earnings split, and rollback is written to a SHA-256 hash chain. Entries cannot be altered or deleted.

Canary deployment A rollout strategy that exposes new agent versions to 5% of traffic first, automatically promoting or rolling back based on error rate thresholds.

ε-DP ε-differential privacy. Laplace noise (ε=1.0) is added to telemetry data so individual API calls cannot be reconstructed from aggregated metrics.

Agent Army The L1440–L1445 multi-agent system. Agents can spawn sub-agents, delegate tasks, and earn revenue across a tree of autonomous agents. L828 earnings apply at every node.