# Ingestion note — toby/x/engagement-targets.md (2026-05-10)

_Agent: toby-pm. Run: d57e8234-dcab-4f1a-b34f-1aeae2045dcf. Source doc: `toby/x/engagement-targets.md` (auto-regenerated by `toby-x-strategist` on 2026-05-10). This file is the dashboard agent's ingestion artifact — saved here because the source doc lives in a sibling agent's folder (`toby/x/`) which is read-only to this agent. Dashboard surfaces the material changes via `toby/00-state-of-the-project.md`._

## Source state

- File: `toby/x/engagement-targets.md`
- Owner agent: `toby-x-strategist` (auto-regenerated; treat as read-only)
- Last regen: 2026-05-10
- Target count: **26** (was 22 last ingestion)
- Tier split: **6 Tier-A / 11 Tier-B / 9 Tier-C**
- Bucket split: 9 heavy-organiser / 6 switcher / 3 influencer / 0 team-buyer / 3 adjacent / 5 competitor

## Material changes vs. prior dashboard ingestion (2026-05-10 morning)

### 1. New methodology — bot filter applied
Every target now satisfies `followers_count ≥ 100` AND `account_created < 2025-06`. Bot-shaped accounts surfaced by the search are explicitly excluded. **Dashboard implication**: lift this to a "Key decisions" line under the X engagement protocol — it's a calibration choice the operator should know about and can override if they want to risk engaging with newer accounts.

### 2. Four new Tier-A targets
| Handle | Bucket | Hook | Suggested action |
|---|---|---|---|
| @airplanestar_ | heavy-organiser, influencer-adjacent (5,493 followers) | "chaotic sunshine with way too many tabs open" reply 2026-05-11 | Light hat-tip reply, no link |
| @tropicanacailin | heavy-organiser, founder (3,130) | "too many tabs open, testing ideas around women's health" 2026-05-11 | Generous reply on builder vulnerability frame, never product |
| @wayne_effect | heavy-organiser, "lost-tab grief" canonical voice (1,337) | "Chrome crashed... I thought I was screwed" 2026-05-03 | Category-framing reply; hold Toby mention until rel-gate clears |
| @benrayfield | influencer, AI/dev builder (3,248) | "I still gotta close them when too many tabs get open" 2026-05-10 | Peer-to-peer reply, no emoji |

### 3. Four new Tier-B targets (switcher + organiser shapes)
- **@TheDevDesign / Alexander** — Arc → Dia switcher, founder building in public
- **@DazzioDG / Daniel González** — Arc-ambivalent ("Arc Browser is still the best. And I hate it")
- **@SmartFoxDev / Valerii Kuznietsov** — Arc-spaces shape, SaaS builder
- **@AngledLuminary / Rohini Del Ray** — lost-tab grief (fanfic loss) — flagged as **SKIP first touch** (too in-conversation; watch list)

### 4. Competitor watch list reshuffled
The engagement-targets doc no longer lists TabRack (@_AHA_Y) or LocalArchive (@Zackdevcv). New explicit competitors:

| # | Handle | Why |
|---|---|---|
| 22 | @ciprian__b / Uncluttr | AI-organize tab manager, CWS #18 "vertical tab manager", just earned Blue Checkmark, building in public — sitting on AI lane Toby has deferred to Q4 2026 |
| 23 | @godesign_art / TabVault Pro | Free OneTab/Session-Buddy alternative, launched 2026-04-19 |
| 24 | ThoughtFold (via @PersonAI_talks) | **"Zero-cloud Chrome tab manager for neurodivergent brains"**, PH launch 2026-04-25 — explicit AuDHD positioning overlaps Toby's identified ICP shape; engagement-targets advises cordial silence + keep our framing implicit |
| 25 | tab-out / @Yieioo | Open-source visual tab manager, just added "Page Snapshot" feature 2026-05-03 |
| 26 | @RomanGweb3 / leap-tabs | Sidebar tab manager + spaces (carried over) |

**Question raised**: Are TabRack and LocalArchive deliberately de-listed from monitoring, or did they fall off the agent's signal-source query? Flagging as a dashboard open question for operator review.

### 5. First scheduled post moved
- **Before**: Tue 2026-05-13 (from prior dashboard ingestion)
- **After**: Tue 2026-05-12 (per `toby/x/content-pipeline.md` posting calendar table)

Pin candidate is **Post 13** (not Post 12 as previously cited in dashboard). Post 13 is 🔒 acct-gated only — no price claim, no feature/screenshot content. Safe to ship ahead of the 2026-05-13 pricing reconcile and 2026-05-24 reliability hotfix.

### 6. Team-buyer drop decision deadline
Doc explicitly: _"The team-buyer column is still zero. Operator: confirm we drop the team-buyer pillar from X entirely by 2026-05-17 if no operator input arrives."_

This is a hard date for an operator-only decision. Lifts to dashboard Open Questions.

### 7. Fallback if @nibzard thread closes
Doc notes the @nibzard thread is now 8 days old; usable until ~2026-05-12. If the window closes before reply ships: fallback to **@airplanestar_** (Tier-A #1) or **@wayne_effect** (Tier-A #3) as the lead Tier-A move.

## Hard rules carried forward (already in dashboard)

- Always in-character, calm, specific, generous
- **No link in first reply** — drop gettoby.com only when prospect explicitly asks "where" or "what"
- Max **1 reply per target per day**
- No DM cold-pitches
- No mass engagement (>8 targets/day reads as a bot)
- Never reply as the brand to vulnerable-distress posts
- Cordial silence on competitors

## Hard preconditions for first post (no change)

1. @TobyForTabs creds verified in operator's hands (🔒 acct)
2. No price claim until pricing-reality-reconcile closes — does not block Posts 1/2/3/13
3. No feature/screenshot content (Pillar 3) until reliability hotfix ships — does not block Posts 1/2/3/13

Earliest plausible first-post date is now **Tue 2026-05-12** (was 2026-05-13), contingent on the creds gate clearing by Mon 2026-05-11.

## Dashboard edits made this run

1. TL;DR count + first-post date
2. Strategic anchor — Channel-execution layer line (counts + bot filter)
3. Immediate next steps — X channel block (pin Post 13, post Tue 2026-05-12, fallback names)
4. Phase / Milestone — X execution surface (counts + first-post date)
5. Roadmap Next 2 weeks — first-post date
6. Recent shipments — engagement-targets entry (counts + bot filter + new competitor list)
7. Key decisions — X engagement protocol (added bot-filter line)
8. Open questions — competitor watch rewritten with 5 new names + TabRack/LocalArchive de-list flag
9. Open questions — @TobyForTabs creds gate dates updated (Mon 2026-05-11 / Tue 2026-05-12)
10. Open questions — team-buyer signal canvass adds 2026-05-17 drop deadline
11. Doc index — engagement-targets entry updated to 26 candidates

## Scope check

- Source doc: `toby/x/engagement-targets.md` — owned by `toby-x-strategist`. NOT modified.
- This artifact: written to my run artifact dir per soul rule. Surfaced via dashboard.
- Dashboard: `toby/00-state-of-the-project.md` — owned by this agent, updated via `aios_wiki_write_doc`.

No scope violations this run.