1
Persistent identity beats per-generation beauty
Seedance produced the most photoreal presenter we saw — and we rejected it. It invents a new person every generation, its policy wall means she can never be made consistent, and its auto-voice garbled the one legal term that matters. An owned, growable identity wins on brand equity, compliance, and compounding value.
2
Policy walls are a competitive map
Seedance blocks all photoreal faces in reference images. Kling 3.0 has no such wall — its elements feature accepted our spokeswoman and held her identity across a three-scene single generation. Knowing which engine permits what is as valuable as knowing which is prettiest.
3
Retention is solved; the hook is structural
Seven experiments against a neuro-prediction scorer: sustain scored a perfect 100 every time, while no first-3-seconds treatment moved the hook score more than ±3. The lesson: our content holds viewers; opening-frame gimmicks don't move the needle — front-loading the strongest content might. And: never remove the human from the cold open (scores dropped).
4
Verify with forensics, not vibes
“The lipsync feels off” became a silence-map diff proving the restyle vendor inserts 0.2–0.6s gaps mid-sentence at caption boundaries. We built an automatic repair (tighten_gaps.py) that cuts inside the silences — lipsync-safe, and it recovers 4–8% runtime. Every anomaly this session got the same treatment: measured, root-caused, then fixed in the pipeline permanently.
5
Compliance is a gate, not a note
Competitor analysis of 9 top credit Shorts found they win with claims we legally cannot make (guaranteed deletions, “legal loopholes”). Our answer: a hard compliance gate in the pipeline (verbatim script checks, mandatory no-guarantee line, disclaimer end card) — and a content strategy that turns their violations into our debunk material.
6
The aggregators are convenience, not magic
Higgsfield resells the same engines we hit directly — its real value is three exclusives (Wan avatars, the virality scorer, style restyling) and its failure modes are real (broken MCP video path, opaque errors, plan-gated features). We use it surgically and keep the backbone on direct, pay-per-use APIs with no automation policing.