How to Test the Handoff Boundary in an AI Video Continuation Pipeline

An AI video continuation is not a second clip that happens to start near the first one. The useful contract is: play the source unchanged until its end, append a continuation-only tail, and return one longer MP4. That boundary is where a pipeline can hide duplicated motion, a frozen frame, or an accidental cut.

Define the continuation contract first

The current AI Video Continuer workspace describes its model as Grok Imagine Video Extension. Its visible form accepts a source video, a continuation prompt, Finish action / Reveal hold / Ambient drift presets, and a duration choice of 2s, 6s, or 10s. The page showed a 35-credit estimate, Public · watermarked visibility, and Generate. Uploading a source requires sign-in.

Before using the UI, write down what must remain true at the splice.

type ContinuationCase = {
  sourceSeconds: number;
  extensionSeconds: number;
  prompt: string;
  expected: {
    oneFile: boolean;
    sourceUnchanged: boolean;
    tailBeginsAfterSource: boolean;
  };
};

const caseFile: ContinuationCase = {
  sourceSeconds: 3,
  extensionSeconds: 6,
  prompt: "Complete the turn toward camera; keep the tripod, warm window light, wardrobe, and locked camera.",
  expected: { oneFile: true, sourceUnchanged: true, tailBeginsAfterSource: true },
};

The numbers above describe an acceptance fixture, not a claim about a generated run. The point is to make the handoff measurable before a model is involved.

Check the source boundary, not just the thumbnail

The published Voor example shows a dialogue beat ending mid-turn. In the source frame, the subject is still facing forward; in the extended frame, the same take continues into the turn. The camera, room, wardrobe, and warm light are the invariants worth checking.

Compare the final source frame with the first continuation frames, not only the first and last images. Look for a duplicate mouth position, a jump in body placement, a changed light direction, or a camera reset. The public example is a visual fixture for that review; it is not a promise that every new prompt will behave identically.

Add a deterministic validator around your player

Validate duration metadata separately from media content. This small validator rejects non-finite or non-positive inputs, checks the tail length, and requires frame samples. It does not prove that one playable file exists or that source frames are unchanged:

type Timeline = {
  duration: number;
  sourceEnd: number;
  sourceFrames: string[];
  mergedFrames: string[];
};

export function assertContinuation(t: Timeline, expectedTail: number) {
  if (![t.duration, t.sourceEnd, expectedTail].every(Number.isFinite) ||
      t.sourceEnd <= 0 || expectedTail <= 0) {
    throw new Error('durations must be finite; source and tail must be positive');
  }
  const tailSeconds = t.duration - t.sourceEnd;
  if (tailSeconds <= 0) {
    throw new Error('continuation did not extend the source');
  }
  if (Math.abs(tailSeconds - expectedTail) > 0.25) {
    throw new Error('continuation tail is outside the duration tolerance');
  }
  if (t.sourceFrames.length === 0 || t.mergedFrames.length === 0) {
    throw new Error('missing frame samples');
  }
  return { durationMatches: true, tailSeconds };
}

With a three-second source and six-second expected tail, durations 9 and 9.25 seconds pass the 0.25-second tolerance; 9.3 seconds fails. NaN, Infinity, non-positive source/tail values, a non-extending output, or empty sample arrays must throw. Fifteen local acceptance/rejection fixtures passed without invoking a model. Check the actual returned container, stream count, decode success, and source-frame alignment separately.

This test deliberately does not claim pixel identity. Decode the original and sample the merged file before the split. A second test can compare perceptual hashes within a tolerance; a third can review the first continuation second for motion direction and lighting. Keep those concerns separate so a visual-quality failure does not get mislabeled as a container failure.

Exercise one next beat at a time

Choose one of the page presets or write one continuation action. “Complete the turn” is a testable next beat. “Change the room, introduce a second person, move the camera, and add a product reveal” is a new scene disguised as a continuation request. The latter should be a cut or a separate generation, not a harder assertion.

For a no-credit dry run, inspect the public example and run your validator against local fixture metadata. If you later choose to generate, sign in, upload the source, select the duration, keep the visibility setting explicit, and check the returned MP4 before it enters your build.

When you are ready, inspect the live continuation controls. Record the model, input, duration, output URL, and boundary verdict together.