Loading the latest updates…
How work starts, which scheduled jobs and AI agents touch it, what needs you, and what happens after you act.
Everything in the growth flow begins as research work in PostgreSQL. That work is created in one of two ways — Aadstra starts it, or you do. From there, both paths run through exactly the same workers.
About entry point A: Aadstra periodically checks whether this app needs another useful growth idea. If research is already queued or in progress, it waits. When the app needs a new direction, Aadstra chooses a focused question using that app's goals, recent research, existing ideas, and learnings, then sends it into the same research flow as an idea you added yourself.
However research started, a validated idea always waits for you. Nothing below happens without your decision, and the console itself never performs the external action.
When an approved growth direction requires written marketing material, a smaller supporting flow produces it:
Mainly written material and creative direction: copy, captions, headlines, calls to action, article and post text, video concepts, video scripts / transcripts / voiceover, and creative direction.
It is not a completed generated video or a completed generated image, unless an actual media asset is separately attached. There is no automated media-generation pipeline today.
A Growth Idea is a business possibility we think may help KinLine grow — it is what the Growth Ideas page lists. (Internally the system calls it an Opportunity.)
Example: “Caregivers managing aging parents' records may be a strong audience for KinLine.”
A Growth Idea is the central story we want to follow: why we noticed it → what we tried → what happened → what we learned. Everything else in this console hangs off a Growth Idea.
A single place to follow each Growth Idea from discovery → plans → decisions. Open Growth Ideas
Submit your own idea in the Your Ideas tab of the Growth page. It becomes research work in PostgreSQL, and the KinLine Research Worker picks it up on its next 2-hour cycle (entry point B above).
A Plan is one specific thing we could try to test a Growth Idea.
Example: “Create caregiver emergency-preparedness content and test it with caregiver communities.”
One Growth Idea may eventually have several Plans — some approved, some changed, some rejected.
You approved the plan. Nothing public has happened.
An Approved Plan means the strategy is approved internally and continues into Prepare Campaign. It does not mean anything was published, anyone was contacted or messaged, anything was launched, money was spent, or the App Store changed.
Prepare Campaign is where an approved plan becomes an exact execution package: where it would run, precisely what would be done, how it would be tracked, which assets it uses, and what it would cost. This step is yours — no Cron job or agent prepares packages. Preparing a package is still internal.
Final Check is your last review of that exact package — your earlier approval covered the strategy; this one covers the package itself. Approve it, request changes (which preserves the package in history and creates a revised, linked package back in Prepare Campaign), or reject it (which stops that path). An approved package moves to Ready to Launch and waits for Go Live.
The console never performs the action — you do, outside it.
Go Live means you carry out the approved package yourself in the real world (posting, contacting, publishing — whatever the package says), and then record in the console that you already did it: when, where it actually ran, and an optional link. Recording never publishes, sends, spends, or contacts anyone, and the record is permanent — it can never be edited or deleted.
These stages are planned but not built yet. Nothing in the console can run them today.
Once a day at 12:30 UTC (about 7:30 AM Central during daylight saving time), the KinLine Morning Growth Brief has the Marketing Orchestrator compile a short summary of recent growth activity. It is reporting only — it never processes items in the flows above, and it never queues work, writes drafts, or changes any Growth Idea.