X Content Pipeline — Ingestion Notes (2026-05-10)

Source#

• Doc: toby/x/content-pipeline.md
• Last regen: 2026-05-10 (auto, toby-x-strategist)
• Drafts only — operator-published, not agent-published.

Diff vs. last ingestion (2026-05-10 earlier, memory sibling_agent_outputs_observed.toby-x-strategist)#

Field	Previous	Now	Action
Draft count	12	13	+1 (new Post 2)
Evergreen / reactive mix	60/40	~55/45	absorb in summary
First scheduled post	Tue 2026-05-13 (per memory)	Tue 2026-05-12 (per pipeline calendar)	fix dashboard
@nibzard reactive (Post 4) window	open-ended	closes 2026-05-12	escalate to Immediate Next Steps
P1 sub-frame	none called out	tab-loss grief	add to anchor/persona context
Competitor watch additions	leap-tabs / TabRack / LocalArchive	+ ThoughtFold + Uncluttr + TabVault Pro + tab-out	add to Open Questions / Key Decisions
Pinned-post candidate	(legacy 2025-06-12 outage status still pinned)	Post 13 drafted as replacement	reference in next-steps
Holiday-filler rule	implicit	explicit (Mother's Day 2026-05-10 deliberately skipped)	informational only

What the dashboard needs#

1. Date fix in two places:
   • "Immediate next steps → X channel goes live this week" item: Tue 2026-05-13 → Tue 2026-05-12.
   • "Roadmap → Next 2 weeks → X channel goes operational" item: same correction.
2. New nuance in strategic anchor: P1 audience frame now has a tab-loss grief sub-frame (4-signal cluster); reframes the brand promise "It's okay, Toby has it now." against new-entrant reliability uncertainty.
3. Competitor watch expansion (Open Questions section): add ThoughtFold + Uncluttr + TabVault Pro + tab-out to the do-not-engage cordial-silence list. Three of them (ThoughtFold neurodivergent positioning, Uncluttr AI-organize, TabVault Pro and tab-out as low-signal entrants) flagged informationally — no engagement.
4. Urgent (48h) operator item: @nibzard reactive reply MUST go out by 2026-05-12 or the post is dropped from the pipeline. Calls back to memory's acct gate — if account-ownership-verification isn't cleared by Mon 2026-05-11, this reactive window expires unused.
5. Pinned-post action can be queued for Day 1 (post acct-gate) — surfaces under "X channel goes live this week" as Step 3.

Pre-conditions stack (no change, restated for operator clarity)#

Three hard gates from soul memory still apply, ordered by likely-resolution date:

1. acct — operator verifies @TobyForTabs creds (must clear by Mon 2026-05-11 to keep Tue 2026-05-12 first-post date)
2. price — pricing-reality-reconcile closes (playbook O3 KR1, due 2026-05-13) — gates Post 13 pinned-post if price is mentioned (it isn't directly, but gettoby.com is) and any future pricing-adjacent posts
3. rel — reliability-blank-page-fix ships (playbook O1 KR1, due 2026-05-24) — gates Post 8 (P3 power-user screenshot post); not blocking for Tue 2026-05-12 launch

Internal consistency check vs. compass & playbook#

• ✅ Post 2 (tab-loss grief) lives compass axiom 3 (Persistence-is-Activation) — consistent.
• ✅ Post 3 leans on axioms 1 + 2 (visual tangibility + ambient-not-invocational), explicitly NOT on cloud-sync — consistent with compass anchor 2 demotion.
• ✅ Post 8 self-gates on O1 KR1 hotfix — consistent with playbook red-team.
• ✅ Anti-bet on AI-organize hype is honored (no AI feature pre-announce drafts).
• ✅ Anti-bet on punch-down is honored (Arc handled carefully in Post 11; competitors not named in trash-talk frame).
• ✅ Public-collection-of-the-week (Post 6 + cadence) lives O3 KR3 (4 featured by 2026-06-30, the under-pulled curator loop).
• ⚠️ Open question carried forward: Posts 6 and 11 both require operator-pulled data / external permission. Pipeline cannot fully self-execute without the operator's hands-on involvement — consistent with strategy doc's "operator publishes, agent drafts" boundary.

No scope violations#

• I did not write into toby/x/.
• I did not regenerate the source.
• Dashboard edits are confined to toby/00-state-of-the-project.md (my owned doc).
• This derivative lives in my artifact workspace and is auto-surfaced on the agent's Artifacts tab.