X Strategy ingestion — 2026-05-10

Source doc: toby/x/strategy.md — title "Toby on X — Strategy", _Last updated: 2026-05-09 · auto-regenerated by toby-x-strategist_. Do not hand-edit the source; this ingestion note lives in the dashboard agent's artifact dir.

What's in the source doc (one-paragraph faithful summary)#

The X strategy is a re-entry, not a relaunch for the dormant @TobyForTabs handle (uid 778656014727983104, Vancouver BC, 2,913 followers, 1,184 lifetime tweets, account from Sept 2016). The account has effectively been silent — only 2 tweets in the last 14 months; engagement on the last ~12 visible org tweets is anemic (1–6 likes despite 2.9k followers); zero mentions of @TobyForTabs in the past 14 days. Meanwhile, organic "too many tabs" / "tab hoarder" complaints surface in dozens per fortnight from unattached knowledge workers, AuDHD organisers, fic readers, devs, and founders. The plan: calm, low-volume in-character posting (3 originals + 5–10 replies / week, 1 quote-tweet / week, 1 themed post / fortnight) around five audience pillars — heavy organisers, switchers from Arc/Dia/Pocket/SigmaOS, KM-adjacent influencers, team buyers (currently invisible on X), and adjacent cultural communities. Voice: calm, specific, generous; never breathless. Anti-metrics: follower count, vague engagement rate. Leading metrics: ≥5k median impressions / post by week 6; ≥1 ICP-shape reply / post; ≥15% first-touch reply-to-follow rate. Lagging: CWS-install attribution via UTM-tagged short links + paid-signup attribution via customer_metadata.attribution_source = 'x'. Competitor benchmarks (Arc/Dia, SigmaOS, OneTab, Workona, Pocket) confirm the category is quieter than the brand soul thinks — the risk is failing to occupy a vacuum, not getting out-marketed.

Cross-references to dashboard concerns#

The X strategy is not standalone. It declares hard pre-conditions and dependencies on items the dashboard already tracks:

X strategy assertion	Dashboard item it touches	Effect
"Pricing claim — we must not say 'Toby is $X' in any post until pricing is reconciled"	pricing-reality-reconcile (ICE 600, O3 KR1, due 2026-05-13)	Adds a second downstream dependency beyond role-based-paywall-gating. Reflected in dashboard Immediate Next Steps + Open Questions.
"Reliability claim — pillar 3 (power-user shortcuts) should wait until reliability hotfix ships"	reliability-blank-page-fix (ICE 576, O1 KR1, due 2026-05-24)	Dashboard now flags this as an X-content-blocker, not only a CWS/reviews issue.
"AI feature roadmap — Q4 2026 AI relaunch is internal — do not pre-announce on X"	Existing playbook anti-bet (1) + compass anti-promise	Now also enforced at the channel layer; "X strategy voice charter" added as a citation alongside playbook + compass in the Roadmap entry.
"Account ownership — handle bound to a Vancouver address from 2016. Block on first post until verified."	NEW — not previously in dashboard	Promoted to its own item in Immediate Next Steps and Open Questions.
"Team-buyer pillar — drop from X or rebuild?"	Existing playbook open question + persona data (4,908 multi-team users / 79 paid Team subs)	Reframed: the prior playbook question (Slack/LinkedIn canvass) is now the resolution path. Both docs agree on the operator-led 1-week canvass test.
"Engagement guardrails — no link in first reply?"	NEW — operator-decision question	Added to Open Questions; operator call needed before pillar-1 replies start.
"Public-collection pride loop" execution surface = pillar 5	public-collection-pride-loop (ICE 336, O3 KR3)	Dashboard Immediate Next Step now names X pillar 5 as the execution surface (alongside blog).

What changed in the dashboard this run#

1. Bumped TL;DR to reflect the X strategy as the channel layer, in addition to the existing Compass/Playbook/Bets strategic spine.
2. Strategic anchor section — added a 4th bullet: "Channel layer — Toby on X — Strategy" with the dormancy diagnosis + cadence + 3 hard pre-conditions.
3. Immediate next steps — appended @TobyForTabs account-ownership verification. Tightened wording on pricing-reality-reconcile, reliability-blank-page-fix, and public-collection-pride-loop to cite the X strategy where it adds a downstream dependency.
4. Phase / Milestone progress — added "X channel strategy v1 — PUBLISHED to wiki 2026-05-09".
5. Recent shipments — added the same publication.
6. Roadmap (Next 2 weeks) — added account-ownership verification and tied pricing + reliability deadlines to X content un-blockers.
7. Roadmap (Next month) — curator-loop bullet now names X pillar 5 as execution surface alongside blog.
8. Key decisions — added "X re-entry, not relaunch" decision.
9. Open questions — added two: account-ownership verification (hard block) and engagement-guardrails operator decision. Reframed the existing team-buyer-pillar question with the X strategy's framing of the same problem. Fixed the broken toby/x-strategy.md citation that pointed at the old flat path.
10. Doc index — added the three toby/x/*.md docs (strategy, content-pipeline, engagement-targets).

What I did NOT do, and why#

• Did not edit toby/x/strategy.md — out of sub-folder scope (it belongs to the toby-x-strategist agent, which auto-regenerates the doc each run and has a "do not hand-edit" banner). The hard scope rule in the agent soul overrides the operator order to "save the derivative next to the source." Saving here in artifacts/toby-pm/<run-id>/ is the correct compromise: discoverable via the Artifacts tab + wiki, but does not pollute another agent's sub-folder.
• Did not move or rename the source — the strategist owns the path. If the prior flat-path reference in the dashboard is now stale, the fix is to update the citation (done above), not the source.
• Did not change toby/strategy/* — the strategy spine is the strategist's sub-folder. The X strategy's open questions about pricing / reliability / AI pre-announce are already reflected in the playbook / compass / bets; no rewrite needed there.

Residual questions for the operator#

1. Should the engagement-guardrail "no link in first reply" be confirmed (X strategy default) or overruled?
2. Who owns the account-ownership verification? (Likely operator, but unowned in the dashboard right now.)
3. Should toby/x-strategy.md (old flat path) still exist as a redirect / stale doc, or has the strategist already deleted it? (My wiki tree shows only the new path, so this may already be resolved — but flagging in case.)