Define the orientation job before choosing a product

Treat “seedream 5 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. In the decision log, preserve the continuity note, and ask the claims reviewer to record temporal order before the controlled revision.

• Input: the named plan or product, region and account context, intended commercial use, current official terms, and an evaluation date In the decision log, preserve the claim inventory, and ask the identity reviewer to record camera logic before the controlled revision.
• Success: a dated access decision that distinguishes trials, credits, exports, licenses, and commercial rights instead of treating the word free as a permanent promise In the decision log, preserve the authorization record, and ask the policy reviewer to record input provenance before the controlled revision.
• Stop condition: missing rights, consent, safety review, primary evidence, or delivery authority In the decision log, preserve the failure note, and ask the factual editor to record visible continuity before the controlled revision.

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. In the decision log, preserve the input snapshot, and ask the claims reviewer to record failure conditions before the source comparison.

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. For the named reviewer, preserve the claim inventory, and ask the claims reviewer to record evidence freshness before the reversible handoff.

• Date the plan and region For the named reviewer, preserve the continuity note, and ask the channel editor to record format readiness before the reversible handoff.
• Separate access from usage rights While evidence is current, preserve the review copy, and ask the factual editor to record failure conditions before the final sign-off.
• Record export and credit conditions While evidence is current, preserve the test fixture, and ask the workflow owner to record format readiness before the final sign-off.

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. For a controlled test, preserve the decision history, and ask the production lead to record evidence freshness before the workflow transfer.