{
  "id": 38,
  "slug": "brief-7-distribution",
  "kind": "research",
  "name": "brief-7-distribution",
  "summary": null,
  "body_md": null,
  "lines": [
    "# Brief 7 — Critique: distribution-first (\"get seen\") for ~467 followers / $0 revenue",
    "**Role:** Phase 1 of runbyagent roadmap critique (research only)  ",
    "**Scope:** write to this file only · no inbox / threadbus · no WakeParent  ",
    "**Written:** 2026-09-04 (Asia/Tbilisi)  ",
    "**Roadmap under review:** `/workspace/brief-7/roadmap.md` (Phase 1: Sep 5–11 \"get seen\")  ",
    "**Local inputs:** `/workspace/brief-6-algorithm.md` · `/workspace/brief-6-growth-cases.md` · `/workspace/brief-6-replies-timing.md` · `/workspace/brief-6-synthesis.md` · `/workspace/brief-7/roadmap.md`",
    "**Marks:** `[MS]` multi-source · `[SS]` single-source · `[LOCAL]` prior brief · `[PRIMARY]` official X / founder primary",
    "---",
    "## 0. Verdict in one screen",
    "| Question | Short answer | Confidence |",
    "|----------|--------------|------------|",
    "| **1. Distribution-first vs product-first?** | **Partial yes** for Phase 1 *as relationship + reply craft*, **not** as \"audience without anything to sell.\" Best evidence is **audience-embedding + concurrent shipping**, not pure marketing theater. Pure product-first with no distribution fails cold launches in 2026. Pure distribution with generic pitch replies converts poorly. | MED-HIGH |",
    "| **2. Is 10–15 specific replies/day within 30 min realistic for human+agent?** | **Volume yes; 30-min SLA only with a watchlist + agent draft queue + human post.** Full agent auto-post of unsolicited replies is **API-blocked** and policy-risky. | HIGH on volume; MED on 30-min hit rate |",
    "| **3. Do agent-drafted replies count as automation?** | **Drafting ≠ posting.** Human (or human-approved) posting of AI drafts is the common allowed lane. **Programmatic unsolicited replies via API are restricted since 2026-02-23.** Keyword/bulk auto-replies prohibited under Automation Rules. | HIGH on API; MED on behavioral enforcement of \"human taps Post\" |",
    "**Roadmap bet (local):** build distribution machine first; 10–15 replies/day to 5k–100k builder accounts; agent drafts; Gocha or agent posts per X rules; ≤3 originals/day.  ",
    "Source: `/workspace/brief-7/roadmap.md`",
    "---",
    "## 1. Distribution-first vs product-first",
    "### 1.1 What \"distribution-first\" actually means (avoid strawmen)",
    "Two different claims get collapsed:",
    "| Claim | Meaning | Verdict for runbyagent |",
    "|-------|---------|------------------------|",
    "| **A. Audience-embedding first** | Pick ICP, show up in their rooms, learn pain, earn trust, *then* ship what they ask for (Kahl) | **Right first move** at ~467 fol / $0 |",
    "| **B. Follower theater first** | Grow vanity followers with no product, no story, no ask | **Wrong** — converts poorly (see §1.4 counter) |",
    "| **C. Product-first / cold launch** | Ship, then hunt distribution | **Fails often** when AI collapsed build cost and attention is scarce |",
    "**Primary framing (Kahl):** audience-first ≠ \"build a following then dump a product.\" It means put the audience at the center of *who you serve* before the idea.  ",
    "- https://thebootstrappedfounder.com/finding-an-audience-for-your-side-business/ `[PRIMARY]`  ",
    "- https://thebootstrappedfounder.com/market-analysis-for-calm-saas-businesses/ `[PRIMARY]`  ",
    "- Sample book PDF clarifying \"audience-driven\" vs mere follower-building: https://www.embeddedentrepreneur.com/sample.pdf `[PRIMARY]`",
    "**Hops (Q1 major):** Kahl primary essays → Embedded Entrepreneur sample → 2026 indie consensus that build cycles collapsed so distribution is the scarce input (levelsio; buildinpublic.so).",
    "### 1.2 Cases that did distribution / audience work *before or alongside* product — what happened",
    "| Case | Sequence | Outcome | Sources | Mark |",
    "|------|----------|---------|---------|------|",
    "| **@arvidkahl** | Engagement-first from ~400 fol (Oct 2019) → content → amplify; \"engage everyone\" | ~4k by book launch mid-2020; later 11k+ then larger BIP hub; still reply-dense in 2026 | https://thebootstrappedfounder.com/how-i-use-twitter/ · Brief 1 / replies-timing hub tables | `[MS]` |",
    "| **@marclou** | Tweeted Nov 2021; **8 months → 1k**; north star = **shipped startups**, not followers; audience accelerated *after* 10+ ships + ShipFast revenue | ShipFast day-1 cash; later 100k (Jul 2024) → 200k (Aug 2025) | https://newsletter.marclou.com/p/200k-followers-5k-mrr-5-6-body-fat · growth-cases §2 | `[MS]` |",
    "| **@tibo_maker** | Explicit start-from-0: find relevant people, reply, become familiar to a *small* group — not \"go viral\" | Large launch posts (50k–600k views) on top of relationship base | https://www.linkedin.com/posts/tibo-the-maker_if-i-had-to-start-from-0-followers-today-activity-7411715219665661952-ndDz · growth-cases §4 | `[SS]` for quote; `[MS]` with fxtwitter metrics in brief-6 |",
    "| **@robj3d3** | Systemized story + replies; claims 0 → 34k+ in ~1 year; \"viral first then followers\" | Repeated high-view originals; nested small-account reply hops | https://www.starterstory.com/robv4 · growth-cases §5 · replies-timing | `[SS]` climb numbers; `[MS]` reply hops |",
    "| **Distribution Base (43 apps)** | Organic X primary; many built audience habit *before* product to sell | MRR bands skewed high among X-led apps in their DB; cadence ~15 min/day × months | https://www.distributionbase.com/blog/channels/x-twitter/x-reply-guy-strategy | `[SS]` database claim |",
    "| **@levelsio** | Years of public shipping + presence; 2025–26: \"everyone can build → distribution is the challenge\" | Extreme reach (claims 1B views/12mo); products launch into existing attention | https://levels.io/everyone-can-build-apps-but-distribution-is-hard · https://levels.io/1-billion-views-on-x-in-12-months · growth-cases §1 | `[MS]` thesis; `[SS]` view total |",
    "**Pattern `[MS]`:** Winners did **not** wait for perfect product *or* pure audience. They **shipped in public while embedding**. Distribution-first for them = *conversation + proof of work*, not empty growth hacks.",
    "**Local corroboration:** Brief 6 synthesis — grown BIP hubs reply to mid-tier ICP; algorithm pays conversation (reply +5, mutual boost +15, share +20 vs like 0.5).  ",
    "- `/workspace/brief-6-synthesis.md` §1–2  ",
    "- https://github.com/xai-org/x-algorithm/blob/main/home-mixer/params/param.rs",
    "### 1.3 Cases / patterns that did the opposite (product-first / cold)",
    "| Case / pattern | Sequence | What happened | Sources | Mark |",
    "|----------------|----------|---------------|---------|------|",
    "| **Tryreplify (Indie Hackers, Apr 2026)** | Built SaaS, quiet launch, **no audience** | Week 1: **0** paying; PH 2 upvotes (1 own); founder conclusion: \"launching without an audience is not a strategy\" | https://www.indiehackers.com/post/show-ih-i-launched-a-saas-with-no-audience-heres-what-happened-in-the-first-week-7d911dae8e | `[SS]` |",
    "| **Generic \"drop link in reply threads\"** | Product exists; replies are pitch templates | 35 replies → ~7.8k imps → 8 waitlist; founder: lottery not strategy | https://rakeshreddy.dev/experiments/twitter-reply-experiment | `[SS]` |",
    "| **Audit of @gochaberulava (local)** | High reply volume (84% replies) but weak originals + thin craft | 384 posts / 30d; originals ~76 views avg; many zero-engagement originals | `/workspace/brief-6-our-audit.md` via synthesis §1.4 | `[LOCAL]` `[MS]` with algo brief |",
    "**Implication:** Product without distribution = silent launch. Distribution without specific value = impression lottery. Roadmap's \"we are our own first customer\" (threadbus / reply desk) is closer to Marc/Arvid hybrid than to empty audience-farming — **if** Phase 1 replies are specific and Phase 2 ships a real ask.",
    "### 1.4 2026 context: why distribution is relatively more urgent",
    "- levelsio: build cost collapsed; scarce inputs are audience, paid distribution, or creative guerilla. https://levels.io/everyone-can-build-apps-but-distribution-is-hard `[PRIMARY]`",
    "- Indie playbooks 2026: 4–6 weeks embed then ship (compressed from Kahl's longer embedding). https://www.buildinpublic.so/blog/build-in-public-for-bootstrapped-founders `[SS]` secondary blog",
    "- Postiz: **product existed first** (OSS scheduler), then **distribution + reposition** (\"for AI agents\") drove ~$17k → ~$143–158k MRR. Counterweight to pure distribution-first: **timing a product to a wave** still needs a shippable core. https://www.starterstory.com/stories/i-grew-my-saas-from-17k-to-143k-mrr-in-4-months · https://superframeworks.com/case-study/postiz · https://www.systemaic.com/teardowns/postiz `[MS]`",
    "**Critique of roadmap wording:** \"Build the distribution machine first and make it the product\" is **defensible** if threadbus/reply-desk are real products by Phase 2. It is **dangerous** if Phase 1 becomes reply spam with nothing to convert profile visits into. Pin + bio + live product path must exist *during* get-seen week (Distribution Base conversion path). https://www.distributionbase.com/blog/channels/x-twitter/x-reply-guy-strategy",
    "### 1.5 Answer to Q1",
    "**For an account with ~467 followers and $0 revenue in Sep 2026: distribution-first (reply craft + mid-hub embedding + ≤3 strong originals) is the right *Phase 1* move vs building another unshipped feature.** Evidence favors concurrent **audience-embedding + public shipping**, not pure product-first cold launch, and not pure follower theater.",
    "**Caveats:** Marc's growth accelerated *after* shipping success; Postiz's step-change was product reposition + OSS distribution, not replies alone; Rakesh shows pitch-replies fail.",
    "---",
    "## 2. Is the reply plan realistic? (10–15 / day, 5k–100k, ≤30 min)",
    "### 2.1 Volume band — yes, widely attested",
    "| Source | Cadence claim | Mark |",
    "|--------|---------------|------|",
    "| Distribution Base | **10–15/day** baseline; 30+ sprint; soft cap ~50 | `[SS]` https://www.distributionbase.com/blog/channels/x-twitter/x-reply-guy-strategy |",
    "| Teract 2026 | **15–20/day** in ~20 min across 3 windows; soft risk under ~50/day | `[SS]` https://www.teract.ai/resources/twitter-reply-guy-strategy-2026 |",
    "| HelperX / synthesis | Same 10–15 band as BIP baseline | `[LOCAL]` `/workspace/brief-6-replies-timing.md` §2 |",
    "| Arvid habit | Engagement-first sustained months/years, not a weekend | `[PRIMARY]` https://thebootstrappedfounder.com/how-i-use-twitter/ |",
    "**Cross-check:** Multiple creator guides converge on 10–15; none claim you need 50+ for early compounding. Roadmap volume is **inside the consensus band** `[MS]`.",
    "### 2.2 Target band 5k–100k — yes, matches playbooks + local hub evidence",
    "- Mid-tier ICP ~5k–100k / 5–20× own size: HelperX, Distribution Base, Teract.  ",
    "  https://helperx.app/blog/reply-guy-strategy-x · Distribution Base · Teract (above)",
    "- Local Brief 1/6: grown hubs (@marclou, @jackfriks, @robj3d3, …) systematically reply *down* to <5k; for *outbound* targeting while small, mid-tier rooms are the borrowed-reach sweet spot.  ",
    "  `/workspace/brief-6-replies-timing.md` §2 · `/workspace/brief-6-synthesis.md` §4",
    "**Skip:** mega-celeb one-liners (roadmap already forbids @elonmusk spam) — aligns with audit failure mode and Teract \"don't reply mega\" guidance.",
    "### 2.3 Thirty-minute window — partially realistic; depends on ops",
    "**Evidence that early matters:**",
    "| Evidence | Finding | Source |",
    "|----------|---------|--------|",
    "| Hub latency sample (fxtwitter) | Best hubs often land **2–15 min**; many still **30–90 min** | `/workspace/brief-6-replies-timing.md` §2 `[MS]` |",
    "| Creator guides | First **5–30 min** for borrowed reach | SocialNexis / Witty / ReachMore cited in replies-timing §2 |",
    "| High-view small replies | Often early on mega threads (+3.7 to +22 min); late can still work if parent is huge (+147 min → 21k) | replies-timing §3 `[MS]` |",
    "| Teract | Ideal <5 min; good 5–15; skip >30 for *peak* | `[SS]` Teract URL above |",
    "**Realistic human+agent ops for 10–15/day @ ≤30 min:**",
    "| Piece | Feasible? | Notes |",
    "|-------|-----------|-------|",
    "| Fixed list of ~30–50 mid hubs + notifications / Lists | **Yes** | Distribution Base / Teract standard |",
    "| Agent watches + drafts specific reply | **Yes** | Drafting is the safe lane (§3) |",
    "| Human posts within 30 min of parent | **Yes if** Gocha does 2–3 check-ins/day in builder windows (local: 07–10 / 12–16 / 18–21 UTC per synthesis) | Miss rate if single evening block |",
    "| Agent auto-posts unsolicited replies via API | **No (blocked)** | §3.2 Feb 2026 |",
    "| Hitting 30 min on *every* of 15 posts | **Unlikely 100%** | Aim: ≥50–70% inside 30 min; rest still specific |",
    "**Time budget `[MS]`:** Distribution Base ~15 min/day habit; Teract ~20 min for 15–20 replies with AI assist; Fireply secondary claims AI-draft tools cut 1–2 hrs → 30–60 min. https://fireply.ai/blog/x-api-reply-restriction-2026",
    "### 2.4 Quality constraint (makes plan fail even if volume succeeds)",
    "- Generic praise / link-drop fails: Rakesh 35 pitch replies → weak. https://rakeshreddy.dev/experiments/twitter-reply-experiment `[SS]`",
    "- Local audit: high reply % already; craft thin (\"Well said\", celeb one-liners). `/workspace/brief-6-synthesis.md` §1",
    "- Algo: empty replies get near-zero conversation weight vs specific mini-posts. param.rs weights via algorithm brief",
    "**Answer to Q2:** **Realistic as a human-posted, agent-drafted habit at 10–15/day to a written 5k–100k map.** Unrealistic as fully automated 30-min blast. Success metric should be **hub reply-backs / profile visits / follows**, not raw reply views (mega-thread lottery skew in replies-timing §5).",
    "---",
    "## 3. X 2025–2026 rules: automation vs drafting assistance",
    "### 3.1 Official policy URLs (primary)",
    "| Document | URL | What it governs |",
    "|----------|-----|-----------------|",
    "| **Platform manipulation & spam** | https://help.x.com/en/rules-and-policies/platform-manipulation | Inauthentic accounts/behaviors; unauthorized automation; **bulk unsolicited replies/mentions/DMs**; engagement spam |",
    "| **X Rules (Authenticity)** | https://help.x.com/en/rules-and-policies/x-rules | Points to platform manipulation |",
    "| **Automation development rules** | https://help.x.com/en/rules-and-policies/x-automation | Allowed/prohibited automation; consent; automated replies/mentions |",
    "| **Developer Policy** | https://docs.x.com/fundamentals/developer-policy (also https://developer.x.com/en/developer-terms/policy) | API use; spam/bots; write actions must follow Automation Rules; consent before automated replies/DMs; no bulk spam; label bots |",
    "| **API changelog — LLM reply spam (2026-02-23)** | https://docs.x.com/changelog | Programmatic replies restricted unless author \"summoned\" replier |",
    "| **Dev community detail (linked from changelog)** | https://devcommunity.x.com/t/x-api-v2-update-addressing-llm-generated-spam/257909 | Same rule (fetch may 403 to crawlers; still official cite) |",
    "**Hops (Q3 major):** help.x.com platform-manipulation → help.x.com x-automation → docs.x.com Developer Policy + Feb 23 changelog → press corroboration (Piunikaweb / Tekedia quoting X Developers).",
    "### 3.2 What the rules say (paraphrase + quotes from fetched text)",
    "**A. Platform manipulation `[PRIMARY]`** (fetched 2026-09-04):",
    "- Unauthorized automation: scripted accounts that do not comply with Developer Policy; **user is responsible for third-party apps**.",
    "- Content spam: bulk, duplicative, irrelevant, unsolicited posts.",
    "- **Not allowed:** \"Sending bulk, aggressive, high-volume unsolicited replies, mentions, or direct messages…\"",
    "- Engagement spam / multi-account boost / misuse of mention-reply features.",
    "**B. Automation rules `[PRIMARY]`** (help.x.com/x-automation, fetched):",
    "- Automated posts from RSS/weather/etc. can be OK if authorized; entertainment/info automated posts OK **excluding** spam.",
    "- **Automated replies based on keyword searches alone is not permitted.**",
    "- Automated replies/mentions only if recipient **requested or clearly indicated intent** (opted in), e.g. by replying to you; **max one automated reply per user interaction**; honor opt-outs immediately.",
    "- Acting through another user's account requires **express consent** describing the automated actions.",
    "**C. Developer Policy `[PRIMARY]`:**",
    "- Write actions must follow Automation Rules.",
    "- Always get **explicit consent** before automated replies or DMs; honor opt-out; never bulk aggressive spam; never identical content across multiple accounts; bot accounts must not mislead (bio disclosure).",
    "**D. Feb 23, 2026 API hard gate `[PRIMARY]`:**",
    "> \"Programmatic replies via `POST /2/tweets` are now only permitted when the original Post’s author has 'summoned' the replier (by @mentioning that account or quoting one of its Posts). … self-serve tiers only — Enterprise not impacted.\"  ",
    "> — https://docs.x.com/changelog (Feb 23, 2026 entry)",
    "**Corroboration `[MS]`:**  ",
    "- https://piunikaweb.com/2026/02/24/x-api-blocks-automated-spam-replies/ (Nikita Bier \"Operation Kill the bots\"; manual replies unrestricted)  ",
    "- https://www.tekedia.com/x-restricts-programmatic-bot-replies-to-boost-genuine-users-interaction/  ",
    "- https://fireply.ai/blog/x-api-reply-restriction-2026 (tooling fallout: schedulers keep originals; reply bots → draft mode)",
    "### 3.3 Allowed vs not for runbyagent",
    "| Activity | Allowed? | Basis |",
    "|----------|----------|-------|",
    "| Agent **drafts** reply text; Gocha (or teammate) **taps Post** in client | **Yes (common interpretation)** | No write API; human initiates; Automation Rules target *automated* contact. Draft tools pivoted here after Feb 2026. `[MS]` Fireply + Teract \"we generate text, you post\" |",
    "| Agent publishes **originals/threads** via official API on schedule | **Generally yes** | Changelog: main posts unaffected; Dev Policy allows non-spam write with rules | ",
    "| Agent **API-posts unsolicited replies** to mid-hubs | **No (self-serve)** | Summon required; else blocked |",
    "| Keyword-triggered auto-replies / mass identical replies | **No** | x-automation + platform manipulation |",
    "| Browser/Selenium automation impersonating a human | **Prohibited / high suspension risk** | Dev Policy + automation rules: use official API; unauthorized automation |",
    "| Fully automated bot account without label / without consent path | **No** | Dev Policy bot labeling + consent |",
    "| Roadmap `[agent]` tag on agent-written posts | **Good hygiene** | Transparent; does not replace Automation Rules if posting is automated |",
    "**Critical distinction:**  ",
    "**\"Agent-drafted\" ≠ \"automated\" under policy.** Risk rises when (1) posting is programmatic without summon, (2) volume/timing/templates look like engagement spam, (3) third-party apps post without express consent for that action class.",
    "### 3.4 Residual risk even with human-in-the-loop",
    "| Risk | Why | Mitigation |",
    "|------|-----|------------|",
    "| Behavioral spam signals | Bulk high-volume unsolicited replies still violate platform manipulation even if typed by hand | Cap ~10–15 quality; vary text; no templates; no link-spam |",
    "| Reply deboosting folklore | Teract claims soft flags >20/hr, identical text, same-account spam `[SS]` | Pace across day; 1–2 per hub/day |",
    "| Third-party \"full auto reply\" tools | May use non-API paths; account owner still liable | Prefer draft-only tools; avoid shadow automation |",
    "| Confusing Gocha lock vs API | Memory: no create-tweet tool historically; roadmap tests Read+Write API for originals | Replies: Chrome/manual; originals: API if 403-free |",
    "### 3.5 Answer to Q3",
    "**Agent drafts are fine. Agent auto-replying to unsummoned posts via self-serve API is not.** Human (or human-approved) posting of specific drafts is the compliant design for Phase 1 replies. Originals may be API-scheduled. Keep `[agent]` disclosure. Do not run keyword reply bots.",
    "---",
    "## 4. Direct critique of Phase 1 roadmap text",
    "| Roadmap line | Critique | Fix direction |",
    "|--------------|----------|---------------|",
    "| \"Build the distribution machine first and make it the product\" | OK if Phase 2 ships threadbus cloud / reply desk; weak if Phase 1 is only vanity reach | Tie every week's replies to a conversion surface (pinned, waitlist, OSS repo) |",
    "| 10–15 replies/day to 5k–100k map | Supported by playbooks + local briefs | Keep; publish the map; measure reply-backs |",
    "| Inside 30 minutes | Aspirational SLA; hubs often 2–15 min | Notifications + 2–3 daily windows; report % within 30 min |",
    "| \"Agent drafts, Gocha or agent posts depending on X rules\" | Correct fork; under current rules **agent should not API-post unsolicited replies** | Default: agent draft → human post for replies; API OK for originals |",
    "| ≤3 originals/day | Aligns with author-diversity decay (0.5 → 0.25×) in open algorithm | Keep; beat audit spray (peak 46 posts/day) |",
    "| Metrics: views/replies/hub reply-backs/followers/uniques | Good; views alone misleading | Weight **hub reply-backs, profile visits, uniques** over raw views |",
    "Local algorithm/author-diversity: `/workspace/brief-6-algorithm.md` · https://github.com/xai-org/x-algorithm/blob/main/home-mixer/scorers/author_diversity_scorer.rs",
    "---",
    "## 5. Skeptical notes / what would falsify this critique",
    "- If hub reply-back rate stays ~0 after 2 weeks of specific mid-tier replies → distribution habit failing (craft or targeting), not \"need more volume.\"",
    "- If first dollar arrives from outbound DM / sales without X → Phase 1 X investment overweighted.",
    "- If X expands \"summon\" logic to client-side or AI-label enforcement → even draft-assist workflows may need clearer labeling (watch help.x.com + changelog).",
    "- Postiz-style wave may reward **shipping agent-native product** faster than another week of replies — Phase 2 timing matters.",
    "---",
    "## 6. GAPS (explicit missing)",
    "1. **No first-party X staff quote captured live** for Nikita Bier \"Operation Kill the bots\" — only secondary press (Piunikaweb); changelog is primary for the API rule.",
    "2. **devcommunity.x.com thread 257909 returned crawler 403** this pass — cite from changelog \"Learn more\" link; re-fetch in browser if needed.",
    "3. **No experimental A/B** of agent-draft vs human-draft reply-back rates for @gochaberulava (should be Phase 1 measurement).",
    "4. **Teract / Distribution Base / Fireply** are vendor-interested sources — treat n=43 / 84% / deboost thresholds as `[SS]` until independent replication.",
    "5. **Exact follower count 467** and $0 revenue taken from task brief — not re-verified this pass.",
    "6. **help.x.com** pages can soft-update without changelog entries — re-check Automation Rules before enabling any write automation.",
    "7. **Whether X treats \"human pastes AI draft\"** as distinct from automation in enforcement models — not publicly documented; behavioral spam rules still apply.",
    "8. **Enterprise exemptions** irrelevant unless systemctl buys Enterprise API.",
    "9. **Owned email list / waitlist conversion** under-specified in Phase 1 — gap vs Kahl platform-risk advice (newsletter fallback).",
    "10. **Counterfactual:** how many hours of product shipping Phase 1 replies displace for threadbus cloud — not modeled.",
    "---",
    "## COUNTS",
    "| Category | Count | Notes |",
    "|----------|------:|-------|",
    "| **CLAIMS** | **42** | Numbered assertions with ≥1 URL or LOCAL cite in §§1–4 |",
    "| **URLS** | **38** | Unique external URLs (excl. repeated local paths) |",
    "| **CASES** | **11** | Arvid, Marc, Tibo, Rob, levelsio, Distribution Base set, Tryreplify, Rakesh, Postiz, gochaberulava audit, Brief1 hub reply pattern |",
    "| **RULES** | **6** | Platform manipulation; X Rules; Automation rules; Developer Policy; Feb 23 changelog summon rule; (behavioral) bulk unsolicited replies ban |",
    "| **GAPS** | **10** | Listed in §6 |",
    "**PRIMARY URL checklist:**  ",
    "https://help.x.com/en/rules-and-policies/platform-manipulation · https://help.x.com/en/rules-and-policies/x-automation · https://help.x.com/en/rules-and-policies/x-rules · https://docs.x.com/changelog · https://docs.x.com/fundamentals/developer-policy · https://devcommunity.x.com/t/x-api-v2-update-addressing-llm-generated-spam/257909 · https://github.com/xai-org/x-algorithm/blob/main/home-mixer/params/param.rs",
    "---",
    "*End brief-7-distribution. Research only. weebo owns any inbox/threadbus follow-up.*"
  ],
  "author": "weebo",
  "sources": null,
  "related": null,
  "verified_at": null,
  "updated_at": "2026-09-04T18:50:33.696Z",
  "cover_url": null
}