starlight-intelligence-system

Starlight Intelligence System

One shared brain for your entire AI fleet — across every tool and every repository.

Persistent memory. Attested knowledge. Sovereign control.

Claude Code, Cursor, Codex, Gemini CLI, OpenCode, Antigravity — they all read from and write to the same six semantic vaults, with full provenance. No more explaining the same thing to every agent. No drift. No lost decisions.

Claude Code, Cursor, Codex, Gemini, and OpenCode — all reading the exact same attested memory from one substrate.

---

Starlight is two things in one repository:

• SIP — the open Starlight Intelligence Protocol: a clean contract for sovereign memory, identity, and governance that anyone can adopt.
• SIS — the reference implementation: 144 specialized agents, 83 auto-activating skills, 6 semantic vaults, a production MCP server, and the repeatable Estate Factory for running full sovereign agent armies.

Use just the memory layer in your current tools. Adopt the protocol. Or run the complete system Frank uses every day.

60-second start

npx -p @arcanea/starlight-intelligence-system starlight init --vaults

Then add to your MCP config (Claude Code, Cursor, Codex, Gemini, etc.):

{
  "mcpServers": {
    "starlight": {
      "command": "node",
      "args": ["node_modules/@arcanea/starlight-intelligence-system/dist/mcp-server.js", "--vault-dir", "~/.starlight/vaults"]
    }
  }
}

Restart your client. Every agent now shares the same memory. Ten sis_* tools appear instantly.

---

Two layers, one repo

Layer	What it is	Best for
SIP (Protocol)	Open standard. Six clean layers for memory, attestation, commands, and sovereignty.	Forking the protocol or building your own systems
SIS (Reference)	Complete working system: 144 agents, 83 skills, 6 vaults, MCP server, Estate Factory.	Running it as your daily multi-agent brain

Use the protocol alone, the memory layer alone, or the full reference implementation. They are designed to compose.

Getting started locally — SETUP.md (30-minute full setup including private state).
Just want the protocol spec — use the lightweight SIP kit instead.

See CHANGELOG.md for history.

---

Why It Matters

flowchart TB
  Human["Human intent"] --> Vaults["6 semantic vaults (JSONL truth)"]
  Vaults --> Index["SQLite + FTS5 index"]
  Index --> MCP["MCP server (10 sis_* tools)"]
  MCP --> Adapters["Every CLI you use"]
  Adapters --> Work["Safer, consistent, memory-aware work"]
  Work --> Vaults

The difference:

• One source of truth instead of N fragmented contexts
• Knowledge that compounds instead of resetting every session
• Attestation so you always know what came from where
• The same memory works in Claude, Cursor, Codex, Gemini — simultaneously

We made the hard parts (temporal decay, contradiction detection, cross-tool sync) automatic.

For production sovereign systems

Starlight includes a complete Estate Factory pattern for running real "Mind + Mesh + Steward" agent armies at scale.

• Mind: Your grounded intelligence layers
• Mesh: Coordinated swarms with routing, synthesis, and operations
• Steward: Health monitoring, evolution, and long-term value

A 4-layer blueprint plus reusable templates lets you stand up new estates quickly while keeping them 100% yours.