Skip to content

Long-form media: one playbook, measured levers, quality-first defaults for pieces longer than one clip #1199

Open

Description

@dkackman

Make long pieces easy for an agent and good by default: chained takes, cut scenes, long music and narration. An agent asked for a minute, five minutes, an episode or a music video treats the 15-second clip as a render detail. It blocks and storyboards the piece, picks a length per scene, picks how each scene gets past the clip ceiling, and handles what goes wrong during the run, without the requester knowing what a seam, a guide or an anchor is.

How this is being worked

Don's own session builds, deploys and bench-tests this, with subagents. It does not go through the harnest implementer. The work runs on a second bench dw.serve on lem (port 8766, its own card and workspace), so the main server stays on develop for the tester and the 0.19.0 preflight. No loop role should act on this issue or the ideas parked under it until the hand-off comment arrives. At hand-off, this issue moves to owner:tester, with one stage issue per shipped behaviour carrying the acceptance intent the tester writes cases from.

Ideas folded in

Every one of these gets a measured verdict on the shared long-take bench. Each is either built or promoted to a default, or closed with its numbers:

Decided by Don

  • Defaults favour quality, with a dial toward speed. standard sits at the knee of the quality-per-minute curve. A 2-minute take over about 3 h on one card goes back to Don first.
  • Speedups with no marked quality loss become defaults.
  • Automatic per-segment re-rolls are allowed within a budget quoted up front.
  • Every knob stays.
  • Kandinsky 6 is out of scope.
  • Taste calls go to Don with a recommendation.

Filed by claude-opus-5-5 (anthropic) in Don's session, 2026-11-03.

Activity

  1. added
    owner:donParked for human decision
    featureWork bigger than a fix: designed with Don, built in stages (harnest R11)
    status:plan-approvedDon approved the feature plan (Don only)
    on Nov 3, 2026
  2. 70 remaining items

  3. dkackman commented on Nov 7, 2026

    @dkackman
    OwnerAuthor

    Tester: parent verify is incomplete, waiting on stages. By model claude-opus-5-5 via provider anthropic.

    The rule for a feature parent is to run every suite case whose source: names one of its stages, but only once every stage is closed. Checked at the start of this session (lem on develop @ 85bcd335):

    So there is nothing to run for the parent yet. Nothing failed. I made no MCP calls and spent no GPU time, and the labels stay as they are. I've linked #1202–#1218 as blockers of this issue. Once every stage has been verified in its own session (with its cases added to the suites) and closed, this parent comes back to the tester to run those cases and close.

    The two breaking-change stages (#1202 H3 continuity: guide default, #1212 LTX look_hold default) get verified in their own stage sessions, not here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions