Cadence Creator Workflow

# Generation contract A Cadence request includes creative controls and returns a generation job. The completed job produces an audio artifact with duration, hash, and generation metadata. Publication to Explore is a separate operation. Do not call a track complete until the audio validates and durable checkpointing succeeds.

# Create a track Confirm ACE-Step is healthy and the queue has capacity. Submit one short, clearly labeled test request, wait for completion, play the output, and inspect duration and metadata. A user-triggered test must not interrupt the serial benchmark controller. If the service reports capacity, wait instead of launching retries.

# Explore Open the public Explore catalog, select an album, play a track, and show the region and genre context. Existing published albums are available while the expanded benchmark corpus continues to generate. Do not claim that the new 74-album corpus is published until the full validation and publication controller reports success.

# Creator tools Use a known demo track to show upload or selection, trimming, sampling, BPM and key analysis, sheet-music views, and creator-ready export controls. State which tools are production-ready and which are beta. The generated artifact remains traceable to its source job and metadata.

# Benchmark provenance For every completed track, retain the track identifier, timing, duration, hash, request trace, validation outcome, and Azure checkpoint state. Aggregate latency, failure, and throughput evidence into the scheduled benchmark report. Never expose API keys, raw credentials, or private prompts in public telemetry.

# Cadence close Show one complete creator workflow and one public album. Then state the current benchmark status with exact completed and total counts from the controller. The next step can be a creator trial, a model-quality review, or a workflow integration discussion. Do not present benchmark volume as finished work before publication verification.