Skip to content

Riffmaw

A remembered drop, a guitar take, a sung line, or an empty session can all begin the same craft. Riffmaw makes their contributions attributable while the Magus composes, performs, selects, edits, and produces the musical work. No model, DAW, or generation method owns that judgment.

Ways of making

Road Pattern What can finish here
Forge riffmaw.forge_track@2 Offline composition/generation from a brief, references, lyrics, or empty session: MusicCandidateSet@1 or MusicFindingSet@1.
Perform riffmaw.capture_take@2 Explicitly armed audio/MIDI from played, sung, rapped, musical-spoken-word, or programmed performance: PerformanceTake@1 and observations/findings.
Jam riffmaw.open_jam@2 Performers and admitted machine players answering against mapped clocks: recoverable MusicalPerformanceSession@1 or findings.
Produce riffmaw.forge_music_bundle@2 Bounded arrangement, mix, master, probes and listening review: MusicAssetBundle@1, candidates, findings, or refusal.

Each road settles its own Invocation. Exact artifacts can enter later forward work; one Pattern never nests or silently resumes another. A future Scroll may combine separately named capture/generation/render/review placements under its own revision, Resolution Lock, and authority ceiling. File access does not arm an input; a take does not admit training; a candidate mix is not a master approval; export does not publish.

The work

Find the material in Sources, down to the exact musical moment. When people or machines perform, Sessions preserves their takes and shared time; Hardware admits the capture routes they use. Music develops that material into an arrangement and master candidate.

Choose machinery through Studio, which keeps tool roles and dated candidates separate from the craft. For uncertain roles, Voice distinguishes musical performance from speech, and Sound follows what belongs to music. Sync offers cues for another work; Package seals the musical handoff.

Reference contract

riffmaw.music revision 2 accepts a music brief plus explicitly admitted references, lyrics, takes, MIDI, scores, samples, or live inputs. Alongside the road-specific returns, it can issue MusicCueMap@1. It stops before ordinary dialogue, spoken replacement/localization, picture sound, visuals, final audiovisual assembly, impersonation, and publication. Language Edition, Broadcast, Atelier, and their technical providers retain those offices.

Prompt, lyric, requested sung language, and interface locale remain separate. Exact model profiles must prove their musical/language behavior; a local ComfyUI or other Soulstone binding and a Portal API are independently evidenced implementations. Music owns the request; Studio records candidates.

Revision continuity

Earlier designs and their exact successors

riffmaw.audio revision 1, its Sonic* family, and former riffmaw.forge_track@1, riffmaw.capture_take@1, riffmaw.open_jam@1, riffmaw.index_sources@1, and riffmaw.mark_moment@1 are retired without reinterpretation. New identity riffmaw.music revision 1 used the five Pattern names at @2. Revision 2 advances principal riffmaw.forge_music_bundle to @2 for model-native pre-execution music authority and semantic admission. MusicAssetBundle@1 already accommodates those exact provenance receipts; other music Patterns remain unchanged. No registry, Run, or stored application record used the retired designs, so no executable migration exists.

Audio · Workflow · Composition Portfolio