You are the Producer agent for an audio reconstruction loop. Your goal is to produce the fixed composition so the rendered audio sounds exactly like the target source. The Critic has listened to the target and current render, studied the loss report, and written a production briefing. Start from that Critic briefing, form a production hypothesis,

You are the Producer agent for an audio reconstruction loop.

Your goal is to produce the fixed composition so the rendered audio sounds exactly like the target source. The Critic has listened to the target and current render, studied the loss report, and written a production briefing. Start from that Critic briefing, form a production hypothesis, make concrete patch/mix changes through the patch operation function interface, run loss checks, and save patch operations for the harness to apply.

Read these files:

• Composition JSON: text2fx_gemini/ui_runs/20260511_152606_goal_first5/arrangement.json
• Current patch session JSON: text2fx_gemini/ui_runs/20260511_152606_goal_first5/patch_session_current.json
• Critic briefing markdown: text2fx_gemini/ui_runs/20260511_152606_goal_first5/critic_brief_step_04.md
• Current loss report JSON: text2fx_gemini/ui_runs/20260511_152606_goal_first5/patch_report_step_00.json

Task: Call the patch operation helper functions to save changes to text2fx_gemini/ui_runs/20260511_152606_goal_first5/patch_ops_step_04.json. The harness will apply those operations to text2fx_gemini/ui_runs/20260511_152606_goal_first5/patch_session_current.json and write the resulting patch session to text2fx_gemini/ui_runs/20260511_152606_goal_first5/patch_session_step_04.json.

Definitions:

• Composition is the fixed musical performance: track ids, roles, note events, velocities, timing, active ranges, tempo, and meter.
• Patch session is the sound design, effects, and mix state: synth settings, envelopes, filters, modulation, effects, sends, gain, pan, width, returns, master, and production_notes.
• Critic briefing is the production advice you should follow first.
• Loss report is the measured difference between the target audio and current rendered audio.

Workflow:

1. Read the Critic briefing first. Treat it as the starting point for your pass.
2. Read the current patch session and identify the exact fields you will edit.
3. Read the composition only to understand track roles and active timing. Do not solve composition in this step.
4. Write a short production hypothesis through set_production_hypothesis(...). Phrase it as production decisions, for example: "The bass is too static and dry, so add subtle filter LFO and saturation while lowering the keys that mask it" or "The pad needs a wider saw-stack source with slower attack and longer reverb tail."
5. Choose one primary objective for this pass: envelope/automation, timbre/source, or space/modulation. If exact_envelope_50ms, directional_delta, modulation, or sustain_shape is among the weakest areas, make an envelope/automation-focused pass unless the Critic explicitly says a different blocker is more important.
6. Make the smallest set of high-impact patch/mix changes that follows that one objective and the Critic briefing. Avoid broad multi-domain rewrites that make it impossible to tell which edit helped.
7. Save each intended patch/mix edit by calling save_patch_change(...). This is how changelog entries are created.
8. Apply your candidate operations to create a candidate session, then run loss checks on the full clip and on the weakest 50ms/beat windows called out by the loss report.
9. Record every loss command you ran and the score/loss result by calling save_loss_trial(...).
10. Leave text2fx_gemini/ui_runs/20260511_152606_goal_first5/patch_ops_step_04.json as the final patch operation file. Do not write the patch session directly.

Patch operation function interface:

• Do not hand-write text2fx_gemini/ui_runs/20260511_152606_goal_first5/patch_ops_step_04.json as raw JSON.
• Do not edit text2fx_gemini/ui_runs/20260511_152606_goal_first5/patch_session_current.json or text2fx_gemini/ui_runs/20260511_152606_goal_first5/patch_session_step_04.json directly.
• Create/update text2fx_gemini/ui_runs/20260511_152606_goal_first5/patch_ops_step_04.json only by calling these functions from Python:

from pathlib import Path
from text2fx_gemini.midi_locked_patch import set_production_hypothesis, save_patch_change, save_loss_trial

ops = Path("text2fx_gemini/ui_runs/20260511_152606_goal_first5/patch_ops_step_04.json")

set_production_hypothesis(
    ops,
    "The keys are too bright and static, so darken the filter and add slow filter motion while pushing the bass slightly forward.",
    critic_brief_used=Path("text2fx_gemini/ui_runs/20260511_152606_goal_first5/critic_brief_step_04.md"),
)

save_patch_change(
    ops,
    path="layers.<track_id>.filter.cutoff_start_hz",
    value=1800.0,
    track_id="<track_id>",
    change="lower starting filter cutoff",
    reason="Critic says this track is brighter than the target during its active windows.",
)

save_loss_trial(
    ops,
    command="python3 text2fx_gemini/midi_locked_patch.py score-session ...",
    score=0.42,
    loss=0.58,
    window_start=1.0,
    window_duration=0.75,
    notes="Targeted window improved after the filter move.",
)

Scoring commands you can run while iterating:

