Viral Generator

Define the tool job and source contract

For Viral Maker, specify the material entering the workflow, the transformation expected within general video generation, and the deliverable leaving it. Keep generation, editing, publishing, and measurement as separate responsibilities. For this section 1, save a delivery checklist; have the media owner review motion coherence; record the failed case as well as the accepted one; and do not advance it beyond a source-preserving edit until the named limitation is resolved. Keep maker evidence separate from viral assumptions.

• Name required input rights and formats — record evidence ledger, legal reviewer, delivery fit, and rights-cleared draft; keep maker evidence separate from viral assumptions.
• List controls that must be directly observable — record prompt brief, visual lead, editability, and rights-cleared draft; keep maker evidence separate from viral assumptions.
• Define a reversible review handoff — record shot contract, motion designer, input fidelity, and rights-cleared draft; keep maker evidence separate from viral assumptions.

Compare against a stable acceptance frame

Use the same inputs, review dimensions, and stopping rules for every candidate. Record tradeoffs separately from availability so a promising test is not mistaken for verified product support. For this section 2, save a camera plan; have the technical reviewer review licensing; record the failed case as well as the accepted one; and do not advance it beyond a source-preserving edit until the named limitation is resolved. Keep maker evidence separate from viral assumptions.

Run a bounded tool test

Use one representative asset and a fixed brief. Observe what the interface actually accepts, which controls affect the result, how revisions behave, and what must still be completed elsewhere. Record failures as carefully as successes. For this section 3, save a acceptance matrix; have the fact checker review input fidelity; record the failed case as well as the accepted one; and do not advance it beyond a source-preserving edit until the named limitation is resolved. Keep maker evidence separate from viral assumptions.

Select on workflow fit, not implied automation

Compare review effort, controllability, source fidelity, rights handling, and export readiness. A useful planning page does not upload media, invoke a model, or manufacture a result merely because the query contains the word tool. For this section 4, save a decision memo; have the fact checker review claim support; record the failed case as well as the accepted one; and do not advance it beyond a stakeholder sign-off until the named limitation is resolved. Keep maker evidence separate from viral assumptions.

Keep the evidence ledger attached to the decision

Partial evidence was supplied, but it does not establish product support or a complete capability, customer, or performance claim. Record the source, verification date, claim scope, unresolved gap, and the decision that the evidence can support. Search demand must never be reused as capability proof. For this section 5, save a asset ledger; have the prompt designer review action readability; record the failed case as well as the accepted one; and do not advance it beyond a stakeholder sign-off until the named limitation is resolved. Keep maker evidence separate from viral assumptions.

Build a specific test brief for viral maker

Start with a rights-cleared representative source and a written acceptance brief. Define one observable change, protected details, a stopping rule, and the named reviewer. The intended output is a reviewable visual-production brief and evidence-aware handoff. Test one variable per version, preserve the source and settings, and compare results at the actual delivery size instead of choosing from an unrecorded impression. For this topic test, save a versioned handoff; have the visual lead review continuity; record the failed case as well as the accepted one; and do not advance it beyond a reproducible test until the named limitation is resolved. Keep maker evidence separate from viral assumptions.

• Primary query: viral maker; test record: continuity sheet, post supervisor, revision control, and editorial approval; keep maker evidence separate from viral assumptions.
• Editorial owner: keyword-expansion:0488; decision record: rights record, post supervisor, source rights, and bounded experiment; keep maker evidence separate from viral assumptions.
• Source scope: a user-provided competitor-gap export dated 2026-08-05 supports topic prioritization only; source review: revision log, brand reviewer, licensing, and rights-cleared draft; keep maker evidence separate from viral assumptions.

Separate topic fit from product proof

A dated, user-provided competitor-gap export supports only the decision to cover “viral maker.” It does not prove audience demand, SEELE capability, third-party behavior, commercial value, or a likely outcome. Verify product-specific statements against current first-party documentation and a recorded representative test. For this source review, save a decision memo; have the motion designer review licensing; record the failed case as well as the accepted one; and do not advance it beyond a source-preserving edit until the named limitation is resolved. Keep maker evidence separate from viral assumptions.