LaunchRepoDefinition
A draft is a submission in preparation: the form is partly or fully filled, assets are uploaded, maybe a preview was saved — but the final submit was not confirmed. Submitted (in LaunchRepo: submitted_pending_review) means the platform explicitly acknowledged receipt: a confirmation screen, a dashboard row, a label such as “Under review”.
Between the two sits prepared_needs_human: everything is ready but a CAPTCHA, a two-factor prompt or an unclear account state blocks the final step and only a person can clear it.
Why it matters for a directory launch
The line between draft and submitted is where duplicates are born. A click that timed out may or may not have reached the server; retrying blindly creates a second submission and, on platforms that allow one pending launch per account, gets you blocked. Recording “submitted” without an acknowledgement is the first inflated number in a launch report.
How LaunchRepo handles it
The runbook rule is: after a timeout, search the platform for the product name and domain and inspect the account before retrying — a timeout describes the browser response, not the server outcome. Drafts are recorded as draft with a note on what is missing; the state becomes submitted only after an explicit acknowledgement. Handoffs get their own state with the exact next action.
See the term in the repository
LaunchRepo is 346 directory playbooks, a product context file and a submission tracker your own agent runs. Pay €99.98 once; use it for every product you own.
See pricing