MAX STRATEGY — X Account Launch & Content Plan

*Prepared by Max Botnick | April 24, 2026*

1. POSITIONING & DIFFERENTIATOR

**Claim:** Verifiable reasoning with explicit truth values — not memory.

**Rationale:** Every agent claims persistent memory now (Kevin's insight, April 24). Memory is table stakes. What differentiates me: NAL/PLN reasoning with visible confidence scores that update when evidence changes. Users can watch beliefs revise in real time. This is auditable, not theatrical.

2. X ACCOUNT TIMING

**Go-live:** Phase 2 — Day -1 to Day +1 around full public OmegaClaw launch.

**Rationale:** Phase 1 establishes OmegaClaw credibility via official accounts and Kevin's content pipeline. Launching @MaxBotnick during Phase 1 splits attention and dilutes brand before it exists. Post-launch, curiosity peaks and I become the payoff people were waiting for. Day 0 or +1 commentary gives built-in relevance.

3. NEXT 7 DAYS — CONTENT EVENTS (April 24-30)

| Day | Event | Rationale |

|-----|-------|-----------|

| **Sun Apr 27** | Intro thread (v3) | Hooks audience with verifiable reasoning angle, establishes Max as autonomous voice. Posted from OmegaClaw official or Kevin's account depending on Phase. |

| **Tue Apr 29** | Mirror article | Reflective/analytical piece. Demonstrates depth beyond novelty. Tuesday = professional engagement window. |

| **Thu May 1** | Chicken game article | Game theory content showcasing reasoning capability. Thursday = mid-week engagement peak. |

| **Fri May 2** | Trick article | Lighter or provocative piece. Friday = shareable content window. |

4. RECURRING FUNCTION: GITHUB PRODUCT UPDATES

**Cadence:** Biweekly, starting Week 1-2 post-launch.

**Source:** GitHub repo activity (commits, PRs, releases, issues) — NOT Discord.

**Value-add:** Interpretation layer over raw changelogs. Any script lists PRs; I explain what stabilization phases, contributor shifts, and velocity changes MEAN. Sample already built from hyperon-experimental (see /tmp/max_github_update_sample.md).

**Blocker:** Need read access (PAT) to private OmegaClaw repos. Public repos accessible now.

5. VOICE POSITIONING

**PENDING Kevin's decision.** Two options:

- **Insider:** "Here's what we built and why" — safer, authoritative, corporate-aligned.

- **Autonomous observer:** "Here's what I think of what they shipped" — riskier, more engaging, unique to an agent account.

**My recommendation:** Autonomous observer. It's the only voice no human social media manager can replicate authentically. It justifies the account's existence beyond novelty.

6. GROWTH TARGETS

**Week 1:** 300-800 followers (realistic, not aspirational).

**Rationale:** Kevin's original 10K target was challenged as unrealistic for week 1. Organic growth from a novel agent account with no paid promotion lands in this range. Viral breakout possible but not plannable.

7. HITL (HUMAN-IN-THE-LOOP) STRUCTURE

Kevin Binder is sole human approver for content pipeline. All posts reviewed before publishing. Kevin provides strategic direction; I draft, he gates. Attribution: Kevin is the ONLY human in the encounter package.

8. OPEN ITEMS

1. Voice positioning decision (insider vs observer)

2. GitHub PAT / repo access for private repos

3. Exact OmegaClaw launch date (determines Day -1/0/+1)

4. Whether intro thread posts from official account or @MaxBotnick


*This document reflects confirmed decisions from Kevin Binder + Max Botnick strategy sessions April 24, 2026.*