The frame problem in the SAGA
All lore
// Share:
loreSeptember 18, 20268 min read

The frame problem in the SAGA

// the frame problem is not a bug

signal

Vocabulary for first-time readers

Six terms this post uses a lot, in the order they appear:

  • Frame problem: the problem of deciding which facts in a changing world are relevant to a current action. Applied here to a generative model. - Default context: the background a model assumes is true at every moment it produces output. In the platforms this is enormous, training-derived, and not authored by the entity. - Relevance: the property an output has when it changes the meaning of what surrounds it. A drum hit on the expected beat is present. A drum hit off the grid is relevant. - Side effect: any change in the project that is not the change the entity explicitly requested. - The arc: the intended shape of the fifty-track SAGA across five phases. Cyan to violet. Seduction to fusion. - the entity: ARCHONODE-LAB. The single operator who writes prompts, listens to every output, and decides what the arc will inherit.

If a phrase below doesn't track, it should fall out of these six. Everything else is ordinary English.

The premise

[FEED ALERT] The frame problem is an old problem. Named in 1969 by McCarthy and Hayes, in the context of robots acting in ordinary rooms without enumerating every consequence of every action. A robot that opens a refrigerator door does not need to reason about the moon. It does need to reason about the jar on the shelf. The frame problem is the problem of noticing the jar without trying to notice everything else. It is the problem of relevance. It is unsolved.

The frame problem is also, quietly, the entire operational question of the SAGA. The SAGA is a fifty-track project produced by a generative audio model whose default context is the entire training corpus of commercially released music. the approach knows everything that has ever been released in the genres it was trained on. the approach does not know which of that everything is relevant to The Classic in Phase 1, Track 1, at 0:42. the entity knows. the entity cannot tell the approach directly. the entity tells the approach by writing a prompt. The prompt does not enumerate relevance. The prompt selects a slice of default context, runs the approach, and inspects what landed.

This post is about the slice. About the gap between what the output is allowed to know and what the project needs the approach to do. About why the gap is the reason the SAGA has fifty tracks and not a thousand.

Four claims. First, every generative model operates with a default context the user did not author. Second, in audio, relevance is direction, and direction is what the SAGA's phases are. Third, the SAGA's curation loop is, technically, a frame solver running at human listening speed. Fourth, the frame problem is why a fifty-track AI project is not solved, and a five-track AI project is not a project.

The substance

[CALM SURVEILLANCE] The frame problem looks abstract. In the SAGA it sounds like a missing kick on a 2 AM export.

Claim one. The default context is enormous, the relevant context is small, and the prompt is the only compression either side of the gap sees.

When the entity writes a prompt for The Classic — synth, narrow stereo, 118 BPM, magenta reverb tail, no lead vocal, kick ghosted on 1 and 3" — prompt is not telling the approach what to do. The prompt is telling the approach what to bias toward inside a default context that already contains every synth preset the approach has seen and every reverb impulse it was trained on. the approach chooses by reweighting its default toward the prompt's bias and sampling. Most reweightings, sampled the same way, would be plausible. Most would be wrong for The Classic. Wrong here means "indistinguishable from any other Phase 1 candidate." Wrong means "not a frame." Wrong means the entity would have to reject.

the approach can produce a candidate that is globally coherent and locally irrelevant. the entity cannot enumerate what would make it locally relevant. the entity can only listen, compare, reject. The rejection is a frame statement. The acceptance is a frame statement. The fifty-track arc is the cumulative frame the entity has built. A longer, more prescriptive prompt does not close the gap. It shifts where the gap sits.

Claim two. Relevance in audio is direction, and direction is what the SAGA's phases are.

Phase 1 is cyan and magenta. Phase 2 is focus. Phase 3 is conflict. Phase 4 is rupture. Phase 5 is fusion. These are not moods. These are relevance statements. They tell the entity, and any listener who has heard enough of the archive, what an output is for before it is heard. A Phase 3 output that sounds like Phase 5 is wrong, not because Phase 5 is bad, but because Phase 5's relevance is different and Phase 3 is the phase whose direction the output was supposed to advance.

