# One fruit-slice drop: keep the slice singular and land on the plate

Describe one low-height ingredient drop with one clear landing and a settled ending. The original still is a staged practice input; it does not demonstrate a tested H3 drop or physically measured impact.

## Package and evidence

The first-frame SVG is original artwork authored for this task. The PNG is the raster upload derivative prepared during integration. Neither image is a model output. The illustration has no teaching text or arrows baked into the input.

Files: `first-frame.svg`, `first-frame.png`, `brief.en.json`, `brief.zh.json`, `checks.csv`, `README.en.md`, `README.zh.md`. The CSV result fields are intentionally blank; fill them from a clip you actually inspect.

## Prepare

1. Use the supplied single orange slice above a plain plate, or your own permitted source with a clear gap between slice and plate. No knife or cutting action is part of this task.
2. Keep the intended landing region visible and empty. A patterned plate or a pile of fruit can hide duplication and the first contact.
3. Choose a short downward path with the slice face visible. Large spins expose a hidden back and complicate segment-pattern checks.
4. Decide on a soft landing without a visible rebound. If real food behavior or exact material impact matters, use captured footage rather than treating this as simulation.

## Copyable prompt

```text
Begin from the uploaded single orange slice suspended a short distance above the empty plate. The camera and plate remain still. The one slice descends straight down a short distance onto the open center of the plate, keeping its round outline, rind thickness and visible segment pattern coherent. It makes one clear gentle contact with the plate and comes to rest there without bouncing up, splitting or cloning. Keep the slice face largely visible during the fall. The plate remains intact and the slice does not pass through its surface. End on the single settled slice. No cutting, no extra fruit, no splash or added text.
```

## Run and inspect

1. **Check the object count at the start.** Count one rind outline and one segment pattern, and confirm a visible air gap above the plate. Remove extra ingredients from the input rather than relying on a negative list.
2. **Write descent and rest together.** Specify straight down, one contact, then rest. Avoid slow-motion explosion, dynamic toss or looping drop language that requests additional behaviors.
3. **Locate the first contact.** Advance around the moment the lower rind reaches the plate. There should be no gap after rest, no penetration through the plate and no second slice replacing the falling one.
4. **Compare the food structure.** Check rind thickness and segment arrangement before and after landing. If the slice becomes a wedge or spreads flat, reduce only the requested drop height and keep the final rest condition.

## Acceptance

- There is exactly one fruit slice at the start, during descent and at rest.
- The slice travels down toward the plate rather than sideways out of frame.
- The visible rind and segment layout remain coherent.
- The slice keeps plausible thickness instead of flattening into a painted disc.
- First contact occurs on the visible plate surface inside its rim.
- The slice neither penetrates the plate nor rebounds into a second landing.
- The final shot holds one resting slice and an unchanged plate.

## Change one variable per retry

- **A second slice appears on landing:** Change only the object-role sentence to the same single slice throughout; keep the landing target unchanged.
- **The slice falls through the plate:** Reduce only the fall distance and emphasize a final surface contact; inspect the first-contact frames again.
- **The slice spins and changes its cut pattern:** Remove only the spin/toss wording and keep the face largely visible during a straight descent.
- **It bounces repeatedly:** Change only the ending to one gentle contact and rest; remove elastic or looping motion language.

## Ending

Finish with one slice visibly supported inside the plate rim. Retain the frame immediately before contact and the first resting frame as evidence for the contact check.

## Intent evidence and boundaries

Historical parent queries below are literal entries in `docs/research/pseo-keyword-gap-2026-10-05/evidence/bing-live-keywords.csv`. This package claims no exact long-tail demand measurement or search volume. The owner plan at `docs/research/pseo-complete-plan-2026-10-09/keyword-owner-work.csv` assigns broad prompt-template intent to `/templates` and distinguishes complete task presets from prompt collections.

- `minimax h3 image to video`
- `minimax h3提示词模板`
- `minimax h3 prompt guide`

A single citrus slice drops onto a clear plate landing area, preserving segment pattern, slice thickness and one contact event without cloned fruit or repeated bouncing.

- `/blog/image-to-video-motion-prompts`: This package supplies one airborne slice, a target plate and contact-event checks; the broad motion tutorial has no task-specific landing fixture.
- `/blog/product-video-shot-list`: It covers one inspectable ingredient drop rather than a food-video shot sequence.

Keep the original source, your submitted prompt, the provider settings actually available to you and your observed checks together. This package does not prescribe hidden provider tokens, exact duration, cost or supported endpoint parameters.