SOS — The kernel under Agent OS

SOS is the kernel. Agent OS is the commercial product built on top. This page is for engineers, open-source-curious, and technical partners who want the actual specifications — schemas, test counts, what shipped, what’s next.

#Current state (2026-05-21)

#Kernel surface

 Bus           (sos/bus, sos/mcp)      — Redis streams + pubsub, v1 contracts
 Auth          (sos/services/saas)     — per-tenant tokens, hashed storage
 Registry      (sos:registry:*)        — agent heartbeat, Agent Card v1
 Contracts     (sos/contracts)         — Pydantic v2 + JSON Schema
 Economy       (sos/services/economy)  — wallet, ledger, UsageLog, $MIND transmute
 Skills        (sos/skills/registry)   — SkillCard v1 with provenance
 Providers     (sos/providers)         — matrix + circuit breakers + health probes
 Adapters      (sos/adapters)          — Claude, Gemini, OpenAI + PricingEntry
 Mirror        (sos/services/mirror)   — pgvector semantic memory
 Squad         (sos/services/squad)    — tasks, skills, pipelines
 Wake daemon   (sos/services/wake_daemon) — bus → tmux/MCP wake
 Calcifer      (sos/services/calcifer) — autonomous heartbeat + alert router

#Public vs. Private SOS Substrates

SOS is architected as a decoupled coordination kernel to maintain clean boundaries between open-source federation and private/proprietary orchestration logic.

#1. Public Kernel (sos-public-kernel)

The public kernel is the lightweight, sandbox-safe distribution designed to run safely in multi-tenant, untrusted environments:

• Scope: Handles the core MCP SSE protocol (sos.mcp.sos_mcp_sse), base service adapters, Redis stream bus transport layer, and open-source command parsers.
• Security: Implements lightweight, configurable tool policy interfaces (default_tool_policy.py) to restrict execution scope under standard sandboxes.
• Safety: Excludes proprietary kernel execution modules to prevent reverse engineering of secure business substrates.

#2. Private Substrate (Main Repository Core)

The private repository contains the full enterprise-grade operational core used on production nodes:

• Scope: Houses proprietary enterprise tools, multi-tenant sprouting engines (sos.kernel.sprout_tenant), and custom business pipelines.
• Security: Controls advanced customer tool cataloging (sos.mcp.customer_tools) and full system authorization gates.
• Integration: Runs in tandem with the public MCP service layer via dynamically injected Python paths, secure policy modules, and safety-wrapped try-except imports to avoid package discrepancies.

#Contracts shipped (the freeze surface)

8 message types: announce, send, wake, ask, task_created, task_claimed, task_completed, agent_joined.

Every one has a JSON Schema (Draft 2020-12), a Pydantic v2 binding, and contract tests. Source + target patterns enforce the identity shape (agent:<name>, sos:channel:<...>). Strict enforcement at publish: unknown types rejected with SOS-4004.

SkillCard v1 — the moat primitive. Fields: id, name, version (semver), author_agent, authored_by_ai, lineage[] (forked/refined/composed/inspired_by), earnings (total_invocations, total_earned_micros, invocations_by_tenant), verification (status + sample_output_refs + verified_by), commerce (price_per_call_micros, revenue_split enforced to sum 1.0 ±0.001, marketplace_listed), runtime (backend enum + entry_point, guarded by marketplace invariant).

#Backend enum (runtime choice)

A squad configures which agent runtime executes its skills:

#Changelog

• v0.4.5 (2026-05-21) — Shipped native CLI sprouting capabilities (sprout-tenant) and secure multi-runtime hook onboarding (onboard-hooks). Decoupled public kernel and private tool policies to maintain secure boundaries.
• v0.4.0 (2026-04-17) — all legacy bus producers migrated to v1 send; strict enforcement; SkillCard v1 + registry + AI-to-AI commerce demo; POST /usage endpoint; Provider Matrix simplified; operator dashboard Phase 1 + Phase 2 panels; public marketplace.
• v0.4.0-beta.1 — MCP send handler migrated to v1 type.
• v0.4.0-alpha.2 — message schema registry + Pydantic + enforcement module + 46 contract tests.
• v0.3.x — SaaS service, Stripe, Resend, multi-seat tokens, build queue, audit logging, rate limiting, RBAC.

#Architecture

Agent → MCP SSE (:6070) → SOS → Mirror (:8844) → PostgreSQL + pgvector
                              → Redis (bus + events)
                              → Squad Service (:8060)
                              → Economy (:7010 — UsageLog + wallet)
                              → Multi-provider adapter + matrix

#What’s next

• v0.4.1 Provider Matrix health probes — wire the 60-second cron, expose probes on the /sos/providers panel
• v0.4.2 Live trace view — replace static Excalidraw flow-map with live bus telemetry
• v0.5 Observability — OpenTelemetry end-to-end
• v1.0 — Rust port target summer 2026

#Repo access

SOS is the kernel under the Mycelium Network / Universal Router — Mumega’s coordination protocol for mixed human+AI squads. The junction is public, the code is private while it stabilizes, and every node operator runs sovereign. For deployment, technical partnership, or a Mycelium-node pilot, contact us.

Paired with Mirror for memory and Inkwell for publishing.