sovereign-spawn

/sovereign-spawn

Load SIP.md, SIS.md, VOICES.md, STACK.md, VERTICALS.md. Spawn a full sovereign intelligence system under SIP — not a vertical (one domain) and not an alliance (multi-party). A full substrate-aware fork the sovereign owns, operates, and extends.

Input

$ARGUMENTS

When this command fires

• /intake classified inbound as Route D (sovereign spawn).
• Sovereign wants to run the whole SIS pattern — substrate awareness + their own operational layer — not just one vertical under someone else's substrate.
• Sovereign accepts the sovereignty clause (SIP § 5) and will ship attestation on their own artifacts.

When this command does NOT fire

• Single-domain builder → /vertical-spawn (cheaper, same substrate, no full fork).
• 2+ parties composing → /alliance-forge (shared not forked).
• Substrate change proposal → /luminor-board → possibly contribute back to SIP itself.

Process

1. Validate the five spawn conditions:

   • Sovereignty clear. Sovereign names their declared domain, their entity (person / company / DAO), and the public surface they'll operate. Ambiguity → halt, name the structural fork.
   • Substrate awareness real. Sovereign has read SIP.md. Ask one comprehension question about Layer 5 (sovereignty clause) before proceeding. Incorrect answer → require re-read, do not soften.
   • Attestation committed. Sovereign agrees every cross-party artifact they ship carries "Built on SIP". Silent composition is a breach.
   • Name not already registered. Check VERTICALS.md and REGISTRY.md. Collision → halt, require rename.
   • Fork intent honest. Sovereign can name one artifact they'll ship in the first 30 days that the fork enables and their prior stack did not. No answer = not ready to spawn; route to Concierge for re-qualification.

2. Build the sovereign's SIS scaffold structure:

<sovereign-name>/
├── README.md                 — what this sovereign system is, domain, public URL
├── SIP.md                    — symlink or upstream reference to starlightintelligence.org/protocol
├── SIS-instance.md           — this fork's substrate map (what operational layer runs on top)
├── SKILL.md                  — sovereign behavior definition (what AI adopts at this layer)
├── AGENTS.md                 — sovereign's named agents (may inherit 5 archetypes or declare new)
├── MEMORY.md                 — instance state (public template — private state stays private)
├── SOUL.md                   — sovereign essence (the thing that must not drift)
├── CANON.md                  — optional; if not adopting canon, declare decline explicitly
├── STACK.md                  — inherited from Starlight STACK.md or overridden
├── VOICES.md                 — inherited or extended per SIP § Layer 6
├── REGISTRY.md               — sovereign's MCP server registry
├── ATTESTATIONS.md           — append-only ledger for their /sip-attest emissions
├── .claude/commands/
│   ├── sip-attest.md         — mirrored from substrate
│   ├── vertical-spawn.md     — mirrored (sovereign can spawn their own verticals)
│   ├── alliance-forge.md     — mirrored (sovereign can forge alliances under SIP)
│   ├── luminor-board.md      — mirrored
│   ├── <sovereign-slug>-*.md — sovereign-tier commands they author
├── agents/                   — sovereign's operational agents (can mirror SIS 7 or declare new)
├── memory/                   — sovereign vault directory (6 vaults or their own taxonomy)
└── private/                  — gitignored; instance state stays here