sound-intelligence

Coordinate six sound practice sub-systems with SIP v1.1.0 attestation and governance.

6|2|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/frankxai/Starlight-Intelligence-System --skill sound-intelligence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sound-intelligence
Source: https://github.com/frankxai/Starlight-Intelligence-System/tree/main/verticals/sound-intelligence
Command: npx skills add https://github.com/frankxai/Starlight-Intelligence-System --skill sound-intelligence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates six interlocking sub-systems into a sovereign domain stack to help practitioners orchestrate composition, production, catalog, performance, audience, and sync with governance, attestation, and metadata discipline.

Core Features & Use Cases

  • Six sub-systems with shared voice and refusal posture to keep practice coherent across creative, technical, and rights workflows.
  • SIP-based attestation and metadata discipline ensuring verifiable provenance and compliance for releases, sync pitches, and catalog updates.
  • Forkable practitioner reference that can be adopted by independent composers, producers, and labels to run end-to-end release cycles while preserving sovereignty.
  • Productization scaffolding including catalog architecture, release planning, rights management, and audience rituals that compound over cycles.

Quick Start

Fork this vertical to your own repo and run /spawn-domain-stack to initialize your first sub-system.

Frequently Asked Questions about sound-intelligence

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage a music catalog with metadata and sync rights for an independent label?

Managing a music catalog with metadata and sync rights requires coordinating composition, production, and release workflows with verifiable provenance. This Skill provides a sovereign domain stack that enforces metadata discipline and SIP-based attestation across six sub-systems for indie labels.

What is sovereign sound practice and how does attestation work for music releases?

Sovereign sound practice is the end-to-end management of music workflows while retaining full rights and governance control. Attestation works through SIP-based metadata discipline, ensuring verifiable provenance and compliance for releases, catalog updates, and sync pitches.

How do I set up a domain stack for composition and production workflows?

To set up a domain stack for composition and production, fork the vertical reference into your own repository and run the spawn-domain-stack initialization command. This scaffolds the six interlocking sub-systems with shared voice and refusal posture for coherent practice.

Can I use this sovereign stack for sync licensing and audience coordination?

Yes, the sovereign stack supports sync licensing and audience coordination through dedicated sub-systems. It enables practitioners to plan releases, coordinate sync within rights boundaries, and build audience rituals that compound over cycles while preserving sovereignty.

Does this catalog management approach work for independent composers and engineers?

This catalog management approach is designed for independent composers, producers, and engineers building catalogs. The forkable practitioner reference lets solo practitioners run end-to-end release cycles with productization scaffolding for rights management and metadata discipline.

What are the limitations of using a sovereign domain stack for music production?

A limitation of the sovereign domain stack is that it requires practitioners to adopt SIP-based attestation and metadata discipline across all six sub-systems. It is not a lightweight tool; it enforces a shared voice and refusal posture that may not suit teams unwilling to follow strict governance boundaries.