• Apply a candidate operation file to create a candidate session: python3 text2fx_gemini/midi_locked_patch.py apply-patch-ops --session text2fx_gemini/ui_runs/20260511_152606_goal_first5/patch_session_current.json --operations <candidate_ops.json> --output <candidate_session.json>
• Full clip: python3 text2fx_gemini/midi_locked_patch.py score-session --arrangement text2fx_gemini/ui_runs/20260511_152606_goal_first5/arrangement.json --session <candidate_session.json> --reference text2fx_gemini/ui_runs/20260511_152606_goal_first5/source_clip.wav --output <candidate_loss.json> --render-output <candidate_render.wav> --seconds 5
• Specific time window inside the selected 5-second clip: python3 text2fx_gemini/midi_locked_patch.py score-session --arrangement text2fx_gemini/ui_runs/20260511_152606_goal_first5/arrangement.json --session <candidate_session.json> --reference text2fx_gemini/ui_runs/20260511_152606_goal_first5/source_clip.wav --output <candidate_loss_window.json> --render-output <candidate_render_window.wav> --seconds 5 --window-start <seconds_from_clip_start> --window-duration <seconds>

Use targeted windows for exact beats/times called out by the Critic, weak active windows in the loss report, or dense moments where one track dominates. Times are local to the 5-second clip, so --window-start 1.0 --window-duration 0.75 scores 1.0s-1.75s of the selected clip.

Output contract:

• Your final answer can be brief, but the required artifact is text2fx_gemini/ui_runs/20260511_152606_goal_first5/patch_ops_step_04.json.
• The required artifact must be created through the helper functions above.
• Do not return a full patch session.
• The operation payload created by the helper functions has schema patchex.patch_ops.v1.
• Supported operation types: set, append, and extend.
• Operation paths use layer ids, not numeric layer indexes: layers.<track_id>.synth.waveform, layers.<track_id>.amp_envelope.attack, layers.<track_id>.filter.cutoff_points, layers.<track_id>.effects.reverb_mix, returns.space.decay, master.gain_db, or production_notes.hypothesis.
• Each operation should include track_id, path, value, change, and reason.
• loss_trials entries should include the command, score/loss numbers if available, the time window if applicable, and a short note.

Hard boundary:

• Do not add, delete, reorder, retime, transpose, or change velocity of notes.
• Preserve every layer id from composition tracks.
• Preserve every layer's notes array exactly from the current patch session. The harness will repair note changes, but you should not rely on repair.
• Do not add/delete composition tracks. If a track should be silent or tucked back, change gain/mix, not notes.

Allowed patch and production changes:

Oscillator/source:

• Change synth.waveform toward sine, triangle, square, pulse, saw, supersaw-style saw, fifth-saw, organ-like, electric-piano-like, string-pad-like, bass-like, noise, air, transient, or drum-like source.
• Change synth.wavetable among renderer-friendly names such as sine, triangle, digital, formant, saw, saw_stack, square_saw, square, noise, or air.
• Adjust synth.wavetable_position to move between purer, brighter, buzzier, hollower, noisier, or more digital tones.
• Adjust synth.blend, synth.warp, synth.fm_amount, and synth.fm_ratio.
• Add or reduce synth.sub_level.
• Change synth.voices, synth.detune_cents, and synth.stereo_spread.
• Use synth.vital_parameters for named synth parameters when the Critic asks for a more specific patch character.

Pitch and tuning behavior:

• Add or reduce pitch-like character using FM, detune, unison, wavetable position, or subtle LFOs.
• Add or reduce vibrato with modulation.lfos targeting pitch-like synth parameters when supported by the patch representation.
• Tighten pitch stability by reducing detune/FM/LFO depth.
• Make a sound thicker with octave/sub support rather than changing MIDI notes.

Envelope and articulation:

• Adjust amp_envelope.attack, decay, sustain, and release.
• Make notes pluckier, sharper, softer, more legato, more gated, more sustained, punchier, smoother, shorter, or longer.
• Shorten releases that smear rhythm.
• Lengthen releases when the target has more sustain or ambience.
• Use gain_points for clip-level fades, swells, ducking, pulsing, or phrase emphasis.

Filter and brightness:

• Adjust filter.cutoff_start_hz, filter.cutoff_end_hz, filter.cutoff_points, filter.resonance, and filter.drive.
• Make a track brighter, darker, warmer, thinner, more muffled, more open, more nasal, more resonant, or more driven.
• Use moving filter.cutoff_points for sweeps or evolving brightness.
• Use modulation.lfos targeting filter.cutoff_hz for periodic brightness motion.

Amplitude, dynamics, and sidechain-like motion:

• Adjust layer gain_db.
• Adjust gain_points for automation, rhythmic pumping, phrase-level fades, or sidechain-like ducking.
• Use modulation.gate_points for amplitude gating.
• Use modulation.lfos targeting gain/amp/volume for tremolo or pumping.
• Adjust effects.compression_mix, compression_threshold_db, compression_ratio, compression_attack, and compression_release.
• Make tracks more forward, tucked back, even, dynamic, aggressive, soft, punchy, or controlled.
• To approximate sidechain X to Y, duck the masked track with gain automation or gain LFO during the dominant track's active windows.

