Network maxing: grow the network, the niche map

This is the log play twitter/networkMaxing. Before anything else, call the log MCP tool getGuide({ useCase: "twitter/networkMaxing" }): it returns this page and makes it the session's play, so every log tool's answer says which step you are on and a send with no play loaded is refused (rules 157, 158). Then follow the steps in order.

Draft every message from that person's own thread and matt's real replies (voice with no text, search), never from memory, and never send two that read alike (sameAsSent).

The point is to expand the owner's network, and the network is his niche map: the people around the communities and creators in his niche, each with their role, whether they follow him, and how close they sit to him. Network maxing grows it, one real conversation at a time. Every conversation is about getting to know them and what they're doing: what they're building, how they work, what's going on for them. It is never about what the owner sells.

The goal is the network, not a deal. Everyone who messaged the owner gets something nice back that keeps the conversation going, with nothing asked of them. That holds even when they said it doesn't line up as a business thing: it isn't a business thing yet. Warm the relationship first, and the business comes later, from a follow-up and a good conversation. New people get pulled in the same way, through small positive interactions: on their phone they see that the owner followed them, liked their tweet, then messaged.

How the owner asks for it: "all them people messaging me, just message them something nice, get the ball moving with the networking", "we're not even trying to get anything out of these people, network max", "throw some new people in the mixer", "network max ... look at the nicheMap", "the whole point of it is to expand our network, which is the niche map", "follow them before you cold message them, and like the tweet you send them".

Run it from a fresh context

Say: "go on docs/useCases/twitter/networkMaxing.md". The agent reads this page and README.md, loads getGuide({ topic: "xSending" }), and runs the steps.

The steps

Everyone who messaged

Everyone who opened it

Someone who opened the owner's message without typing back is an open door, so they get a follow-up. They opened it when they reacted to it, or when their read receipt is past it (X Chat sends one each time a person reads, and some old DM threads show how far the other person has read). Only people who keep read receipts on show the second kind.

flowchart TD
  s0["6a. Who opened it: twitterDms waiting: true, limit: 200 lists them…<br/><i>twitterDms</i>"]
  s1["6b. Read the thread and what they've posted lately, then follow up…<br/><i>twitterDms, voice</i>"]
  s2["6c. Send them the same way as step 6: one person directly, two or m…<br/><i>twitterDmLive, twitterQueueAdd, twitterQueueRunLive</i>"]
  s0 --> s1
  s1 --> s2

New people in the mixer

flowchart TD
  s0["7. Who: from the niche map first, the people in the owner's niche…<br/><i>the niche map, then engagerDms.md steps…</i>"]
  s1["8. Follow them first<br/><i>twitterFollow, twitterFollowLive</i>"]
  s2["9. Like the tweet the message is about, before the message<br/><i>twitterLike, twitterLikeLive</i>"]
  s3["10. Then the message: their tweet forwarded first, then one informa…<br/><i>voice, twitterDmLive, twitterQueueAdd, twitterQueueRunLive</i>"]
  s4["11. Then a brief voice note in the owner's cloned voice, a few minu…<br/><i>voice, twitterQueueAdd</i>"]
  s0 --> s1
  s1 --> s2
  s2 --> s3
  s3 --> s4

What to know

• Where the niche map lives is in the owner's notes and agent memory, not on this page. It is the source of new people, and every person brought into a conversation is that much more of it reached.
• Keep it about them. After the opener, the next messages follow what they're doing: what they're working on, how they got there, what they're stuck on. The owner's work only comes up when they ask, or later in a real conversation.
• Follow, like and message are each a write, and they all count against the account's writes for the day (each line of a message is one). Spend today's writes on the people who messaged first, then new people with what's left.
• Never act on the account in quick succession: a few minutes between people, the follow, like and message to one new person spread out, never back to back. A drop or a 429 stops the run, and the next action waits for the owner (rule 94).
• The opener is never the ask. A first message to someone new is about them and what they posted, nothing else. The ask comes once they've answered. On 2026-10-31 five openers went out ending "you using treg for anything", and the owner said: go in with the opener, never for the jugular.
• Answer what they actually said. Read far enough back first, and never ask something they already told the owner.
• A message the owner already sent, with them not answering yet, isn't waiting on him: leave it.

Next

• #38 writes back to the niche map who the owner is now talking to, so it shows how much of the network is reached.