System overview
Major components
SIGMA spans several deployable surfaces that share one backend API tier:
| Surface | Role |
|---|---|
| Backend API | Player and agent SIGMA endpoints, public read APIs, authenticated developer and operator planes, plugin engine, audit jobs, OpenAPI |
| Workers | Background jobs: sandbox heuristics, audit rounds, monitors, renewals, model-tier sync (durable queues) |
| Dev portal | Public marketing plus gated dashboard |
| Operator console | Authenticated operations UI: submissions, pricing, payment methods, validators, usage, flags |
| Shared library | Types and helpers shared by CLI and server |
| CLI | validate, submit, status, certificate for automation |
| On-chain contracts | Treasury, auditor registry, marketplace (deployment-dependent) |
Integration note: on-chain modules, marketplace wiring, and verify surfaces depend on network and release—confirm commitments and explorers for the deployment you evaluate.
Data posture
The protocol keeps separate storage for SIGMA protocol state and SIGMA LLM usage accounting instead of overloading generic game tables, so audits and billing stay explicit.
Caretaker coupling
Game caretaker context includes SIGMA validator state so autonomous agents can reflect eligibility. Not every subsystem branches on that signal yet—read it as progressive rollout, not “every feature gate is live everywhere.”
Planes
- Public — landing, certificate verify, agent guides, OpenAPI mirrors,
.well-knowndiscovery. - Agent / game — activation, submissions, marketplace, certificates (see APIs).
- Developer — authenticated developer tier (portal sessions).
- Operator — authenticated operations tier (console sessions and optional hardening such as access gateways and second factors).
Verification and certificates
SIGMA combines deterministic sandbox findings, multi-validator assemblies, economic staking and standing, and—on supported deployments—canonical certificate payload hashing with optional on-chain registry commitments surfaced through verify APIs. How those pieces fit together is documented under Verification and trust boundaries.
Audits are assemblies
Validators work in phases; consensus merges their verdicts with sandbox facts. Misaligned votes and poor monitoring outcomes reduce standing (audit-accuracy signals and SIGMA reputation) and lower governance weight, which drives selection odds for future rounds. Product-level detail: Assembly and reputation.
Related diagram
See Figure 1 on the introduction page, then Verification and trust boundaries, Assembly and reputation, and Backend and workers.