USE CASES
Each play is the same loop with a different input. The recommended action always comes from the real vocabulary, and one of the seven is deliberately WAIT.
INPUT
product URL
SIGNAL
Which communities are already discussing the problem you solve, and how strong that evidence is right now.
OUTPUT
A channel and angle, with the threads that justify it.
RECOMMENDED ACTION
PUBLISH
Post where the conversation already exists instead of announcing into silence.
INPUT
product context
SIGNAL
Topics accelerating faster than their usual baseline for your category.
OUTPUT
A brief with angle, format and outline, plus the sources behind it.
RECOMMENDED ACTION
PUBLISH
Write the piece while the interest curve is still rising.
INPUT
product context
SIGNAL
A live discussion where your product is genuinely relevant.
OUTPUT
A reply angle with the thread it belongs in.
RECOMMENDED ACTION
REPLY
Answer in the thread that is moving, not in a support inbox three days later.
INPUT
seed topics
SIGNAL
Queries breaking out before obvious answers rank against them.
OUTPUT
A query cluster with intent and current answer scarcity.
RECOMMENDED ACTION
PUBLISH
Publish the answer page early enough to own it — SEO, GEO and AEO at once.
INPUT
a prior asset
SIGNAL
A format still gaining traction in your category.
OUTPUT
A remix plan for an asset you already own.
RECOMMENDED ACTION
REMIX
Re-cut what already earned attention instead of starting from a blank page.
INPUT
campaign window
SIGNAL
How fresh the supporting evidence is, and how long it stays usable.
OUTPUT
A validity window with an explicit confidence note, not a promise.
RECOMMENDED ACTION
PUBLISH
Ship inside the window; the evidence behind a move expires.
INPUT
weak evidence
SIGNAL
Evidence that is stale, thin, saturated or outside what you can credibly make.
OUTPUT
What to watch, and when the next check is worth running.
RECOMMENDED ACTION
WAIT
WAIT is a real answer. No platform, no destination and no draft is manufactured for it.