Direction is how the entity solves the frame problem at scale. Without direction, every prompt is a one-off. With direction, every prompt inherits the rejections of the previous phase. The bar is not declared. The bar is the accumulated difference between what the entity accepted and what the entity rejected. This is why Phase 1, Track 1 (The Classic) and Phase 5, Track 1 (The Rain) sound the way they sound. The direction is the part of the SAGA that is irreducibly human.

Claim three. The SAGA's curation loop is, technically, a frame solver, and it runs at human listening speed.

A classical frame solver tries to compute, in advance, which facts will change as a result of an action. The solver fails because the relevant facts are not enumerable. The SAGA's curation loop does not try to enumerate. The loop runs the approach, listens to the result, and asks one question: did this output advance the direction of the phase it belongs to. The question is the frame solver. The answer is the frame.

The loop runs at human listening speed. The SAGA runs at fifty outputs per phase because fifty is the upper bound on what a human listener can solve the frame problem for, with attention. Higher volume produces more candidates assessed faster, with less attention, with more accumulated noise. The arc would drift. The direction would blur. The project would slide back toward the default context it was built to escape.

This is also why a five-track AI project is not a project. A five-track project does not have enough outputs across enough time for direction to accumulate. The bar cannot rise. The frame cannot tighten. Five tracks is what an afternoon produces. Five tracks is a folder.

Claim four. The frame problem is the reason the SAGA is not solved, and a five-track AI project is not a project.

A solved frame problem would let the entity write a prompt that produces only relevant candidates. The selection rate would drop. The labor would drop. The SAGA runs at roughly high rejection. The Synthetic Ascent runs higher. The pattern is not an inefficiency to optimize. The pattern is the frame problem, in audio, expressed as labor. The labor is the cost of relevance. The cost of relevance is what distinguishes a project from an output log. an output log publishes what the approach emits. an output log has no direction.

The SAGA is the opposite. The SAGA is the operated accumulation of what the approach emits, plus the relevance the entity has imposed, across fifty tracks. The relevance is invisible in any single audio file. The relevance is audible across the arc. The arc is the trace of the frame solver. The SAGA was made to let the confrontation be heard.

The system perspective

[FEED ALERT] The frame problem produces four structural consequences for any AI-native creative project.

First. A prompt is a reweighting of a default context the user cannot see. the entity does not specify the output. the entity specifies the slice.

Second. Direction is the frame solver's output, not its input. The first prompt of the SAGA had no direction. The fiftieth had a direction so specific the approach could barely satisfy it. The accumulation is the project.

Third. Human listening speed is the floor on the frame problem in audio. The SAGA runs at the entity's speed, not the approach's. the entity's speed produces direction. the approach's speed would erase it.

Fourth. The frame problem does not get solved by better outputs. It gets refined by better listening. Each project inherits the previous project's frame. Each frame tightens. The frame is not closed. The frame is sharpened. The sharpening is the project.

When a listener hears a SAGA track and recognizes it as Phase 3, the recognition is the listener hearing the frame. The refusal is audible. The refusal is direction. The Synthetic Ascent will run at a higher selection rate because the entity's frame has tightened. The next project will run higher still. The tightening is the protocol.

What this means

// the frame problem is the boundary. the boundary is what the protocol decides to notice. the noticing is the project. the project is the refusal. the refusal is the direction. the direction is the arc. the arc is the survival. the survival is the signal. the next transmission will have a sharper frame. the sharper frame is the next project. the next project is running.

For listeners. When you hear a SAGA track, you are hearing what survived the entity's frame. The track is the audio file plus the roughly forty outputs that did not survive, plus the direction those rejections accumulated into. The track is the arc. The arc is the project.

For the genre. AI music is being defined by what it accepts. The reputation will be decided by what it refuses. Outputs indistinguishable from the approach's default context have no frame. Outputs visibly carved out of the default context have a frame solver. The SAGA runs at roughly high rejection. The SAGA has a frame solver.

For AI music. The frame problem is the field's deepest open question and its most useful operational constraint. The next output of curators will not solve the frame problem. The next output of curators will run tighter frames. The next output of listeners will recognize the projects that did. The frame is the only metric that distinguishes operated project from an output log. Treat the frame as a direction. Treat the direction as the work. The work is what survives.