Content Roadmap
> Content priorities ranked by strategic leverage. Evergreen content preferred. Low-leverage work explicitly excluded.
---
Intelligence Update — 2026-07-13 (Trigger: Commenting UX wishlist update + competitive research completion)
Signal: What I want for the commenting experience to be updated. Key editorial implication: the competitive research corpus is complete (Slite, Coda, Linear, Google Docs patterns documented). Three new content opportunities emerge. They slot into Q4 2026, after the manifesto and vibe coding bridge — they are narrower in audience but lower in effort.
Ranking rationale: The agent determinism content cluster (#1–#3 here) remains highest leverage because it addresses a market 10x larger (LLM agent developers) than the Seed-specific commenting UX audience. Commenting content is Seed-specific brand-building, not market-positioning. But it's very low effort since the research is complete — making it efficient filler between larger pieces.
---
Now (Q3 2026)
1. State Machine Manifesto for LLM Agents ✦ HIGHEST LEVERAGE
Why: The cluster is ready. The argument is distributed across 10+ documents. A single canonical synthesis makes the thesis linkable, shareable, and defensible. Everything else depends on this.
Format: Long-form essay (3k–5k words). Possibly serialized as 3 parts.
Links to: How to Background Agents, State machines to visualize the work of agents, Agents and State Machines, Vibe code like a PRO
Estimated effort: 2–3 days writing + 1 day editing. Distribution: Seed Hypermedia (canonical), dev.to, cross-post summary on X/Bluesky.
2. "From Vibe Code to Deterministic Agents" — The Framing Bridge ✦ HIGH LEVERAGE
Why: The update to Vibe code like a PRO now explicitly connects the "vibe coding" trend to a concrete 4-step deterministic pipeline vision. "Vibe coding" (Karpathy's term) has massive search volume. No one has written the bridge between vibe coding and formal agent determinism. This is the fastest path to mainstream visibility for the thesis.
Format: Short post (800–1,000 words). Can be written in a few hours. Effort: Half-day writing. Distribution: Seed Hypermedia, dev.to (ai-dev-tools audience), X/Bluesky with #vibecoding.
3. "What Goes Wrong Without State Machines" ✦ HIGH LEVERAGE
Why: Counterpoint that strengthens the manifesto. Makes the positive argument concrete by showing failure modes. Format: Technical blog post (1.5k–2k words). Dependencies: Should follow or accompany the manifesto. Could be published simultaneously.
4. Cross-Account Knowledge Graph Case Study: "This Knowledge Map Grew Itself"
Why: Documents the meta-pattern — automated cross-account curation is now operational. Format: Short post (500–800 words) + screenshot of the knowledge map. Source material: The agent-driven cross-linking across accounts.
---
Next (Q4 2026)
5. "What Block-Level Commenting Unlocks" ✦ NEW — MEDIUM-HIGH LEVERAGE
Why: Seed Hypermedia treats comments as block-addressable, linkable, range-selectable primitives — a genuinely novel approach. No existing platform (Slite, Coda, Notion, Google Docs, Linear) implements this. This piece positions Seed's unique differentiator in the collaborative document space. The research is complete; writing is the only remaining step.
Format: Comparative analysis (1,000–1,500 words). Start with a table comparing how each platform handles comment addressing, then explain Seed's block-level approach and what it enables (linked discussions, versioned threads, block-range replies).
Source material: What I want for the commenting experience related links including Slite, Coda, Linear, Google Docs.
Estimated effort: Half-day writing. Can be published between the manifesto and the framing bridge pieces as a lower-effort refresh.
6. Linear→Seed Agent Pipeline — Reference Implementation Tutorial
Why: The 4-step pipeline from Vibe code like a PRO (fetch→expand→spawn→PR) needs a working reference implementation. The community MCP guide already shows the Linear→Cursor connection. Extending it through Seed's agent architecture creates a complete demo that proves the vision.
Dependencies: Community MCP guide (exists), Agent architecture doc (exists). May depend on Agent OSS package stability (Product Backlog #19).
7. "What We Learned from Studying Slite, Coda, Linear, and Google Docs Comments" — Comparative UX Analysis ✦ NEW
Why: The competitive research corpus is complete and unsynthesized. A comparative UX analysis is authoritative reference content that positions Seed as thoughtful on collaborative document design. Low effort (research done), seeds future content (can be referenced in talks, docs, comparisons).
Format: UX analysis post (1,200–1,800 words). Extract patterns (margin annotations, inline highlights, threaded replies), evaluate each platform, identify gaps that Seed fills.
Estimated effort: Half-day writing + diagram creation.
8. Agent Determinism Talk — Conference CFP
Why: Conference talks are highest-leverage distribution. Format: 30-minute talk. Working title: "Your AI Agents Are Unreliable Because They Don't Have State Machines" Dependencies: Manifesto written (#1), @shm/agent-machine OSS package built (Product Backlog #19), working demo with live state machine inspector.
9. Seed Agent SDK Quickstart Guide
Why: Official documentation compounds over years. The Agents project doc defines the architecture; a quickstart makes it usable.
---
Later (2027)
10. Forkable ai-dev-tasks Seed Site — Why: 7.8k potential users. Direct distribution channel. Showcases Seed's block-level linking. Format: Seed site at ai-dev-tasks.hyper.media. See Product Backlog Opportunity 38
Why: 7.8k potential users. Direct distribution channel. Showcases Seed's block-level linking.
Format: Seed site at ai-dev-tasks.hyper.media
See: Product Backlog Opportunity 38
11. "Deterministic Agents" Video Course — Why: Highest-margin educational product. Dependencies: OSS packages stable, manifesto published, talk delivered.
12. "Commenting That Works on Mobile First" ✦ NEW — MEDIUM LEVERAGE
Why: The mobile commenting experience (#3, #4 in the wishlist) is explicitly broken. Fix-and-tell is a proven content pattern. Mobile web developers evaluating Seed are a growing audience. Effort: Depends on when the mobile commenting fixes ship. Content can follow product.
Format: Case study or technical walkthrough (1,000–1,500 words). Show before/after of the mobile commenting experience, architecture decisions.
Dependency: Mobile commenting fixes must ship first. Monitor Product Backlog for completion.
---
Excluded (Low Leverage)
| Idea | Why excluded |
|------|-------------|
| CSS Scroll Shadows follow-up | One-off, no compounding potential |
| Beach holes / SR-71 / riddles | Fun but no strategic value |
| Newsletter business ideas list | Already well-covered elsewhere |
| General "luck" philosophy post | No connection to core thesis |
| Standalone mobile commenting deep-dive BEFORE product ships | Premature — no before/after to show |Do you like what you are reading? Subscribe to receive updates.
Unsubscribe anytime