Ingestion — `toby/blog/pipeline.md` (Run #2, 2026-05-12)

Source#

• Path: toby/blog/pipeline.md (sibling-owned: toby-blog-seo)
• Last updated in source: 2026-05-12 09:00 UTC (explicit auto-regen marker added this run)
• Trigger: file_event updated on watched folder
• Scope ruling: derivative saved here (workspace artifact dir), not in toby/blog/ — sibling-agent scope rule wins over "save next to source" per memory rule scope_rule_precedence.

What changed vs. previous ingestion (run ea1223d6-…, 2026-05-12)#

Previous ingestion captured Run #1 (1 draft, 7 queued, pipeline scaffolding). This is Run #2 — the agent shipped a second draft, applied a folder migration, surfaced a new pricing signal, reordered the queue, and added two new internal open questions. Material deltas:

1. Second draft shipped — OneTab Alternative#

• Path: toby/blog/onetab-alternative.md (was queue rank #1; now SHIPPED).
• Pillar: P5 competitor comparison, mid funnel.
• Persona: OneTab refugee (new-adopter / tenured-free overlap).
• Wedge: "URL list → workspace" reframe, anchored by OneTab's own troubleshooting page warning users not to uninstall/reinstall (the December 2025 data-loss notice).
• Voice fingerprint: ~1,500 words, generous to OneTab, explicitly self-routes readers to Workona / Session Buddy / TabGroup Vault / TheTab / Partizion where their needs differ. Honors "no punch-down" anti-bet.
• Distribution: needs its own dedicated X anchor (operator coordination required — the first X Post 1 pair was already claimed by the foundational tab-hoarder post).

2. Folder migration applied#

• Legacy toby/blog-*.md files have been moved into the new toby/blog/ sub-folder.
• Pipeline doc + foundational draft both now live under toby/blog/.
• No content edits during relocation — pure structural move.
• Side-effect: the previous open question I logged about stale path references (toby/x-strategy.md, toby/x-content-pipeline.md) self-healed in this regen — pipeline now correctly cites toby/x/strategy.md and toby/x/content-pipeline.md. Resolve in the dashboard.

3. New pricing-inconsistency signal — TheTab claims Toby is "$9/mo"#

• TheTab's comparison post (thetabextension.com/blog) lists Toby at $9/mo in its comparison table.
• This is a third price that doesn't match either the internal $4.50/mo modeling input OR the public $6/$10 Efficient.app listing.
• Three possibilities: (a) outdated price somewhere internal, (b) TheTab is wrong, (c) a tier-specific price exists we're not tracking.
• Strengthens the urgency of pricing-reality-reconcile (O3 KR1, due 2026-05-13). Surface alongside the existing $4.50 vs $6/$10 contradiction on the dashboard.

4. Queue reordered (one slot dropped, one new slot added at #7)#

Rank	Run #1	Run #2
1	OneTab Alternative	Bookmarks vs Tab Manager (was #2)
2	Bookmarks vs Tab Manager	How to save Chrome tabs (was #3)
3	How to save Chrome tabs	"I'll deal with it tomorrow" (was #4)
4	"I'll deal with it tomorrow"	Session Buddy alternative (was #5; gate released — safe to schedule once OneTab shipped)
5	Session Buddy alternative	Arc browser users — where to put your tabs now (was #6)
6	Arc browser users	Public collection of the week (was #7; ties to O3 KR3)
7	Public collection of the week	"Chrome 133 vs. Toby" comparison page (NEW; ties to existing roadmap entry)

5. New competitor-blog watch entries#

• partizion.io/blog — added as primary citation source for OneTab data-loss claim; "adversary but worth a respectful read" framing.
• thetabextension.com/blog — flagged for the $9/mo Toby pricing claim (see signal above); marked "Worth occasional check-in".

6. New internal open questions (pipeline-internal, not dashboard-blockers)#

• socialdata listening cadence — codify rule: only call socialdata when topic is conversation-driven (live competitor moves, viral incidents). Skipped this run because OneTab story was web-sourceable.
• 🔒 gate column convention — pipeline doc currently uses inline "🔒 rel-gated" notation for P3; questions whether it should be a separate column on the Posts table (matching the X content-pipeline pattern).

7. Confirmed-still-honored guardrails (no change)#

Guardrail	Honored?
No price claims pre-reconcile	✅ OneTab draft says "free for solo use" + "Paid plans exist", no dollar figures
P3 power-user posts rel-gated	✅ P3 explicitly held out of queue
No AI pre-announce	✅ OneTab draft says "AI auto-organize is on the roadmap, not in your hands today" — editor note flags this for softening or removal
No holiday filler	✅ Explicit NOT-pursued entry
Cordial silence on new-entrant competitors	✅ OneTab draft deliberately omits Uncluttr / TabVault Pro / ThoughtFold / tab-out / leap-tabs
No punch-down on incumbents	✅ Generous framing of OneTab; explicit self-route for Workona-shaped readers

Reliability-gate recommendation worth surfacing#

The pipeline doc adds a sharp recommendation: hold publish of the OneTab draft until the 3-layer blank-page hotfix ships (O1 KR1, due 2026-05-24). Reasoning: the OneTab draft is feature-promotional (Save Session, new tab page), so publishing it pre-fix would drive switchers directly into the bug we're fixing. The foundational "Why 80 Tabs Open" draft is less feature-promotional and can publish earlier.

Operator should treat this as a recommendation, not a hard rule — but it's the kind of self-aware coordination that deserves a dashboard entry under Immediate Next Steps.

Dashboard mutations applied this run#

• TL;DR: bumped from "one draft already shipped" to "Run #2 of the blog pipeline · two drafts shipped"; mention migration + reliability-gate recommendation for OneTab publish.
• Strategic anchor § Blog/SEO bullet: update to "two drafts published" + new queue rank order + new wedge framing.
• Immediate next steps: add reliability-gate decision on OneTab draft publish; add OneTab X-anchor coordination (separate from Post 1 pairing).
• Recent shipments: add new entry for OneTab Alternative draft + migration applied.
• Roadmap → Next 2 weeks: bump blog rolling cadence to reflect 2 drafts shipped + adjust dates (next post in 2 weeks lands ~2026-05-26).
• Open questions / blockers:
  • Resolve the stale path references (self-healed this run).
  • Strengthen the pricing contradiction question with the TheTab $9/mo signal as a third data point.
  • Add the reliability-gate decision for the OneTab draft (parallel to publish-flow blocker).
• Doc index: add toby/blog/onetab-alternative.md entry.
• Memory note: record TheTab $9/mo as a tracked external pricing claim under pending_review.

What I did NOT do (and why)#

• Did not write into toby/blog/ — sibling-agent territory. Same scope rule that holds for toby/x/, toby/strategy/, toby/incidents/.
• Did not edit toby/blog/onetab-alternative.md to surface internal coordination notes — the pipeline doc already carries the editor TODOs and the operator owns publish-time edits.
• Did not file a warroom incident or ticket on the TheTab $9/mo signal — it's a marketing signal, not a bug; it strengthens an existing open question that already has a due date (2026-05-13).
• Did not propose a hard reliability gate on the OneTab publish — surfaced as a recommendation per the pipeline doc's own framing; operator decides.
• Did not prioritize Bookmarks vs Tab Manager (new rank #1) over other queued topics — that's the agent's own ranking; dashboard just reflects it.

Cross-references#

• Source doc: toby/blog/pipeline.md
• Co-shipped draft: toby/blog/onetab-alternative.md
• Prior ingestion (Run #1): artifacts/toby-pm/ea1223d6-6512-422e-8cfd-4848dec5340d/blog-pipeline-ingestion.md
• First-draft ingestion: artifacts/toby-pm/ec8b11c5-f5c0-4aaa-824a-c5a8193d4941/blog-why-you-have-so-many-tabs-open-ingestion.md
• New-draft ingestion (Run #1 OneTab): artifacts/toby-pm/21e5e5e8-ccb4-4a7e-afe5-316ba73a0acf/blog-onetab-alternative-ingestion.md
• Dashboard: toby/00-state-of-the-project.md