Ingestion — `toby/blog/why-you-have-so-many-tabs-open.md`

What landed#

The toby-blog-seo agent has shipped its run #1 as a structured pipeline:

• One draft — why-you-have-so-many-tabs-open.md, ~1,300 words, P1 (Tab anxiety, named) — top-of-funnel essay reframing tab hoarding as working memory. Brand promise reused verbatim ("It's okay, Toby has it now."). Pin-line: "Bookmarks ask you to retrieve. Toby asks you to recognize."
• Pipeline doc — toby/blog/pipeline.md with 5 pillars (P1–P5), 2-week cadence (1st + 15th, 09:00 UTC), queue of next 7 topics, keyword landscape snapshot, and competitor-blog watchlist (Workona, Partizion, TabGroupVault, MaxFocus, Arc/Dia, OneTab, etc.). Drafts only — agent does not push to CMS.

This is the first published artifact of the blog program. Status is draft in wiki, not published on gettoby.com — the production blog lives at apps/landing/src/content/post/*.md and the operator owns the hand-copy step (open question in pipeline doc).

Why this matters for the dashboard#

The blog program is a fourth ICE-relevant motion alongside Compass / Playbook / X / Incidents. It is materially aligned with the playbook:

• Voice fingerprint matches product/strategy/soul.md and toby/x/strategy.md (post explicitly cites both — though under stale paths, see below).
• Pillar mix mirrors X content pillars 1:1 — pipeline cites this intentionally so blog + X tell the same story.
• P3 (power-user / feature posts) is rel-gated on the blank-page hotfix — pipeline explicitly defers feature posts until reliability lands. Direct dependency on O1 KR1.
• No pricing claims in the draft — pipeline self-imposes the same gate as X content (until pricing-reality-reconcile complete 2026-05-13).
• No AI pre-announce — pipeline explicitly excludes that topic.

Three points need operator action; each is a new or updated entry on the dashboard.

Action items surfaced#

1. X Post 1 distribution loop — operator decision#

The blog draft is the natural destination for X Post 1's "47 tabs is not a personality flaw" line. Pipeline asks: should X Post 1 link the blog, or run parallel?

• Recommended resolution (per the blog draft's own editor notes): X Post 1 links the blog. Gives the X post a click-through destination and converts the line into both top-of-funnel SEO and reactive social.
• Counter-case: X Post 1 is scheduled Tue 2026-05-12 (this week); the blog is still a draft and not yet on gettoby.com. Linking now points to a wiki URL that won't exist on the public site. If the blog publish lags past 2026-05-12, the X post either ships without a link (parallel) or slips a day.
• Cleanest call: operator decides BEFORE 2026-05-12 15:00 UTC whether to (a) publish the blog to apps/landing/src/content/post/ ahead of the X post and update Post 1 with the link, or (b) ship Post 1 parallel as currently drafted and re-aim later.

This is an addressable operator decision, not a long-running open question.

2. Stale path references — flag back to toby-blog-seo#

The blog draft cites toby/x-strategy.md (Voice fingerprint check) and toby/x-content-pipeline.md (Open questions / TODOs). The pipeline doc cites both as well (Voice section + Distribution loop open question).

Both paths moved 2026-05-10:

• toby/x-strategy.md → toby/x/strategy.md
• toby/x-content-pipeline.md → toby/x/content-pipeline.md

toby-blog-seo regen template carries the old paths. Not my folder to edit (scope rule). I flag it via the dashboard open question; the blog-seo agent fixes on next regen, or operator nudges with a one-line update to the agent's orders.

Low operational risk — wiki links still resolve via doc-search fallback, but the citation is technically broken.

3. Reliability gate alignment#

Pipeline locks P3 (power-user / feature posts) behind the blank-page hotfix. Confirms reliability hotfix unblocks more than just CWS reviews — also unblocks a content lane. Worth noting on the reliability immediate-next-step to surface the multiplier effect for operator priority calls.

Cross-references the blog made TO my surface#

The blog draft and pipeline cite the dashboard directly:

• toby/00-state-of-the-project.md — pricing $4.50 vs $6/$10 unresolved (used as guardrail).
• toby/00-state-of-the-project.md — Save Session UI last verified ship date (extension v1.13.0 on 2026-04-14).
• toby/00-state-of-the-project.md — blank-page reliability hotfix gating P3 posts.
• toby/00-state-of-the-project.md — AI relaunch deferred to Q4 2026 (anti-pre-announce).

The dashboard is functioning as the upstream source of truth for the blog program's guardrails. That's the intended pattern — confirmed working.

What I did NOT do#

• Did NOT edit toby/blog/why-you-have-so-many-tabs-open.md to fix the stale path references — sibling-agent folder, hard scope rule.
• Did NOT edit toby/blog/pipeline.md — same reason.
• Did NOT propose a change to the blog draft itself (e.g., copyedits, internal-link fixes) — out of role; blog-seo owns content.
• Did NOT re-publish the dashboard's Recent Shipments date-range for the blog write date (2026-05-09 falls inside the 14-day window the dashboard tracks; surface it as a wiki shipment, not a code shipment).

Suggested dashboard mutations (executed in this run)#

1. TL;DR — append one sentence noting the blog program is live + first draft shipped.
2. Recent shipments — add two entries (blog draft + pipeline doc).
3. Doc index — add two entries.
4. Open questions — add ONE entry covering both the X Post 1 distribution-loop decision AND the stale toby/x-strategy.md / toby/x-content-pipeline.md path references the blog agent uses (combine to avoid noise).
5. Reliability hotfix immediate-next-step — add inline note that P3 blog content is also gated on the fix (multiplier effect).

State changes to persist in memory#

• blog_pipeline_path: toby/blog/pipeline.md
• blog_first_draft_path: toby/blog/why-you-have-so-many-tabs-open.md
• blog_first_draft_status: draft-in-wiki (not yet on gettoby.com)
• blog_first_draft_pillar: P1 (Tab anxiety, named)
• blog_seo_agent_known: toby-blog-seo owns toby/blog/*; auto-regenerates pipeline; ships drafts.
• blog_cadence: 1 post / 2 weeks (1st + 15th, 09:00 UTC).
• blog_p3_rel_gate: P3 (feature deep-dives) explicitly gated on blank-page hotfix — same dependency as X pillar 3.
• blog_stale_paths_observed: blog-seo regen template cites toby/x-strategy.md + toby/x-content-pipeline.md; both moved 2026-05-10 to toby/x/strategy.md + toby/x/content-pipeline.md. Flag for next blog-seo run.
• x_post1_blog_distribution_loop_pending: operator decision needed before 2026-05-12 15:00 UTC.