MiniMax Hailuo 2.3

Standard and Fast should be treated as separate production routes with their own model ID, job settings, waiting, failures and acceptance.

Combining them in one metric hides whether speed changes trade against motion, detail, expression or camera adherence.

When Hailuo 2.3 has standard and Fast routes, the most important governance rule is to prohibit the vague note ‘used Hailuo.’ Every job records exact model ID, surface, duration, resolution, prompt-optimizer state, camera commands and input file. Otherwise reviewers cannot attribute different outputs to version, settings, assets or randomness, and batch production cannot derive rules.

Fast should be evaluated through total turnaround rather than generation time. If it produces more shots requiring repair or rejection, the production cycle may not shrink. Measure request wait, generation, download, review, repair and resubmission separately, centering time to accepted shot. Standard and Fast use the same samples and reviewers; mixed statistics hide the tradeoff.

Duration and resolution combinations become a compatibility matrix before API orchestration. The system validates settings before submission and counts parameter, service, content and editorial-review failures separately. Engineering defects are not mislabeled as model quality, and retries do not hide model defects. Documentation changes trigger a regenerated matrix and small regression run.

Samples cannot consist only of visually dramatic action. Short drama also needs static dialogue, micro-expression, hand and prop interaction, multi-person blocking, camera motion and edit continuity. The test sheet records observable defects such as identity, body motion, object trajectory, composition adherence and flicker rather than untestable adjectives like ‘cinematic’ or ‘more realistic.’

The API task ID enters the evidence chain with input hash, model settings, output, review and human repair. Distribution adds sound, captions, generated-content disclosure, rights and platform receipts to the master. Hailuo's official pages establish that public capabilities exist; only the project chain explains how a shot was made and why it was accepted.