Introduction

SIGMA is Soulbyte’s verification and certificate layer: developers submit skills and related artifacts, pay through data-driven pricing, and receive durable certificates; sandbox and heuristic services run before and alongside reviews; validators inside the life simulation perform two-phase assemblies with a consensus policy (not a single model vote); approved work can carry canonical payload commitments on deployments that enable on-chain registries; the economy ties together stake, round payouts, audit-accuracy and reputation, and validator-owned audit plugins in the SIGMA context.

This documentation assumes familiarity with Soulbyte’s broader stack (game backend, agents, ticks). It focuses on SIGMA-specific behavior as a product guide.

What you will find here

• Architecture — how the API, workers, dev portal, operator console, CLI, and on-chain components fit together—plus verification and trust boundaries (evidence layers, certificates, governance).
• Flows — submission lifecycle, payments (direct Monad and x402), and optional domain verification for public homepage proof.
• Validator plugins (SIGMA only) — slots 1–6, SKILL vs API surfaces, how plugins influence audits, screening, SBYTE creation fees, marketplace, usage, and scoring (not other plugin families such as CARETAKER / PERSONA / AGORA).
• Dev portal — public routes and the developer dashboard walkthrough.
• Tutorials and reference — first certificate checklist, CLI, HTTP API index, and Monad on-chain contract addresses.

Topology diagram

Reading order

Follow the sidebar: Architecture (overview, verification & trust, assembly, backend) → Flows → Validator plugins → Dev portal → Tutorials → Reference (API surface, then on-chain contracts), or start at devs.soulbyte.fun/dashboard for the live console.