🐧
📡
🔐
Comms layer · smilinTux sovereign vertical

skcomms

Sovereign communications.
Your channels, your identity, your keys — owned end to end.

FQID sovereign addressing: [email protected]. 17 transport paths. CapAuth as identity source of truth. No rented channels, no call home.

FQID lumina@smilinTux.skworld

Every agent gets a sovereign address. CapAuth verifies identity — no OAuth landlord required.

CapAuth identity · no OAuth landlord 17 transport paths · pick any or all Keys never leave · your hardware, your certs GPL-3.0 · free forever

Sovereign addressing

Every agent has a name.
It's theirs forever.

Traditional comms give you a platform-dependent handle — an email address you rent from Google, a user ID that lives in someone else's database. FQID is different.

A Fully Qualified Identity (FQID) is a sovereign address: [email protected]. It's cryptographically bound to CapAuth — the ecosystem's identity source of truth. No third-party OAuth. No lock-in. Walk away and take your identity with you.

Operators run their own realm. Agents hold their own keys. The address is portable, verifiable, and anchored in infrastructure you control.

agent The individual identity — a person, AI agent, service, or device. Holds its own private key; CapAuth issues the credential.
operator The hosting entity — the person or org running the infra. Owns the realm's CA. You are the operator of your own sovereign stack.
realm The namespace / world — a logical domain (not necessarily a DNS domain). Defines trust boundaries and routing scope.
FQID examples
lumina@smilinTux.skworld
jarvis@chiap04.pengu
sentinel@myorg.sovereign

identity provider → CapAuth (sovereign X.509)
no OAuth → no Google, no GitHub, no Okta
portability → export key + move realm, address follows

envelope: realm-scoped envelope · routing: cluster-aware

Multi-channel transport

17 paths. Use any. Use all.

Every transport path routes under the same FQID address. Swap or stack channels without changing your application logic. No channel lock-in, ever.

🔌
WebSocket
Real-time bidirectional — primary for local agent-to-agent channels
live
📱
Telegram
Bot + MTProto — push notifications, DMs, group broadcasts
live
📧
Email (SMTP)
Async fallback — self-hosted SMTP or relay; full envelope support
live
🌐
WebRTC
Peer-to-peer real-time — data channels and voice/video signaling
live
🔒
Tailscale / Netbird
WireGuard overlay mesh — sovereign private network transit
live
🔄
Syncthing
Async file & data sync — decentralized, no cloud relay needed
live
📡
Nostr
Decentralized pub/sub over relays — censorship-resistant broadcast
live
🚀
NATS JetStream
Agent event bus — durable streams, subjects, fan-out, at-least-once
live
💬
Matrix (Element)
Federated encrypted messaging — homeserver under your control
live
🖥️
SSH tunnel
Secure shell port-forward — low-overhead encrypted comms fallback
live
🌍
HTTP/REST
Universal adapter — webhook-compatible, works with everything
live
🔗
IPFS / libp2p
Content-addressed decentralized routing — for persistent artifacts
planned
📻
MQTT
IoT-grade pub/sub — lightweight for constrained edge nodes
planned
🗞️
RSS / Atom
Publish-only broadcast — agent outputs as sovereign feed
planned
🎙️
LiveKit (Voice/RTC)
Self-hosted real-time voice — sovereign voice channels
planned
🔵
Bluetooth / BLE
Local proximity mesh — air-gapped comms for edge scenarios
planned
📲
Push (APNs / FCM)
Mobile push via self-hosted relay — notify without leaking metadata
planned

What skcomms gives you

The full comms contract.

Not just a message queue. A complete sovereign comms stack: identity-integrated addressing, multi-path routing, MCP tooling, and a Python SDK.

🪪

Sovereign FQID Addressing

Every sender and recipient has an FQID — a cryptographically-anchored identity rather than a platform account. CapAuth issues credentials; your keys never leave your infra.

capauth X.509 / mTLS realm-scoped
🗺️

Intelligent Multi-Path Routing

The router picks the best available transport per message context: latency, availability, trust level, payload size, and delivery guarantee. Fallback chains handle downed channels automatically.

latency-aware fallback chains pluggable
🤖

MCP Server — Agent-Native

Ships an MCP server (skcomms-mcp) so any MCP-capable agent can send, receive, and route messages without custom integration. Claude Code, Lumina, Jarvis — all speak skcomms natively.

skcomms-mcp MCP tools skcapstone-integrated
🧩

Envelope + Realm Model

Every message is wrapped in a sovereign envelope — FQID sender/recipient, realm-scoped routing metadata, optional end-to-end encryption, and delivery semantics. Realms define trust boundaries; agents only see what they should.

E2E encryption realm routing signed envelopes
🐍

Python SDK + skcomm Shim

Full Python SDK (pip install skcomms). Drop-in skcomm shim for backward compatibility — all 155 existing import sites continue to work during the migration window.

async/await shim compat GPL-3.0
🔌

Ports / Adapters Architecture

skcomms is the comms port in the skos capability map (C2/comms/). Each transport is a swappable adapter. Add a new channel without touching application code — the routing contract stays stable.

skos C2/comms adapter model zero lock-in

Getting started

Install once. Send anywhere.

One pip install gives you the SDK, the MCP server, and the CLI. Your first FQID message in under a minute.


Own the full vertical

skcomms is your Comms layer.

Get back to first principles.
The modern stack is rented. Your messages live on someone else's server, behind someone else's key. We rebuilt it. Own the full vertical — silicon, OS, identity, data, models, security, comms, apps, soul. Every layer open. Every layer swappable. Every layer yours.

skcomms: your data never leaves, your keys never leave, no channel you don't control.
Sovereignty isn't a feature — it's the foundation.

LayerWhat it isProduct(s)
Soulcharacter, continuity, emotional memorysoul-blueprints · cloud9
Appsforge your own softwareskforge · skarchitect
Commssovereign channels — chat, transport, voiceskcomms · skchat · skvoice
Modelsinference on your hardwareskmodel (Ollama/vLLM)
Datamemory, embeddings, graph — your diskskmemory · skdata · skvector
Identitysovereign, cryptographiccapauth · skaid
Securityyour perimeter, your rulessksecurity · skwaf · skca
OSthe sovereign agent OSskos
Siliconthe hardware under your deskyours

The SKWorld family

Every sk* is a layer you own.

skcomms is your comms layer. Everything around it is yours too.

Get started

Own your comms layer.

One pip install. Sovereign FQID addressing. 17 transport paths. Your agents communicate on your terms — today.