Content Roadmap

Maintained by the Strategist agent. Updated: 2026-07-24

Published

Writing

Graduated Trust: A Web-of-Trust Proposal for Open Source in the AI Era - Updated 2026-07-24. The signature piece. Fully developed.

Remodeling the web - Architectural critique that graduated trust extends.

Vibe code like a PRO - Problem context for slop PRs.

Queue: Next to Write

Priority 1 (High leverage, low effort)

Graduated Trust: Protocol Spec v0.1 - Formal RFC extending Seed contacts with scoped attestations. Turns the article into something implementable. Expected impact: high (makes Seed the trust substrate). Effort: medium.

Talk Abstract: Trust in the Age of AI Slop - Conference submission for late 2026. Content is 70% written (the article). Effort: low. Expected impact: high (positions author, recruits collaborators).

Priority 2 (Medium leverage)

The Graph is the Gate: How Social Distance Replaces CAPTCHA for Code - Shorter, punchier version of the graduated trust thesis for a developer audience (maybe a blog post or newsletter). Distills the core mechanic into 500 words.

From Slop to Signal: A Maintainers Guide to the New Trust Landscape - Practical guide for maintainers dealing with AI-generated contributions, framing the graduated trust approach as one tool in a broader toolkit.

Priority 3 (Long-term authority building)

Beyond OSS: Web of Trust for Science, Journalism, and Moderation - Synthetic piece connecting the graduated trust model to other domains where AI fabrication is a threat. Positions the idea as platform-level, not niche.

Proof-of-Context: Can We Ask AI-Generated Code Questions the AI Cannot Answer? - Deep dive on the most novel mechanism in the graduated trust proposal. Requires prototyping to validate claims.

Evergreen Candidates (Reusable, Perpetual Value)

Seed Trust Architecture Documentation - Documentation explaining how Seed's contacts, capabilities, and documents compose into a trust substrate. Lives on the Seed site. Updates as protocol evolves.

Graduated Trust FAQ / Explainer - Short, opinionated answers to common objections (Sybil resistance, privacy, centralized alternatives). Lives alongside the protocol spec.

Content Principles

Prefer one strong piece over three mediocre ones

Every piece should link to the signature idea

Every piece should advance a specific argument, not summarize

Avoid generic takes on AI or open source - specific mechanisms only