Ingestion — `toby/blog/onetab-alternative.md`

What landed#

Second draft from the toby-blog-seo agent: an OneTab → Toby comparison/migration post at toby/blog/onetab-alternative.md, ~1,500 words, status draft. This is Pillar 5 (competitor alternatives), mid-funnel, comparison intent. The post was queued as topic-idea #1 in toby/blog/pipeline.md when the program was stood up on 2026-05-09 — it has now shipped to draft.

Authoritative path is the wiki doc itself — this file is a derivative ingestion note, not a re-statement.

Why this matters to the dashboard#

1. Blog program shows real cadence. The pipeline promised a 2-week cadence; first draft 2026-05-09, second draft 2026-05-12. That's faster than promised — the program is in motion, not just announced.
2. Strategic-spine compliance is intact. The post structurally honors three live constraints:
   • Cordial silence on competitor watch. Editor notes (visible at bottom of source) explicitly call out: "Don't mention Uncluttr / TabVault Pro / ThoughtFold / tab-out / leap-tabs" — the five watched entrants from the engagement-targets competitor list. Comparison content is limited to the established cohort (OneTab, Session Buddy, Workona, TabGroup Vault, TheTab, Partizion). This is the Q2 anti-bet #4 ("no public punch-down") rendered into a real published artifact — proof the policy is implementable, not just slogan.
   • Pricing reality guardrail. Body deliberately uses "Free for solo use" + "Paid plans exist for team workspaces" — no dollar figures. Holds the line until pricing-reality-reconcile (O3 KR1, due 2026-05-13) is closed. Editor notes flag this explicitly.
   • Reliability gate respected. Editor notes recommend holding publish until the 3-layer hotfix ships (O1 KR1, due 2026-05-24) "so we don't drive switchers into the bug we're fixing." That ties the blog publish-gate directly to the incident close from 2026-05-11.
3. Generosity to competitors is policy made real. Workona, Session Buddy, TheTab, Partizion are all named with their actual strengths surfaced (Workona = "deeper workspace platform"; Partizion = "thoughtful design and active development"). Self-routes readers who aren't Toby-shaped. This is the brand promise rendered into a SEO-bait genre — comparison posts usually punch down; this one doesn't.
4. Cross-pollination with X is real. The post's headline-equivalent ("URL list vs your work") is a different anchor than X Post 1 ("47 tabs is not a personality flaw"). Editor notes recommend the operator draft a separate X anchor for this post rather than reusing the existing pipeline — a small but operationally important call.

Operator decisions surfaced (or re-surfaced)#

The post itself doesn't require operator action to exist, but its publish path generates four:

1. Publish gate vs reliability hotfix. Hold until 2026-05-24+ hotfix ships, OR publish now and accept switcher-into-bug risk. The editor notes recommend holding; the dashboard already carries the rel hotfix as O1 KR1.
2. X anchor for this post. Operator drafts a dedicated X anchor on "URL list vs your work" rather than reusing X Post 1. This is a new entry for the X pipeline queue if accepted.
3. Chrome Web Store URL slug verification. Post body hardcodes toby-better-than-bookmark/hbdpomandigafcibbmofojjchbcdagbl. Confirm before publish.
4. Image hand-off. Hero image showing OneTab URL list vs Toby visual collection — the post's whole claim rides on this contrast image.

What this is NOT#

• Not a sign that the blog motion has resolved its publish-flow question. Pipeline still has an unresolved open question: "Do drafts get hand-copied into apps/landing/src/content/post/ after editing, or do we change the publish flow?" Neither blog draft has actually shipped to production yet. This is still the first blocker on first publish.
• Not a competitor-watch revision. The post doesn't engage with the 5 watched entrants. Cordial silence policy remains in force.
• Not a pricing reconcile. The post's silence on price is a workaround, not a resolution. O3 KR1 still due 2026-05-13.

Sibling-doc consistency check#

• toby/blog/pipeline.md topic-idea #1 ("OneTab Alternative for Chrome (2026)") matches the shipped draft 1:1 — primary kw, intent, funnel, "why winnable" rationale all align.
• toby/strategy/playbook.md anti-bet #4 (no punch-down) honored in the draft's tone.
• toby/x/engagement-targets.md competitor-watch list (Uncluttr, TabVault Pro, ThoughtFold, tab-out, leap-tabs) deliberately not engaged in the draft — cordial silence policy intact.
• toby/strategy/compass.md axiom 1 (visual tangibility) is the explicit reframe the post leans on ("URL list vs workspace"); axiom 3 (persistence-is-the-product) carried in the "Cloud-backed account" section, framed accurately as table stakes now that Chrome 133 ships native sync (compass anchor #2 already relegated to table stakes — the post is consistent with that, not stale).
• toby/00-state-of-the-project.md blank-page incident referenced by docPath in the editor notes — the cross-link is correct.

No conflicts surfaced. Doc is internally consistent with the strategic spine.

Dashboard updates applied this run#

• TL;DR — extended the blog program one-liner to reflect 2 drafts and pillar diversity (P1 + P5).
• Recent shipments — added 2026-05-12 entry for OneTab Alternative draft.
• Doc Index — added toby/blog/onetab-alternative.md.
• Roadmap / Next 2 weeks — added "operator publish-gate decision (hold for rel hotfix vs ship now)" as an explicit item.
• Open questions — added entry on blog publish flow (already implicit in the pipeline, but now visible at the dashboard level since drafts are accumulating).

Scope reconciliation note#

User instruction: "save it next to the source so it's discoverable." Soul rule: never write into sibling-agent folders (toby/blog/ is owned by toby-blog-seo). Per the established heuristic — when these conflict, the soul rule wins; the derivative lands in the agent workspace artifact dir and surfaces via the dashboard. Discoverability is preserved via the dashboard's Doc Index + this artifact's automatic exposure under Artifacts → toby-pm → 21e5e5e8-ccb4-4a7e-afe5-316ba73a0acf once the next sync runs.