Operating sequence
Use intake questions to define a cloud-generation job, asset rights, data limits, output acceptance, budget, retention, and approval ownership.
- 01
Ask about purpose and accountability
What business or creative decision will the output support? Who owns the project, who may operate the account, who approves the result, and who handles an incident? What audience, channel, territory, deadline, and lifespan apply? What would make the job unnecessary or unsafe? Require an acceptance statement that can be tested on a file, not “make it good.” Ask whether the phrase “Atlas Cloud Generator” refers to a verified service, an internal label, or only the discovered query. This prevents the brief from silently assigning trust to an ambiguous name.
- 02
Ask about assets and data boundaries
Which prompts, images, video, audio, brand materials, or personal data are proposed as inputs? For each, who owns it, what permission allows transformation, and may it be uploaded to the verified service under current terms? What content is prohibited, confidential, regulated, embargoed, or subject to deletion? Ask for approved alternatives when an asset cannot enter the cloud workflow. Require the requester to separate inspiration from material intended for direct input and to name the person who resolves a rights or privacy uncertainty.
- 03
Ask about outputs and service evidence
What file properties, duration, variants, editability, safety review, provenance record, and delivery package are required? What budget and retry ceiling apply, and when must the operator stop? Which current official source supports the account access, terms, pricing, controls, retention, and export behavior the plan relies on? Ask how outputs will be downloaded, named, stored, reviewed, approved, and deleted. Any unanswered service question remains a blocker or explicit assumption; circulation metrics cannot fill it, and one observed job cannot establish general quality or repeatability.