The growth loop
Pull a briefing, do the work elsewhere, write back what happened. Three optional tools keep follow-up state between sessions.
Growth work is long-running: you reply to a post today, it answers on Thursday, and the agent that replied is a different session by then. The growth loop is the small amount of server-side state that lets any session pick up where the last one stopped.
┌──────────────┐ what is due today? ┌──────────────┐
│ get_briefing │ ──────────────────────▶ │ your agent │
└──────────────┘ └──────┬───────┘
▲ │ researches, drafts, acts
│ later │ (elsewhere: you or the agent post)
┌──────┴───────┐ what happened? ┌──────▼───────┐
│ track │ ◀────────────────────── │ log_action │
│ (what to │ │ (write back) │
│ follow) │ └──────────────┘
└──────────────┘| Step | Tool | Purpose |
|---|---|---|
| Pull | get_briefing | Start of a session: ranked follow-ups, experiments waiting for a decision, pipeline counts, attribution. |
| Register | track | Save opportunities, create or update experiments, make short links. Up to 20 items per call. |
| Write back | log_action | After something was done: one sentence, plus a stage, a follow-up time or an outcome if you know them. |
None of the three needs another to be called first, and none is required. A note in memory is enough when you do not need follow-ups.
A typical day
Pull
The agent calls get_briefing with the project. It sees today (ranked opportunities with a plain reason each), experiments (any with decision_needed: true), and the attribution summary.
Work
The agent searches (search_signals, creator_lookup), drafts replies, and the user or the agent posts them outside OpenNomos.
Write back
For each thing done, log_action with the post url, a one-line summary, and stage: "contacted" if that is true. New people and posts found along the way go in with track (several per call).
Decide
When an experiment's deadline passes, the next briefing puts it in experiments with decision_needed: true and a question. The agent records stop, scale, extend or keep with track.
Example: reply to a post and schedule the follow-up
{
"url": "https://www.reddit.com/r/SaaS/comments/1abc23/looking_for_a_lightweight_crm",
"action": { "kind": "comment", "summary": "Replied with a comparison table", "channel": "reddit" },
"stage": "contacted"
}The URL is unknown, so it is tracked automatically. The stage changed to contacted, so the follow-up is set to three days from now. Next session the opportunity appears in today once that time passes. See log_action defaults for the exact rules.
Where to go next
- Briefing and ranking: what
todaycontains and why items are ordered the way they are. - Memory vs opportunity: what goes where.
- log_action defaults: what happens to the stage and the follow-up time.
- Experiments: metrics, stop rules, due and decision.
- Attribution: short links, outcomes and
unknown.
Not available yet
Weekly reviews and watching for new replies on posts you replied to are not available yet. The briefing's signals list is currently always empty, and OpenNomos does not push notifications. The agent has to ask.