Publish

Publish gathers release evidence and project history without inventing a second authority. The song’s TypeScript files, compiled structure, Audio Session, managed assets, and render provenance remain the truth.

Production Proof

Production Proof renders the full current arrangement and reports independent checks for:

• source/compiled revision freshness and compile state;
• sections, tracks, arrangement length, and renderable shape;
• engine ownership, worklets, output route, pending/failed assets, and health;
• integrated LUFS and true peak;
• referenced assets and devices;
• fallbacks and structured degradations;
• completed revision-bound offline render provenance.

A check can pass, warn, fail, or remain pending. There is no readiness score. The proof says what was demonstrated and what still needs a producer or hardware test.

Musical Change Requests

Branches are reviewed as Musical Change Requests:

• the complete multi-file line diff is authoritative;
• stable source ids summarize changed sections, tracks, devices, clips, assets, and lyrics;
• current and candidate projects compile independently;
• matching eight-bar revision-bound renders provide A/B audio and the same production checks;
• merge adopts the complete branch file set after automatically snapshotting the target.

The first version has no hidden partial-merge state or persisted approval database. Rejecting a request leaves both songs unchanged; accepting remains reversible through History.

History

History lists named and automatic snapshots. Restoring a snapshot writes its complete file set back through the shared Yjs document, so connected editors, compilation, and collaborators follow the same change.

Registry

The Registry distributes single-file TypeScript packages. Install creates a normal project module that imports only @barline/core; packages therefore remain readable, editable, deterministic, and composable with the rest of the song.

Publication and remixing

Members can change title, publish state, and remix permission. Public remixes preserve lineage and licensing; private development branches remain distinct from public remix descendants and are the only valid merge sources.

MCP parity

The AI collaborator can compose the same work:

• get_song, get_status, and render_and_measure build Production Proof;
• list_branches, get_song, matching render_and_measure calls, and merge_branch review and accept a Change Request;
• snapshot, project, publication, package, asset, and render tools cover the remaining Publish operations.

Audio operations require an open Studio tab for each target song because the browser is the audio engine.