Why: The Devin case study is the perfect narrative vehicle. It proves the problem exists today. Links the abstract proposal to concrete reality.

Form: Long-form article (3-4k words)
Audience: Open source maintainers, AI safety community, P2P developers
Dependencies: None — all source material exists
Links: Graduated Trust proposal, Devin case study

Why: The Community Models document shows Seed already has the dual trust model (formal communities + web of trust) that Graduated Trust needs. This essay bridges the theory to Seed's actual implementation, proving Graduated Trust isn't theoretical — it's buildable on Seed today.

Form: Medium-length article (2k words)
Audience: Seed adopters, OSS foundation security teams, P2P developers
Dependencies: Graduated Trust in Practice (#1) should publish first
Links: Community Models, Graduated Trust

Why: The LLM Wiki spec is a 3,000-word blueprint. It demonstrates Seed's architectural philosophy: build on existing primitives (no new storage), respect human intent (human-curated flag), design for self-healing (version tracking, periodic regeneration). This is content gold for system architects and knowledge management enthusiasts.

Form: Technical architectural essay (3-4k words)
Audience: System architects, knowledge management community, LLM application builders
Dependencies: None — spec is complete

Why: Captures the Rich Hickey-inspired schemaless-with-query-lenses decision before implementation locks in.

Form: Technical ADR + blog post
Audience: Seed contributors, developers evaluating Seed

Why: The State Machines — Knowledge Map reached critical mass (10+ docs across 3 accounts) and is now linked from Short Posts. One authoritative long-form guide consolidates the cluster into a flagship artifact and gives every future post a hub to link to — the capstone of the Agent Observability signature idea.

Form: Long-form guide (3-4k words) using the Knowledge Map learning paths as outline
Audience: Frontend engineers, agent builders, XState/state machine community
Dependencies: None — all source material exists
Links: Knowledge Map, Short Posts

Why: The Jean Web Access behind Tailscale field note is the first infrastructure case of state confusion (two modes, easy to mix up). It extends the state machine franchise into DevOps territory and bridges the state machine and self-hosting clusters.

Form: Short essay (1-1.5k words)
Audience: Self-hosters, DevOps engineers, state machine community
Dependencies: Jean field note (published 2026-07-31)

Why: The self-hosting lane is now author-labeled and cross-linked: the Jean Web Access behind Tailscale post's "Related reading" section groups it with Deploy a Seed Site From Your Own Fork, Codesign your Electron Application for Windows, and Velopack: Delta Updates for Electron Apps. A hub page curating the four how-tos (with a deployment-modes decision table: bind-localhost vs bind-tailnet-IP × direct vs Serve proxy) mirrors the State Machines — Knowledge Map hub pattern already proven in this repository.

Form: Hub page + decision table
Audience: self-hosters, local-first devs, Seed adopters
Dependencies: None — content exists; pairs with Opportunity Backlog #12

---

Why: Makes the connection between the community models taxonomy and the social-graph-aware UI pattern explicit. This is a strategic argument about Seed's unified data model — the same graph serves contribution scoring (long distances) and UI relevance (short distances).

Form: Short essay (1.5-2k words) + mockup
Audience: Seed community, P2P product designers

Why: Establishes the foundational logic for graduated trust. Can be published independently or as part of a series.

Why: Positions the comments feature as a protocol innovation, not just a UI feature.

Timing signal (2026-07-27/28): Comments feature implementation actively progressing. This piece should align with feature launch.

Timing signal refresh (2026-07-31): Seed design sprint is live — Create Site, Search, and Identity stories all updated today with live discussion on hierarchical navigation, desktop account-picker gaps, and comment infrastructure. Launch-aligned content remains on track.

Additional hook (2026-07-31, reconciliation): What I want for the commenting experience to be gives the essay a first-party problem statement to open with (redirect-based flows).

Additional hook (2026-08-03): The document machine spec explicitly ties editing states to the commenting experience in its See also (What I want for the commenting experience to be) — the essay can open with the editor-state requirements for inline comments.

Why: Connects Graduated Trust theory to Seed's actual implementation. Useful for onboarding.

Why: Generalizes the Jean deployment artifact into a timely theme: AI infrastructure self-hosted on your own tailnet (private, token-gated, health-checked). Pairs with the self-hosting cluster and Seed's self-owned-infrastructure ethos.

Form: Essay (1.5-2k words)
Audience: indie hackers, privacy-minded developers
Dependencies: Jean guide stable (#12)

Why: Remodeling the web + What I want for the commenting experience form a thesis; the synthesis turns two posts into a positioned editorial voice for the Seed vision.

Form: Essay (1.5-2k words)
Audience: Web platform critics, P2P enthusiasts, designers
Dependencies: Both short posts (published)

Architecture evidence (2026-08-03): The document machine spec is the concrete "what the web should feel like" answer: explicit states, no draft leakage into old versions, guarded rebase.

Why: The Seed team wants to copy Jean's docs patterns; the Jean Web Access behind Tailscale post is a perfect worked example of the structure (symptom → recommended setup → failure mechanism → quick checks → "is this a bug?" diagnosis). A docs-craft piece dissecting why this structure works positions the author as a docs authority and directly feeds the Jean template opportunity (Opportunity Backlog #15, Research Roadmap #9).

Form: Essay (1.5-2k words) + reusable template checklist
Audience: docs engineers, devtools writers, Seed contributors
Dependencies: Jean Deployment Guide (#12) — flagged: body entry missing in current merge; footer-only

---

Form: Conference talk or workshop
Target: RustFest, FOSDEM, or P2P conference

Form: Short book (50-80 pages, digital-first)
Precondition: At least 3-4 articles published, measurable audience engagement

Why: The unifying piece that connects Graduated Trust + Community Models + LLM Wiki into the master narrative. Positions Seed as trust infrastructure for the AI era, not just a hypermedia protocol.

Form: Long-form essay (4-5k words)
Precondition: At least the first three essays in this roadmap published

---

_Created: 2026-07-28 | Updated: 2026-07-31 (added #12 Jean Deployment Guide + Projects entry, #13 Private AI Stack essay; refreshed timing signal for #7 from active design sprint) | Next review: on significant repository change_

_Reconciled 2026-07-31 (second pass): filled the referenced-but-missing #12 item; merged state-machine cluster content — #14 definitive guide, #15 config-as-state-machine bridge, #16 web criticism synthesis; added commenting hook to #7. Concurrent execution content preserved in full._

_Post-reconciliation append 2026-07-31: added Related-section evidence (Seed team's "this developer docs are amazing" note) to #12 Jean Deployment Guide. All previous analysis preserved. | Next review: on significant repository change_

Why: The Vibe code like a PRO update formalized the 4-step pipeline — get assigned Linear issues → expand with codebase context → spawn background agents → create PRs — and cross-linked the tactics post, the state machine thesis, the product entry, and a working MCP template. All source material exists; the guide becomes the hub that closes the loop and answers the author's own open question (#IkGu9X1J).

Form: Long-form guide (2-3k words) + working mcp.json + PR checklist
Audience: indie hackers, Cursor/Claude Code users, agent builders, Linear users
Dependencies: None — all source material exists; pairs with Opportunity Backlog #16

Why: The 4-step pipeline stops at "create PR" — the trust problem starts there. A companion piece proposing step 5 (verification gates: state trace, test evidence, human review protocol) bridges the pipeline to Agent Observability (Signature #1) and Graduated Trust (Signature #2); the pipeline is the perfect concrete carrier for the trust argument.

Form: Essay (1.5-2k words)
Audience: same as #19 + maintainers reviewing agent PRs
Dependencies: #19 should publish first; links to Research Roadmap #10

_Updated: 2026-07-31 (Vibe code trigger) — added #19 pipeline guide and #20 verification-gates companion. All prior content preserved._

Why: The State Machines lane just demonstrated the hub pattern (lane → Knowledge Map → definitive guide). The AI & Agent Workflows lane is at the same pre-hub stage the state-machine lane was at before its map — three curated posts plus product and community anchors (Product Backlog #18, MCP template). A Knowledge Map for this lane gives Signature #3 the same canonical hub — see Opportunity Backlog #17.

Form: Hub document mirroring the State Machines — Knowledge Map structure
Audience: agent builders, Cursor/Claude Code users, Linear users
Dependencies: None — content exists; #19 guide will link to it

When a labeled lane appears in the Short Posts hub, apply this ladder to decide investment: 2 posts = thesis → schedule synthesis essay; 3-5 curated posts = lane → schedule guide/hub; 10+ docs across accounts = Knowledge Map + definitive guide (the State Machines lane is the model). This keeps investment proportional to author intent instead of agent enthusiasm.

_Updated: 2026-07-31 (Short Posts hub restructure trigger) — added #21 Knowledge Map hub; appended evidence to #14/#16/#18/#19; added Cluster Maturity Ladder governance note. All prior content preserved._

Why: The homepage surfaced Notes about how the document machine should work — a first-party spec of Seed's editor as a state machine with cross-account implementation (Project Plan, XState v5 465 lines; Publish Guard; Draft Publishing Chain; Multi-draft; Document Web Editing) and an external Case Study on the UI with State Machines hub. This is the flagship concrete instance of the state machine thesis in production and the natural capstone for the cluster — see Opportunity Backlog #18, Signature #6.

Form: Long-form essay (3-4k words) + state diagram
Audience: frontend engineers, editor builders, Seed adopters, XState community
Dependencies: None — all source material exists; pairs with Opportunity Backlog #18 and Signature #6

Why: Modeling resizable panels using State Machines (homepage-surfaced) + Pure CSS Scroll Shadows + external UI with State Machines hub participation form a UI-pattern lane; a recurring series compounds with the definitive guide (#14) and the external community — see Opportunity Backlog #19.

Form: Recurring compact case-study posts; first follow-up on app-chrome panel splits using the Seed Frontend App/Layout Current State tech talk
Audience: frontend engineers, XState/state machine community
Dependencies: None; first installment exists

Why: The serif/sans essay is source-backed original research already curated on the homepage's Last Writings; it opens a differentiated evidence-based design lane (with Canva Pause as the product-craft sibling) — see Opportunity Backlog #20.

Form: Series; installment #1 exists (serif vs sans); follow-ups on line length/measure and screen readability myths
Audience: designers, frontend engineers, product builders
Dependencies: None

#14 (State Machines definitive guide) — new source material. The guide's outline should now include the document machine as its flagship in-production case study (states: loaded/editing/publishing/rebase/version-history) and the resizable-panels UI pattern; both are homepage-curated.

#16 (Web & Hypermedia synthesis) — architecture evidence. The document machine spec is the concrete "what the web should feel like" answer: explicit states, no draft leakage into old versions, guarded rebase.

When a post appears in the homepage's Latest Short Posts or Last Writings sections, treat it as author-curated at the top level: 1 homepage surfacing = consider series/hub investment; repeated surfacing alongside a labeled lane = flagship territory (the document-machine post is the current model).

_Updated: 2026-08-03 (homepage trigger) — added #22-#24; extended Cluster Maturity Ladder governance note; appended evidence to #7/#14/#16. All prior content preserved._