sound-sync-brief-fit

/sound-sync-brief-fit

Load verticals/sound-intelligence/SKILL.md, verticals/sound-intelligence/SOUL.md, verticals/sound-intelligence/MEMORY.md, agents/starlight-sound-sync.md, skills/sound-intelligence/sync-licensing.md, the catalog state files at sound-intelligence/catalog/<release-state-files> if present in the practitioner's runtime vault (this path is instance-state, not substrate-shipped), and active vision boundaries from MEMORY.md. Produce a Brief-Fit Verdict — pass to placement thesis OR refuse with documented rationale. Hand off to exactly one next command.

Disclaimer (non-waivable)

Sync placement decisions touch rights law, contributor splits, sample clearances, AI involvement disclosure, and brand-association liability. This is system architecture, not legal advice. Every specific placement requires sign-off from the practitioner's qualified music counsel. Vision-boundary refusal is non-waivable; the boundary either holds or gets revised at MEMORY.md level deliberately, never "this once" under deal pressure.

Input

$ARGUMENTS

Process

1. Disclaim. Non-waivable opener.
2. Read brief. Brief content, source (library / direct-supervisor / brand / agency), budget range if disclosed, timeline, content context (film / TV / commercial / trailer / branded content / political / video game / etc.), exclusivity request.
3. Axis 1 — Catalog match. Does the practitioner have tracks that fit the brief? Search catalog by mood / tempo / instrumentation / lyric-or-instrumental / emotional arc against brief requirements. Three or more matching candidates → pass. Two matches → conditional pass (named gap). Zero or one match → refuse-on-catalog OR route to Composition for purpose-built work (rare; only when budget justifies).
4. Axis 2 — Master availability. For each candidate track: does the master state allow placement? Rights structure permits sync (no exclusivity-elsewhere conflict)? Sync-availability flag true in metadata? Alternate-master available if brief specifies (sync-grade-dynamic-range master vs. streaming master)?
5. Axis 3 — Rights structure. Per candidate: splits documented; sample clearances complete; AI involvement disclosed (per /sip-attest-audio doctrine); contributor consents on file. Any incomplete clearance → flag and refuse on this axis until resolved.
6. Axis 4 — Vision-boundary respect. Pull active vision boundaries from MEMORY.md. Common: refuses-political-campaign-sync, refuses-violence-soundtrack, refuses-extractive-fossil-fuel-brand, refuses-AI-vocal-impersonation-license-out, refuses-children's-content-without-curated-fit. Per-practitioner the list varies. Compare brief to each active boundary. Any contradiction → non-waivable refuse. The deal pressure does not override; if the boundary is to be revised, that revision happens at MEMORY.md, deliberately, not "this once."
7. Verdict synthesis.
   • All four axes pass → PROCEED to /sound-sync-placement-thesis.
   • Catalog or master axis fails → REFUSE-ON-AXIS, document, no further sync work for this brief.
   • Rights-structure axis fails → REFUSE-PENDING-CLEARANCE, document gaps, route to clearance work before re-running.
   • Vision-boundary axis fails → REFUSE-ON-BOUNDARY, document, communicate the refusal honestly to brief source if relationship warrants.
8. Document refusal. Refusals are first-class artifacts. The refusal-on-boundary letter (when relationship warrants) is in practitioner's voice via Genius — direct, warm, non-apologetic, non-compromising.
9. Save. Write to sound-intelligence/sync/brief-fit-<brief-slug>-<YYYY-MM-DD>.md.
10. Hand off. Name exactly one next move:
    • PROCEED → /sound-sync-placement-thesis.
    • REFUSE-ON-CLEARANCE → clearance work (sample clearance, contributor-split documentation, AI disclosure).
    • REFUSE-ON-BOUNDARY → refusal letter (if relationship warrants); MEMORY.md boundary update if practitioner wants to deliberately revise (rare).