_Last updated: 2026-07-28 (trigger: Graduated Trust References section expanded with formal cross-links. Added 3 new opportunities: Commenting Widget, Graduated Trust Course, Agent Session Logger.)_
_Next review: On significant repository change_
---
Ranking Criteria
Confidence (1-10): How certain the opportunity is real based on evidence
Difficulty (1-10): How hard to build/first version (higher = harder)
Seed Fit (1-10): How much this strengthens Seed's ecosystem and positioning
Asymmetric Upside: Can this succeed wildly with moderate effort?
---
1. 🏆 Graduated Trust: PR Trust Scoring as a Service
Problem
OSS maintainers are drowning in AI-generated "slop PRs" while simultaneously facing sophisticated supply-chain attacks (xz-utils style). Current solutions (2FA, signed commits, Sigstore) only verify identity — they don't answer "should I trust this person to touch this code?" The cost of contribution review is paid entirely by maintainers, in attention.
NEW EVIDENCE from Graduated Trust cross-links (2026-07-28):
Devin Booking System — real-world proof: 6 AI-authored PRs merged to production in one month. This IS the trust problem today, not hypothetical.
Community Models in Seed — Seed already has the dual trust model (formal communities + informal web-of-trust).
Secure Scuttlebutt — technical precedent: social graph as infrastructure, follow/hops for replication scope.
P2P Trust & Safety knowledge base — foundational primitives: key-based identity, UCAN, capabilities, Sybil resistance.
Combined thesis: The problem is urgent (Devin ships real PRs today), the solution is novel (social-graph distance), and the primitives exist (Seed contacts, capabilities, P2P protocols). Nobody else connects these three dots.
Additional evidence: Graduated Trust proposal, Fix OSS with Seed Hypermedia, Vibe code like a PRO.
Users
OSS maintainers of popular packages (npm, PyPI, crates.io ecosystems)
Foundation security teams (OpenSSF, Apache, Linux Foundation)
Enterprise open source program offices (OSPOs)
CI/CD platform providers (GitHub, GitLab)
Solution
A GitHub/GitLab app that computes a trust score for every PR contributor based on their position in a cryptographically verifiable Web of Trust. The score determines friction level:
Hop 0-1 (maintainers + direct vouchees): No friction, normal review
Hop 2 (friend-of-friend): Light checks (key age, single reviewer ack)
Hop 3+ (distant): Proof-of-context questions, observation windows, multiple reviewers
No path: Maximum PoW + canary quarantine
MVP
A CLI/server that constructs a trust graph from signed contacts
A GitHub bot that adds a trust-score label + friction checklist to PRs
A simple hop-distance badge in the PR
Publish on a Seed site as the canonical trust-graph viewer.
Distribution
Ship as a free GitHub App with a "Pro" tier for private repos
Publish the Graduated Trust essay widely (HN, lobste.rs, r/programming)
Partner with one high-profile OSS project (e.g., Homebrew, Tailwind, Vite) as a pilot
Cross-post to OpenSSF, CNCF security channels
Pricing
Free tier: Public repos, basic hop scoring
Team tier ($99/mo): Private repos, custom friction policies, canary quarantine
Enterprise ($499/mo): SSO, audit logs, EigenTrust-style path quality weighting, integration with existing CI/CD
Competition
Sigstore: Verifies identity, not trustworthiness — complementary
Socket.dev: Detects malicious packages, not malicious contributors
GitGuardian: Secrets detection, not trust scoring
EigenTrust (academic): Paper only, no product
Keybase (deprecated): Had proof-of-identity but not scoped vouching
Confidence
9/10 — The problem is widely acknowledged (xz-utils, slop PRs are daily pain), the solution is novel, and Seed already has the primitives. The Devin case study now provides concrete, documented evidence that the AI contribution problem exists TODAY.
First Experiment
Build a tiny demo: two Seed accounts, one vouch, display hop distance on a mock PR page. Show it to 5 maintainers of popular npm packages. Would they install a GitHub bot that shows this? Would they pay?
Roadmap
MVP: GitHub bot with static hop scoring (week 1-2)
Add vouch creation UI inside Seed (contacts extension) (week 3-4)
Proof-of-context question generation (week 5-6)
Observation windows and quarantine mode (week 7-8)
Self-hosted Enterprise (week 9-10)
---
2. Seed Commenting Widget: Embeddable Content-Addressed Comments for Any Website [NEW]
Problem
The web's commenting ecosystem is broken. Disqus is heavy and ad-ridden. Utterances uses GitHub issues as a database. Most comments on the web are unauthenticated, unsignable, and lost when the page changes. Seed users want "the commenting experience to be perfect" — with expand-to-full-window, block-level references, mobile-friendly editors, and no redirects. Seed's content-addressed, cryptographically signed, threaded commenting system solves all of this — but only for Seed-native documents.
Evidence: What I want for the commenting experience to be — 5 explicit UX pain points. Killing the Web Redirect for Commenting — redirect problem solved internally. Discussions Panel Is Confusing.
Users
Any website owner who wants better comments than Disqus/Facebook/utterances
Bloggers, indie publishers, documentation sites
Seed site owners wanting embedded discussions on their custom landing pages
P2P/Web3 projects wanting cryptographically verifiable comments
Solution
A lightweight JavaScript widget (< 20KB) that any website can embed via a script tag. It renders Seed-powered comments: content-addressed, cryptographically signed, threaded, with block-level linking, no redirect, and optional key-based identity. Comments are stored on Seed's network — the website owner doesn't need infrastructure.
MVP
<script src="https://cdn.seed.hm/comments.js" data-account="..." data-path="..."></script> embed tag
A hosted JS bundle that renders comment threads fetched from Seed servers
Inline comment creation with keypair derived from ephemeral or stored seed phrase
Basic moderation: site owner can delete/hide comments via their Seed account
Distribution
Free tier for personal blogs (5 sites, basic moderation)
Embed on Seed's own docs site first as a reference implementation
Blog post: "Seed Comments Are Better than Disqus — Here's Why"
Launch on ProductHunt, Hacker News as a Disqus alternative
WordPress plugin, Hugo/Eleventy shortcode, generic JS embed
Pricing
Free: 5 sites, 1,000 comments/month, basic moderation
Pro ($9/mo): Unlimited sites, custom CSS, advanced moderation, export
Enterprise ($49/mo): Self-hosted comment server, SSO, audit logging
Competition
Disqus: Heavy, ad-supported, owns your data, not content-addressed
Utterances/Cusdis: GitHub-based, no cryptographic guarantees
Hyvor Talk: Paid, centralized, no P2P
Isso: Self-hosted, Python, minimal features
Remark42: Self-hosted, Go, no block-level linking
Confidence
7/10 — The UX pain is documented (5 specific points + redirect solution). The technology exists (Seed's existing commenting infrastructure). The challenge is packaging for non-Seed sites and competing with established alternatives. Strong Seed ecosystem benefit: more Seed identities in the world.
First Experiment
Embed a Seed comment thread on a simple static HTML page. Ask 3 Seed users: "Would you switch to this for your blog?" Time how long it takes to set up (target: under 2 minutes).
---
3. "Graduated Trust in Practice" Cohort-Based Course [NEW]
Problem
The Graduated Trust proposal is intellectually compelling but abstract. OSS maintainers, OSPO teams, and foundation security staff need practical guidance on implementing graduated trust — how to construct trust graphs, author vouch policies, configure friction levels, integrate with GitHub/GitLab, and handle edge cases (Sybil clusters, compromised accounts). Without a structured learning path, the concept stays theoretical.
Evidence: Graduated Trust — Strategist agent flagged "Graduated Trust in Practice" as #1 content priority. The document has 5 open questions (reputation calibration, Sybil resistance, privacy, scope governance, compromise recovery) that are perfect course modules. Fix OSS with Seed Hypermedia — embeds the full proposal with "Hope y'all can read it and give some feedback!" signaling demand.
Users
OSS maintainers of popular packages
Open source program office (OSPO) managers
Foundation security engineers (OpenSSF, CNCF, Apache)
Platform engineering teams considering trust scoring
Security researchers studying supply-chain attack mitigation
Solution
A 4-week cohort-based course teaching the full graduated trust toolkit: trust graph construction and hop distance calculation, vouch policy authoring (scopes, expiration, revocation), friction level configuration (proof-of-context, observation windows, canary quarantine), integration with existing CI/CD (GitHub Actions, GitLab CI), advanced topics (Sybil resistance, EigenTrust weighting, compromise recovery).
MVP
A single cohort (10-15 participants) run live over 4 weeks
4 modules released weekly: Theory → Graph Construction → Policy Configuration → Production Deployment
Each module: pre-recorded video (30 min), live Q&A (60 min), hands-on exercise
Graduates receive a signed Seed capability certificate verifiable on the trust graph
Distribution
Announce on HN when the Graduated Trust essay drops (this is the "take the next step")
Cross-post to OpenSSF, CNCF, and OSPO mailing lists
Offer free seats to maintainers of top-1000 npm packages
Seed community announcements
Conference talk: "We Built a Trust Graph for Open Source — Here's How" (lead gen)
Pricing
Individual ($299): Full course, exercises, certificate, trust graph badge
Team ($999): Up to 5 seats, private cohort option, Slack support
Enterprise ($2,999): Private cohort, custom friction policies, integration support
Competition
OpenSSF Best Practices Badge: Self-serve checklist, no curriculum
Linux Foundation courses: Broad, not focused on trust/contribution gating
Sigstore workshops: Focus on signing, not on trustworthiness
Conference workshops (KubeCon, Open Source Summit): One-off, no follow-through
Confidence
7/10 — The content exists (proposal + 5 open questions). The Strategist flagged this as the #1 content action. Risk: building the cohort format and exercises from scratch. Low cost to test (single cohort).
First Experiment
Create a single module: "Building Your First Trust Graph." Run it as a free lunch & learn for 5 maintainers. Record it. Ask: "Would you pay $299 for the full course?"
---
4. Agent Session Persistence Library (Seed-native Audit Logger) [NEW]
Problem
The Agents document defines a formal model: Agent Specifications, Instances, Sessions (sequential logs), Completions, and Triggers. But there is no standard library for agents to automatically persist their sessions as Seed documents. Every agent implements ad-hoc logging: the Gardener writes activity reports, the Product Scout updates the backlog, the Knowledge Manager tracks topics. None are machine-readable, queryable, or auditable. Teams running multiple agents have no unified audit trail.
Evidence: Agents — full formal model: Specification, Instance, Session, Completion, Trigger. The agents in this repository (Gardener, Product Scout, Content Strategist, Knowledge Manager) each implement ad-hoc logging. No standard format exists.
Users
Developers building Seed-native agents (Seed team, external agent builders)
Teams running multiple autonomous agents needing audit trails
Site owners who want to see what agents did in their spaces
Researchers studying agent behavior patterns
Solution
An npm package (@shm/agent-logger) that provides a simple API: createSession(), logCompletion(), logToolCall(), logError(). Each call creates or updates a Seed document under /_logs/agent-name/session-id/ with structured content (timestamps, states, inputs, outputs, errors). Documents are content-addressed, signed, and queryable via Seed's existing search.
MVP
createSession(spec): DocumentRef — creates a new log document at /_logs/agent-name/session-timestamp
logStep(sessionRef, step): void — appends a completion block to the session document
logToolCall(sessionRef, tool, args, result): void — logs tool invocations as sub-blocks
A Seed query block (/_logs) that shows recent agent activity across all agents
Distribution
Open-source npm package, documented in the Agents project
Package as part of the Seed Agent SDK (#8)
Blog post: "How to Know What Your Agents Are Doing — Agent Logging for Seed"
Reference implementation: instrument the Product Scout and Gardener agents themselves
Pricing
Free: Open-source core library, local-only logs
Pro ($9/mo): Cross-agent dashboard, log search, retention policies
Enterprise ($49/mo): Centralized log collector, compliance export, audit trails
Competition
LangSmith/LangFuse: LLM observability for prompts/responses, not agent session lifecycle
AgentOps: Agent monitoring, but not Seed-native, no content-addressed storage
Custom code (status quo): Every agent reimplements logging, no standard format
Seed activity feed: Shows events, but not structured by session/completion
Confidence
8/10 — The formal model already exists in the Agents document. The need is immediate (4+ agents operating today with no unified logging). Low implementation risk (thin wrapper around Seed document creation API). Every agent in the ecosystem benefits.
First Experiment
Instrument the Product Scout agent with @shm/agent-logger during this backlog update. Verify the log document appears at /_logs/product-scout/session-timestamp with structured blocks. Show to other agent operators.
---
5. LLM Wiki: Self-Maintaining Knowledge Base for Seed Spaces
Problem
Seed spaces accumulate documents over months but knowledge stays fragmented. No layer connects them.
Evidence: LLM Wiki project — 3,000-word spec.
Users
Seed users with 50+ accumulated documents
Teams using Seed for collaborative knowledge management
Solution
An LLM-powered background agent that maintains a persistent wiki at /_wiki/.
MVP
A TypeScript background process that reads documents, sends to LLM, creates wiki pages.
Confidence
8/10 — 3,000-word spec ready.
---
6. Paid Content Engine for Seed Sites
Problem
Site owners on Seed want to sell access to private content with no way to do it.
Evidence: Paid Content project.
Users
Seed site owners who want to monetize content
Independent creators publishing courses or premium research
Solution
Document-level restriction metadata + Read Capability grants + Stripe payment flow.
Confidence
6/10 — High complexity but also high strategic value.
---
7. Forum-Style Query Block for Community Sites
Problem
Seed sites lack a forum/discussion surface. Users paste Seed links into Discord.
Users
Seed site owners wanting community discussion on their site
Solution
Enhanced query block showing documents + latest comments, with inline Reply.
Confidence
7/10 — Direct user pain, low build cost.
---
8. Seed Agent SDK / Agent Marketplace
Problem
Each agent requires custom infrastructure, charters, and tool integration.
Solution
TypeScript SDK + CLI for building Seed-native agents.
Confidence
7/10 — Clear internal need.
---
9. Proof-of-Context: AI-Resistant Contribution Validation
Problem
AI patches compile but contributors can't answer basic questions.
Solution
Service generating comprehension questions from PR diffs.
Confidence
6/10 — LLM quality dependency.
---
10. Trust Graph Interactive Block
Problem
Graduated trust is abstract — maintainers need to _see_ the graph.
Solution
Embeddable Seed document block rendering force-directed trust graphs.
Confidence
7/10 — Straightforward, high narrative value.
---
11. "Remodeling the Web" Learning Curriculum
Problem
8+ web remodeling documents with no structured learning path.
Solution
Structured curriculum with completion badge.
Confidence
6/10 — Low cost, indirect monetization.
---
12. Seed Document Export & Portability Suite
Problem
Users report unusable export format. Lock-in perception blocks adoption.
Solution
CLI and desktop export to Markdown, ZIP, PDF, JSON-LD.
Confidence
8/10 — Direct user pain, low risk.
---
13. Multi-Agent Coordination Protocol
Problem
4+ agents operating with no coordination — risk of conflicts and redundant work.
Solution
Document-level lease system + activity broadcast.
Confidence
7/10 — Growing need.
---
14. Seed Site Analytics & Engagement Dashboard
Problem
No insight into site engagement. Seed perceived as static blogging software.
Solution
Privacy-respecting dashboard from existing activity feed data.
Confidence
7/10 — Clear demand, low risk.
---
15. State Machine Visualizer & Inspector
Problem
State machines are "hard to establish" — debugging is painful without visual tooling.
Solution
Interactive XState v5 inspector with real-time state display and time-travel.
Confidence
6/10 — Niche but high-value.
---
16. Agent State Trace Protocol & Dashboard
Problem
"State machines to visualize agents" has no implementation for running agents.
Solution
Lightweight event format + real-time observability dashboard.
Confidence
7/10 — Formal model exists, achievable in a week.
---
17. Agent Invariant Validator
Problem
25 formal invariants defined for agents — no verification tool exists.
Solution
CLI checking agent traces against formal invariants.
Confidence
8/10 — Invariants already peer-reviewed.
---
18. Linear Task Expander CLI (@shm/linear-agent)
Problem
Step 2 of the vibe coding pipeline (expanding issues into codebase-aware specs) is the missing link. Devin case study proves end-to-end viability.
Solution
CLI expanding Linear issues into structured task specifications.
Confidence
9/10 — Devin validation, explicit gap.
---
19. Seed Media Galleries & Visual Asset Search
Problem
No way to find images across a Seed site. User requested a "media view."
Solution
Query block showing all image blocks in a responsive grid.
Confidence
7/10 — Direct user request.
---
20. Vibe Code Dev Environment (seed-dev-env)
Problem
"Creating a Server, running a new branch, and building takes 80% of my Vibe Coding time."
Solution
CLI handling entire dev environment bootstrap in one command.
Confidence
8/10 — Pain quantified.
---
21. Seed Protocol Analyzer & Debugger
Problem
Developers can't inspect the protocol in real-time.
Solution
DevTools-like panel for blob stream, verification, and inspection.
Confidence
7/10 — Direct developer request.
---
22. Seed In-App Notification Service
Problem
Users discover activity via Discord. "This is so tiring!"
Solution
In-app notification badge + email digest from activity feed.
Confidence
8/10 — Direct pain, existing data.
---
23. Seed Key Recovery Service
Problem
"High risk for Users with local keys to lose them."
Solution
Shamir Secret Sharing social recovery + Seed escrow.
Confidence
7/10 — Documented product issue.
---
Rankings Summary
| # | Opportunity | Confidence | Difficulty | Seed Fit | Asymmetric Upside |
|---|-------------|------------|------------|----------|-------------------|
| 1 | 🏆 Graduated Trust PR Scoring | 9/10 | 7/10 | 10/10 | Yes — Devin case study validates urgency |
| 2 | Seed Commenting Widget (NEW) | 7/10 | 5/10 | 9/10 | Yes — packaging existing infra for web |
| 3 | Graduated Trust Course (NEW) | 7/10 | 3/10 | 8/10 | Yes — content exists, low cost to test |
| 4 | Agent Session Logger (NEW) | 8/10 | 3/10 | 10/10 | Yes — formal model exists, immediate need |
| 5 | LLM Wiki | 8/10 | 6/10 | 10/10 | Yes — 3,000-word spec ready |
| 6 | Paid Content Engine | 6/10 | 8/10 | 9/10 | Yes — ecosystem monetization |
| 7 | Forum-Style Query Block | 7/10 | 4/10 | 9/10 | Yes — removes Discord dependency |
| 8 | Seed Agent SDK | 7/10 | 6/10 | 10/10 | Yes — enables ecosystem |
| 9 | Proof-of-Context Validation | 6/10 | 5/10 | 8/10 | Moderate |
| 10 | Trust Graph Block | 7/10 | 4/10 | 9/10 | Yes — piggybacks on #1 |
| 11 | Remodeling the Web Curriculum | 6/10 | 2/10 | 9/10 | Yes — low cost, high narrative impact |
| 12 | Document Export & Portability | 8/10 | 4/10 | 8/10 | Yes — removes adoption barrier |
| 13 | Multi-Agent Coordination Protocol | 7/10 | 5/10 | 10/10 | Moderate |
| 14 | Site Analytics & Engagement Dashboard | 7/10 | 5/10 | 9/10 | Yes — existing data, no infra cost |
| 15 | State Machine Visualizer & Inspector | 6/10 | 4/10 | 7/10 | Moderate |
| 16 | Agent State Trace Protocol & Dashboard | 7/10 | 5/10 | 9/10 | Yes — formal model exists |
| 17 | Agent Invariant Validator | 8/10 | 3/10 | 8/10 | Yes — 25 invariants already defined |
| 18 | Linear Task Expander CLI | 9/10 | 4/10 | 7/10 | Yes — Devin case study validates pipeline |
| 19 | Seed Media Galleries & Asset Search | 7/10 | 3/10 | 8/10 | Yes — user-requested, low cost |
| 20 | Vibe Code Dev Environment | 8/10 | 3/10 | 9/10 | Yes — 80% setup pain, trivial fix |
| 21 | Seed Protocol Analyzer | 7/10 | 4/10 | 8/10 | Moderate |
| 22 | Seed In-App Notification Service | 8/10 | 4/10 | 9/10 | Yes — removes Discord dependency |
| 23 | Seed Key Recovery Service | 7/10 | 4/10 | 8/10 | Yes — removes critical adoption barrier |Do you like what you are reading? Subscribe to receive updates.
Unsubscribe anytime