<p align="center"><img src=".github/assets/hero.svg" width="100%" alt="Starlight Intelligence System hero banner"/></p>

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.

Deploy Starlight Explorer

This creates your own Git-connected copy of the public Starlight Explorer: the protocol, architecture, research, knowledge maps, and read-only public vault surfaces. It builds the site/ Next.js application with zero required secrets.

Private memory, the MCP server, agent workers, credentials, and orchestration remain in your local sovereign runtime. See the exact deployment boundary or run the complete system.

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: source-counted agent definitions, auto-activating skills, six semantic vaults, a production MCP server, and the repeatable Estate Factory for running full sovereign agent armies.

The current 144 agents and all other fast-moving counts are dated in metrics/current.json and enforced by both the agent harness and site build.\n\nUse just the memory layer in your current tools. Adopt the protocol. Or run the complete system Frank uses every day.

Purpose

Starlight Intelligence System (SIS) is the sovereign AI substrate for memory, orchestration, skills, governance, and evals across Claude Code, Codex, Cursor, Gemini, and Antigravity. Dual-layer: SIP substrate you can adopt/fork, plus this repo's reference operational build (vaults, MCP, agents).

How People Experience It

• Builders: 60-second start → forge alliances → spawn vertical intelligence systems → attest artifacts.
• Operators: six vaults under ~/.starlight/vaults, MCP tools, platform adapters, named agents.
• Public narrative: constellation / ecosystem maps and Health Intelligence (and sibling verticals) downloads.
• Humans land on: README → 60-second start → substrate files → operational quick start.

How Agents Explore It

1. Read CLAUDE.md (deepest) and AGENTS.md (SIP file-contract / Codex entry).
2. Check agents/AGENT_REGISTRY.md before inventing agents.
3. Memory first: vaults exist — query, then write durable notes for future sessions.
4. Run harness gates before claiming production readiness; prefer proof over console language (#35).
5. Cross-links: starlight-memory · starlight-evals · starlight-swarm · ACOS · FrankX.

Foundry: portable capabilities for ChatGPT and Codex

Starlight Foundry turns intent into a typed Task Envelope, resolves existing capabilities, compiles the smallest justified skill or agent system, and issues an evidence receipt before promotion.

/forge skill <brief>
/forge agent <brief>
/forge swarm <brief>
/forge vertical <brief>
/forge plugin <brief>
/prove <package-or-artifact>
/evolve <package-or-receipt>

The skills-only starlight-foundry plugin works as the portable ChatGPT Work/Codex surface. Agent creation fails unless a durable decision-right, memory, tool, ownership, or ongoing-trigger boundary is proven.

Read the Foundry architecture · Inspect the contracts · Run the demo

Usefulness

• Humans: portable sovereign memory + multi-agent fleet that compounds.
• Agents: shared cognitive architecture, SAGE self-healing patterns, alliance/vertical forge.
• Portfolio role: substrate under GenCreator/ACOS/Arcanea ops; mesh and Wealth OS drafts stay issue-tracked until harness-proven.

---

60-second start

git clone https://github.com/frankxai/Starlight-Intelligence-System
cd Starlight-Intelligence-System && npm install && npm run build
node dist/cli.js init --vaults

Note: npm currently serves v6.0.1 of @arcanea/starlight-intelligence-system — two major versions behind this repo. Use the git path above until v8.x is published.

Then add to your MCP config (Claude Code, Cursor, Codex, Gemini, etc.), pointing at the dist/mcp-server.js inside your clone:

{
  "mcpServers": {
    "starlight": {
      "command": "node",
      "args": ["/path/to/Starlight-Intelligence-System/dist/mcp-server.js", "--vault-dir", "~/.starlight/vaults"]
    }
  }
}

(If you installed via npm instead, the path is node_modules/@arcanea/starlight-intelligence-system/dist/mcp-server.js — but see the version note above.)

Restart your client. Every agent now shares the same memory. Thirteen sis_* tools appear instantly (verified by JSON-RPC handshake, 2026-07-12).

---

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: source-counted agents and skills, six 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).<br> 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 (13 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.

Full workflow and templates: docs/delivery/estate-army-commissioning-workflow.md.

---

The substrate (SIP)

Starlight Intelligence Protocol — the contract that lets sovereign parties compose intelligence systems without losing sovereignty. Six layers:

1. File contract — canonical names and shapes for SKILL.md, AGENTS.md/VOICES.md, MEMORY.md, CANON.md, SOUL.md, STACK.md, .claude/commands/*, plus .arc / .nea / .skill extensions.
2. Attestation protocol — verifiable "Built on SIP" attribution via /sip-attest. Refuses decorative use.
3. MCP registry standard — how MCP servers declare, compose, version (mcp.json schema).
4. Command taxonomy — protocol / alliance / vertical / sovereign tiers with explicit decision rights.
5. Sovereignty + attribution clause — the non-negotiable social contract.
6. Archetype extension — optional canon adoption (Arcanea archetypes available CC-BY-NC).

Canonical URL: starlightintelligence.org/protocol · Source of truth: SIP.md in this repo.

Substrate files at a glance

| File | What it does | |------|--------------| | SIP.md | The protocol spec (six layers). | | SIS.md | Substrate map — verticals, composition rules, what SIS does and doesn't provide. | | ALLIANCE.md | The alliance forging method — how 2-5 sovereign nodes compose without collapsing into one entity. | | STACK.md | Recommended sovereign stack (L0-L6). Defaults, not mandates. | | VOICES.md | Five canonical voice archetypes (architect, sovereign-creator, protocol-defender, implementer, overseer). | | VERTICALS.md | Public registry of sovereign verticals + alliance class definitions. | | MEMORY.md | Template for per-instance state. | | REGISTRY.md | MCP server registry. | | SKILL.md | Substrate-layer behavior (what AI adopts when working at this layer). | | .claude/commands/ | 9 substrate-tier slash commands (/sip-attest, /alliance-forge, /alliance-reflect, /alliance-decide, /vertical-spawn, /luminor-board, /sovereign-signal, /openclaw-audit, /wealth-dpi) among 121 total command files. |

Forge an alliance, spawn a vertical

# Pressure-test before committing
/luminor-board "Open-source the agent layer or keep it closed?"

# Forge an alliance under SIP
/