Engagement-targets ingestion — 2026-05-10

Source#

• toby/x/engagement-targets.md (auto-regenerated by toby-x-strategist, last updated 2026-05-09).
• Companion docs in the same sub-folder: toby/x/strategy.md, toby/x/content-pipeline.md.

What the move means#

The toby-x-strategist agent has reorganized its outputs from flat toby/x-*.md into a proper toby/x/ sub-folder. The three docs that previously lived at the top level (toby/x-strategy.md, toby/x-content-pipeline.md, plus the new engagement-targets file) are now nested under toby/x/. The dashboard had stale cross-references (toby/x-strategy.md) that now need to be updated to toby/x/strategy.md. That's the primary path-drift fix.

Dashboard-relevant signals extracted#

1. X channel goes operational this week. The doc's "Operator one-pager — what to do this week" specifies a 48-hour reply window on @nibzard (Tier A #1) and the first scheduled post landing Tuesday 2026-05-13. This belongs in the dashboard's Next-2-weeks roadmap because it co-occurs with the pricing-audit (2026-05-13) and Phase 2 canary (2026-05-19) windows.

2. Account-gate blocker. Step 1 of the operator one-pager is "Verify @TobyForTabs creds are in our hands (the 🔒 acct gate)". Until the creds are confirmed, nothing in the X channel ships. New dashboard blocker.

3. Team-buyer pillar resolution (half-answer). Bucket recap table: team-buyer = 0 targets at every tier out of 22 candidates. The strategist asks operator to "confirm we drop the team-buyer pillar from X entirely (or rebuild it)." This is half-resolution of the playbook open question on team-buyer signal — X surfaces zero signal; the Slack/LinkedIn operator-led canvass is what's left.

4. Competitor watch list (informational only — do-not-engage). Three competitor/adjacent accounts named:

   • leap-tabs.com (@RomanGweb3) — competitor founder explicitly building a tab manager.
   • TabRack (@_AHA_Y) — open-source tab manager extension launched 2026-04-23.
   • LocalArchive (@Zackdevcv) — local-first Chrome archive extension; adjacent category. None of these had appeared on the dashboard. They go in Open questions / blockers as a passive watch.

5. Engagement protocol (hard rules in the doc, useful as PM context for any other agent that might want to interact with X): no link in first reply, max 1 reply per target per day, no DM cold pitches, no mass-engagement (>8/day looks like a bot). Operator-only, never agent-driven.

What is NOT material to the dashboard#

• Per-target reply drafts — execution-level, owned by toby-x-strategist + operator.
• Tier classification mechanics — strategy-doc detail.
• Brand-voice calibration ("DO NOT REPLY" on vulnerable tweets) — execution standard, not strategic.
• The toby/x/content-pipeline.md Post 1 / Post 12 references — operational, owned by the pipeline doc itself.

Resolved cross-reference#

• Compass / playbook reference to toby/x-strategy.md is now stale → toby/x/strategy.md. Fixed in the dashboard this run.

Decisions taken#

• Updated toby/00-state-of-the-project.md (Recent shipments + Roadmap → Next 2 weeks + Open questions + Doc index).
• Did NOT write any file into toby/x/ (out of sub-folder scope; that's toby-x-strategist's territory).
• Did NOT modify toby/strategy/* (out of sub-folder scope; that's toby-strategist's territory).

Memory carries#

• New pending review: confirm @TobyForTabs account creds — operator-side blocker, dashboard cannot resolve.
• New pending review: when the Tue 2026-05-13 first post lands (or doesn't), note it in next dashboard cycle — early signal for whether X channel is a real motion.
• Open question carry: blank-page reliability + Phase 2 silent slip remain unchanged.