Define the orientation job before choosing a product

Treat “seedream 5.0 free” as a broad orientation request, not as evidence that a feature exists. The action implied by the query is to clarify the term and choose the next production decision; the working object is named model or platform. Write the intended audience or user, authorized input, desired change, review owner, and finished handoff. Also state what the task excludes. This brief keeps search wording from turning into an unsupported promise about SEELE, a named vendor, a model, or an automatic result. For a reversible workflow, preserve the reference set, and ask the channel editor to record input provenance before the final sign-off.

• Input: the named plan or product, region and account context, intended commercial use, current official terms, and an evaluation date For a reversible workflow, preserve the delivery checklist, and ask the claims reviewer to record identity consent before the final sign-off.
• Success: a dated access decision that distinguishes trials, credits, exports, licenses, and commercial rights instead of treating the word free as a permanent promise For a reversible workflow, preserve the evidence table, and ask the release approver to record control availability before the scope confirmation.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority For a reversible workflow, preserve the rights memo, and ask the channel editor to record destination fit before the scope confirmation.

Use the category discovery method

Start by defining the term or named product in neutral language, then separate the reader's likely production job from brand recognition, spelling variants, and search popularity. Build a shortlist of questions before opening any workspace or vendor page. For this query, clarify the intended meaning and production job before choosing a process or product. Keep notes about assumptions, source dates, failed checks, and human decisions beside the working asset. The category-discovery classification determines this learning sequence, while the authoritative taxonomy remains the only owner of the route. This page supplies editorial copy and cannot silently change the category, subhub, or URL. For a reversible workflow, preserve the decision history, and ask the factual editor to record visible continuity before the scope confirmation.

Apply the price, access, and usage terms boundary

Search wording does not prove free access, a download, rolling credits, monetization, commercial rights, or any entitlement. Verify current first-party pricing, plan limits, license terms, and platform policy. Work from the named plan or product, region and account context, intended commercial use, current official terms, and an evaluation date. Review toward a dated access decision that distinguishes trials, credits, exports, licenses, and commercial rights instead of treating the word free as a permanent promise. A polished draft is not enough: the reviewer must be able to see which source supports each factual statement, who authorized each asset or identity, and which product behavior is still an unanswered test question. Topic selection alone never establishes safety, availability, quality, or permission. Before delivery, preserve the review copy, and ask the workflow owner to record destination fit before the reversible handoff.

• Date the plan and region Before delivery, preserve the test fixture, and ask the delivery owner to record evidence freshness before the reversible handoff.
• Separate access from usage rights Before delivery, preserve the claim inventory, and ask the channel editor to record destination fit before the dated decision.
• Record export and credit conditions Before delivery, preserve the continuity note, and ask the release approver to record control availability before the dated decision.

Record evidence, review the handoff, and name the next check

The handoff should state what the reader now understands, which interpretation remains uncertain, and which official source would be needed before a product-specific conclusion is publishable. Run separate passes for craft, factual accuracy, identity and source rights, safety, accessibility, and destination requirements. Record the source and verification date for any changing platform, model, price, policy, privacy, export, or compatibility statement. If primary evidence is missing, publish the item only as a question or editorial planning step. The finished handoff must name the approver and preserve a path back to the authorized original. At the next gate, preserve the delivery checklist, and ask the release approver to record reversal cost before the rights check.