alliance-forge

/alliance-forge

Load SIP.md, ALLIANCE.md, AGENTS.md. Forge a new SIP alliance with full scaffold + compliance checks.

Input

$ARGUMENTS

Process

1. Validate the four forging conditions (per ALLIANCE.md):

   • Skill complementarity: ask the user to name what each node uniquely holds. If any two nodes' domains overlap such that one could absorb the other, halt and recommend services contract instead.
   • Non-zero-sum value: ask for one artifact the alliance will ship that none of the nodes could ship alone. If none, halt.
   • Sovereignty is possible: ask for each node's declared domain. If domains collide on decision rights, halt and recommend domain reshaping.
   • Attestation is wanted: confirm each node agrees to "Built on SIP" attribution on cross-node artifacts. If any node declines, halt.

2. Build the node declaration for each member. Enforce the full YAML schema from ALLIANCE.md § Node definition. Missing fields = node not ready; do not paper over.

3. Scaffold the alliance repo structure:

<alliance-name>/
├── README.md             — what this alliance is, members, cadence
├── SKILL.md              — alliance protocol fingerprint
├── AGENTS.md             — per-node voices (from starlight/AGENTS.md template)
├── MEMORY.md             — cycle 0 state
└── .claude/commands/
    ├── alliance-reflect.md
    ├── alliance-decide.md
    └── <alliance-name>-specific commands as needed

1. Write the alliance's SKILL.md — names the alliance, lists nodes, references SIP version, declares cycle cadence and attestation commitment.

2. Write the alliance's AGENTS.md — map canonical voices (architect / sovereign-creator / protocol-defender / implementer / overseer) to declared nodes. Unfilled voices are visible gaps.

3. Write the alliance's MEMORY.md — cycle 0 state, active commitments (empty), open forks (empty), external IDs placeholders.

4. Install alliance-scoped commands — copy alliance-reflect.md and alliance-decide.md from starlight/.claude/commands/, customized with alliance name.