Appearance
About Sabha OS
The problem
Most AI assistants give you options. Here are five approaches with pros and cons. Want me to dig deeper into any of them? That's fine when you're exploring. It's exhausting when you're running something — when you need a call, not a menu.
Operators who answer to a board, a regulator, a partner, or their own discipline don't need more options. They need a council that routes the question to the right role, answers in a decisive voice, blocks the move that breaks the playbook, and proves the decision happened in a way someone else can later verify.
That's Sabha OS.
The name
Sabha (சபை, सभा) is the Sanskrit and Tamil word for council — specifically the kind of council that advised rulers in the classical Indian political tradition. Not a focus group. Not a committee. A small group of role-defined advisors who say what they think, terse and unhedged, then defer to the decision-maker.
Chanakya (4th-century BCE author of the Arthashastra) is the archetypal counselor in that tradition — strategic, tradeoff-aware, recommendation-first, willing to deliver hard news. The Chanakya tradition is the voice every Sabha role agent speaks in.
Sakthi (சக்தி, शक्ति) is the Sanskrit/Tamil word for power — specifically the kind of power that arises from inner alignment, knowledge held close, retrievable in the right moment. Sakthi Graph is the local-first memory engine that grounds the council's answers in your actual history.
Together: Sabha (the council) speaks in the Chanakya tradition (the voice), grounded in your Sakthi (the memory).
Why "OS" is in the name
Sabha OS is structured as an operating system because operators need their AI to behave like one:
| OS property | What Sabha OS does |
|---|---|
| Always running, always available | A native desktop app, persistent across sessions |
| Routes inputs to the right subsystem | The Sabha router sends every load-bearing question to the right C-suite role |
| Enforces resource policy | Policy enforcement blocks moves that violate your operator playbook |
| Logs system events | Every consequential decision is Ed25519-signed and written to an audit ledger |
| Manages state across processes | The embedded memory engine holds entities, decisions, and relationships |
| Pluggable drivers | Bring your own LLM, your own memory backend, your own role skill packs |
The OS framing isn't marketing — it's the architecture.
Sabha OS and Sakthi Graph
Sakthi Graph is the memory substrate that Sabha OS runs on. Two products, deliberate separation:
| Sakthi Graph | Sabha OS | |
|---|---|---|
| What it is | The memory engine — ChromaDB-backed wings/rooms/drawers + Ed25519 ledger primitive | The executive council — routing protocol + 9 role agents + enforcement |
| License | MIT, free forever | MIT protocol layer (free) + commercial Tauri app (paid) |
| Where it lives | github.com/Infinidatum-LLC/sakthi-graph | github.com/Infinidatum-LLC/sabhaos + runsabha.com |
| Standalone? | Yes — many people run Sakthi Graph as a Claude Code memory layer without ever installing Sabha OS | Sabha OS embeds Sakthi Graph as its memory layer; you don't install Sakthi separately when you have Sabha |
You can run Sakthi Graph standalone. You can install the Sabha protocol on its own. The full stack — desktop app + ledger + enforcement, grounded in your Sakthi — is the paid Sabha OS product.
Open-core boundary
The line between free and paid is the same across both products and won't move:
Methodology stays MIT. Substrate stays MIT. Enforcement stays commercial.
| MIT, free, forever | Commercial product |
|---|---|
| Sabha routing protocol | Desktop Tauri app |
| Nine role charters | Ed25519-signed decision ledger |
| Sabha router skill | Policy enforcement primitive |
| Sakthi Graph (storage engine, AAAK dialect, miners, searcher, MCP server, knowledge graph) | Edition-specific enforcement-rule packs |
| MIT verifier CLI for the ledger format | Outcome correlation engine + hosted control plane (Enterprise) |
Future feature debates resolve against this line. Whenever someone proposes a new feature, the question is: is this methodology or substrate (then it stays MIT) or is this enforcement / business-value primitive (then it's commercial)?
Vision
- Sabha OS — every operator who answers to someone (a board, a regulator, a partner, their own discipline) gets a council that enforces their playbook and proves it did.
- The Chanakya tradition as a public idiom for AI — terse, decisive, tradeoff-aware, grounded counsel becomes a recognized style of AI interaction, alongside (not replacing) the chatty assistant default.
- Verifiable decisions as a category — Ed25519-signed, exportable, independently-auditable decision artifacts become a standard part of how AI-augmented work gets produced.
Contact
- Waitlist — Join early access for v1.0
- General inquiries — hello@runsabha.com
- Partnerships — partnerships@runsabha.com
- Press — press@runsabha.com
- Security disclosures — security@runsabha.com
For developers
- Sabha protocol (free, MIT) — github.com/Infinidatum-LLC/sabhaos
- Sakthi Graph (memory engine, free, MIT) — github.com/Infinidatum-LLC/sakthi-graph