04 / 07 · Weekly free spine
Hold the queue
ASO drafts and SEO/GEO drafts wait in one queue, still labeled.
The channels
Which surface, which words
Apps · ASO
Listing and keyword drafts wait here until you submit them to the App Store. Press stays held until ASO Ready.
SaaS web · SEO/GEO
Page and answer-brief drafts wait here until you publish them on the site. Distribution stays held until Web Ready.
Human in the loop
What PROMACHOS does not do
PROMACHOS does not clear the queue, schedule a send, or treat Ready as permission. ASO Ready is not a listing submission. Web Ready is not a publish. Nothing in the queue ships itself.
Drafts and queues only. You publish. You spend.
Sits with The queue
The step
What it is
The queue is shared. The labels are not. ASO drafts, SEO/GEO drafts, and Amplify plans sit here with a status: draft, needs you, ASO Ready, Web Ready, or held. Work stays in the queue until you publish or you spend.
The reason
Why it exists
One queue is how the week stays visible. Shared storage is not a shared channel. A listing line does not become SEO because it sits beside an answer brief.
The week
What you do this week
- 01Read every waiting item with its channel label in view.
- 02Edit, keep, or drop each ASO draft and each SEO/GEO draft on its own terms.
- 03Leave App Store items unsubmitted, leave site items unpublished, and leave spend items held.
The handoff
Inputs and outputs
Inputs
- ASO drafts pulled toward ASO Ready
- SEO/GEO drafts prepared in Web Ready
- Amplify plans still unapproved, each tied to one gate
Outputs
- A queue of unsent work, still labeled by channel
- A split between items you will send and items that stay