Package

In plain words: Riffmaw: sealed music bundle

Designed 2 min read 3 glossary terms 4 connected pages
The short version written for the Snayu team

How Riffmaw seals accepted music, stems, mixes and masters into a MusicAssetBundle for other apps, and how it handles effects, recovery, revocation and deletion.

Why read it: Read when building the music handoff to Broadcast or Foundry, or its restart and deletion behaviour.
  1. 1The bundle carries checksums, sources and target profiles, but no credentials or publishing permission.
  2. 2A lost write acknowledgement stays unknown and is reconciled before retrying.
  3. 3Separated-source stems are labelled as estimates, distinct from native or rendered stems.

Words on this page, decoded click one for its card

The original text Underlined words open their plain-English card.

A master arrives with stems, credits, findings, and enough lineage to understand how it was made. riffmaw.forge_music_bundle@2 seals accepted composition, instrumental/vocal performances, production effects, stems, mix relationships, and masters into MusicAssetBundle@1 with target profiles, checksums, and exact source revisions.

A compound model-native layer also retains its compound digest and Riffmaw-issued SemanticFacetAdmissionReceipt@1. A visual, timed-language, picture-sound, or world-sound receipt cannot substitute for musical judgment.

Handoff and authority

Broadcast or Foundry independently admits the exact digest, role, format, timing, rights, findings, and approval for its purpose. The bundle carries no SigilID Badge, secret, provider/DAW session, capture permission, performer consent for another use, dialogue/picture-sound authority, editorial placement, or publication permission.

Capture, paid generation, DAW export, and handoff remain separate effects with exact request digests/receipts. A destination may have written bytes before acknowledgement disappeared. Keep that outcome unknown and reconcile the write before another attempt.

To resume interrupted work, resolve the exact source, feature, PatternWorkflow, model, plug-in, session, edit, mix, and export revisions. Recovery needs that chain to distinguish completed output from a new attempt. Takes, rejects, indexes, works, stems, masters, and handoffs keep independent retention.

Revocation or an invalid source makes dependent work stale while preserving its history. Deletion begins by stopping capture/indexing, then removes permitted derivatives, inventories exports, and leaves required content-free receipts. It records what happened to local material without promising that a consumer forgot an exported work.

Proving the bundle

Begin with two local synthetic two-minute references, a frozen thirty-second guitar take, short MIDI, an approved sung fixture, and the 01:32 marker. Use pinned onset/tempo observations and an editable FeelProfile@1 to develop an original four-section arrangement. Produce one generated candidate with a complete receipt, retain the human selection/edit, and add a vocal layer or production-effect print.

Carry that work through intermediate stems, a candidate mix, and a target-conformant technical master. The final bundle must retain three sync markers, restart-safe indexing, and complete lineage so another reader can reconstruct the passage from sources to accepted music.

Label separated estimates separately from native or rendered stems. No ambient folder/microphone, copyrighted catalogue, PortalCloud Model, visuals, paid effect, or platform call enters the proof. Sessions owns the independent live-jam fixture.