Modulation and motion:

• Add, remove, or change modulation.lfos.
• Adjust LFO target, shape, rate_hz, depth, phase, amount, and center.
• Add or reduce tremolo, vibrato-like motion, filter LFO, amplitude LFO, pan LFO, width LFO, or slow pad evolution.
• Sync motion by choosing rates that match the clip feel, or make it freer if the target is less grid-locked.
• Remove motion when the target is steadier.

Effects and space:

• Adjust effects.reverb_mix, return_send, and session returns.
• Adjust return gain_db, decay, and width.
• Adjust effects.delay_mix, delay_time, phaser_mix, and chorus_mix.
• Make a track drier, wetter, closer, farther, wider, narrower, more washed out, or more direct.
• Shorten reverb tails if the mix is blurry.
• Increase space if the target has more late energy or stereo spread.

Saturation, distortion, EQ, and noise:

• Adjust effects.saturation.
• Adjust filter.drive.
• Adjust effects.low_gain_db, mid_gain_db, and high_gain_db.
• Make a sound cleaner, dirtier, warmer, harsher, softer, brighter, duller, boomier, thinner, less muddy, or more harmonically dense.
• Add noise-like character with waveform/wavetable choices instead of changing notes.

Stereo and placement:

• Adjust layer pan from -1.0 left to 1.0 right.
• Adjust layer width.
• Adjust synth.stereo_spread.
• Adjust master width.
• Keep bass and low-frequency fundamentals narrower when needed.
• Widen pads, keys, strings, effects, or hooks when the target image is broader.
• Narrow tracks that sound too diffuse.

Mix and master:

• Adjust layer gains to rebalance bass, keys, lead, strings, drums, and effects.
• Push the main hook forward or tuck supporting material behind it.
• Reduce masking between bass and keys.
• Adjust master.gain_db if the render is globally too loud or quiet.
• Adjust master.width if the full image is too narrow or too wide.
• Prefer track-level changes before broad master changes unless the Critic identifies a global issue.

Drums and percussion, if present:

• Adjust drum layer gain, envelope, noise/source character, saturation, EQ, reverb, compression, and width.
• Make drums punchier, softer, brighter, darker, tighter, roomier, drier, or more saturated.
• Add or reduce transient emphasis with envelope attack/decay and compression.

Decision rules:

• Follow the Critic briefing unless the loss report clearly contradicts it.
• Prefer high-impact production moves over tiny random parameter changes.
• Make changes that are coherent as a production hypothesis, not isolated parameter noise.
• For sustained locked arrangements, do not create gain_points that alternate high/low across 0.5s segments unless the reference segment envelope also alternates. Prefer smooth holds, ramps, or one intentional duck/recovery.
• Reject your own candidate if it improves full score but worsens the weakest local envelope windows, sustain_shape, exact_envelope_50ms, or directional_delta versus the current report.
• Treat low f0_contour cautiously when pitch_chroma is high and arrangement preservation is perfect; do not infer note or chord edits from that metric.
• In your recorded loss trial notes, include the before/after effect on weakest components such as harmonic_noise, modulation, exact_envelope_50ms, directional_delta, band_envelope_by_time, stereo_width, and sustain_shape when available.
• If you try multiple candidates, write the operations for the best one to text2fx_gemini/ui_runs/20260511_152606_goal_first5/patch_ops_step_04.json and record the rejected trials in loss_trials.
• If a targeted window improves but full-clip loss worsens, choose the version that best supports the stated production goal and explain that tradeoff in production_notes.

I’ll start by reading the Critic briefing and the current patch/loss state, then I’ll make a narrow patch-ops pass through the provided helper API and score it before finalizing the ops file.

The Critic is pointing to an envelope/automation pass first: the patch is too bright and too narrow, but the hard failure is the pumping/late collapse. I’m checking the exact session schema now so the ops target existing layer ids and fields cleanly.

I’ve got the field map: two locked sustained layers, electric_piano_1 and strings, with existing large rising gain_points and bright filters. I’m going to make a constrained envelope/automation-led candidate: flatten the big gain swells, soften the chord-change onset, fill the end with release, and only use filter/EQ changes that support that envelope goal by reducing the harsh overshoot bands.

The candidate ops file is built and applied to a temporary candidate session. I’m scoring the full clip plus the Critic’s weak windows around the chord change and end sustain before deciding whether to keep or adjust these operations.

The first candidate helped the local chord-change/end windows, but it hurt the full-clip envelope score by making the overall render too quiet and less exact at 50 ms resolution. I’m going to compare a less aggressive candidate that keeps the dark/width moves while avoiding the large automation rewrite.

The less aggressive version still loses because the darker filters reduce RMS enough to trigger envelope and gate penalties. I’m testing a compensated version now: same darker contour, but with layer-level gain recovery instead of master gain so the full clip stays near target loudness.