# Video reference probe mismatch note

Status: corrective note
Captured: 2026-03-29

## Purpose
Record exactly why the recent “use previous generated video as reference for the next clip” test was not SOT-grounded.

## What was attempted
A live billable Omni create was attempted with a hypothesis payload shaped like:
```json
{
  "model_name": "kling-v3-omni",
  "prompt": "...",
  "duration": "5",
  "mode": "std",
  "aspect_ratio": "16:9",
  "video_url": "<base64 video>"
}
```

## What is wrong with that attempt
### 1. `video_url` was a hypothesis field, not a documented SOT field
In the currently reviewed Qingque-derived reference, the confirmed field structures we have explicitly extracted include:
- `image_list[].image_url`
- `image_list[].type = first_frame | end_frame`
- `multi_prompt[].index`
- `multi_prompt[].prompt`
- `multi_prompt[].duration`

We do **not** currently have a documented extracted Omni create-body field showing:
- `video_url`
for direct inline video continuation in the same way it was attempted.

### 2. The run bypassed the SOT-before-create discipline
Because `video_url` was not first confirmed from the Qingque-derived reference layer, this call should have been classified as hypothesis-only before any billable create.

### 3. Success of task creation did not prove video conditioning
The task succeeded and produced a video, but the result did not clearly show that the prior generated video had actually been used as a reference/continuation source.
Therefore:
- create success != reference semantics success
- accepted field != proven conditioning path

## Current corrected interpretation
- The attempted `video_url=<base64 video>` path is **not currently SOT-confirmed**.
- It should be treated as a hypothesis probe that was executed prematurely.
- The result should not be cited as proof of video-reference continuation support.

## What should happen instead
Before the next video-reference test:
1. Re-open Qingque-derived reference sections for element/video-character/video-reference APIs.
2. Identify the documented create path and exact field names.
3. Only then map the workflow into builders/validators and test live.