OpenHaven: Stakeholder Brief

Executive Summary

OpenHaven is a community-led, data-driven convergence navigator for the peer-to-peer (P2P) and decentralized protocol landscape that makes it visible, navigable, and directly actionable — including for AI-assisted development workflows. It replaces the current single-page openhaven.net with a live, data-driven website that serves as both a navigable guide to open protocols and a collective voice for the people building and using them.

Born from the Collaborative Technology Alliance (CTA) and a growing coalition of researchers, builders, and community leaders, OpenHaven translates complex protocol research into something legible, actionable, and shareable. OpenHaven's mission is making the open protocol landscape interoperable and interact-able — navigable by the people who need it — informed by the understanding that technical convergence depends on social convergence. Not just mapping the technology, but building the tent — giving the movement a collective voice, a shared home, and tools — including machine-readable context and prompt generation for AI-assisted workflows — that lower the barrier to understanding and adoption.

OpenHaven serves three interconnected audiences: community leaders seeking tools to solve real coordination problems, builders and researchers seeking convergence and network effects across fragmented efforts, and coalition organizations (e.g. CTA, DWeb) needing a shared evidence base to weave their convergence work together. For all three, OpenHaven is a hub they are proud to share — because it demonstrates tangible progress toward foundational infrastructure for humanity's coordination challenges.

Core Vision

Problem Statement

The P2P and decentralized protocol landscape is deeply fragmented. Dozens of protocols, platforms, and applications exist across a spectrum from fully P2P to federated to centralized — each solving overlapping problems, developed largely in isolation.

• For community leaders and non-technical users: The landscape is illegible. They have real needs — private communication, mutual aid coordination, censorship-resistant journalism — but no trusted, outcome-oriented guide to match needs with tools.
• For builders and researchers: The pain is fragmentation. Talented teams build impressive technology in silos, struggling to achieve network effects. Everyone feels the drag — if these projects were more unified, the collective impact would be exponentially greater.
• For coalition organizations like CTA: There is no shared mechanism to map "what code each person is bringing to the table" so convergence efforts can be woven together effectively. OpenHaven can serve as that mechanism.

Problem Impact

The stakes extend well beyond the technology community. The convergence of environmental, political, and social coordination failures demands foundational infrastructure — systems that enable humanity to organize, communicate, and govern at scale without dependence on centralized systems vulnerable to capture, censorship, or failure. Communities facing authoritarian pressure, journalists protecting sources, neighbors coordinating disaster response — they need this to work, and it needs to be findable, understandable, and action-enabling.

Why Existing Solutions Fall Short

Several mapping efforts exist — Christina Bowen's DWeb Kumu map, Josh Field's Wise Tech Capabilities Matrix, Brandon Norgaard's convergence spreadsheet — but each addresses only a slice:

• Existing maps are researcher-facing, not community-leader-facing — they catalog technology but don't answer "what should I use?"
• Nothing is outcome-oriented — current tools organize by technology category, not by human need.
• There is no social convergence layer — existing resources are static documents, not living hubs.
• Nothing is built for AI-assisted workflows — no resource provides machine-readable context, chatbot exploration, or prompt-ready recommendations.
• The movement lacks a collective voice — contributors across DWeb, NAO, RegenOS, and CTA have no shared home.

Proposed Solution

OpenHaven (openhaven.net) becomes a live, data-driven convergence navigator comprising:

1. Open Protocol Navigator — An interactive, data-driven tool backed by a convergence matrix of 69+ protocol entries with 40+ standardized attributes each. Users navigate through a Use Cases → Affordances → Tools architecture: enter through human needs, understand the capabilities required, and discover the protocols that provide them. Governance model and capture risk are surfaced alongside technical capabilities for every entry.
2. Verified Data Infrastructure — An open-source relational data platform as the source of truth. Every entry is expert-verified, contributor-attributed, source-referenced, and carries a last_investigated date.
3. State of Convergence — Editorial content summarizing the landscape and where convergence is emerging, produced collaboratively with CTA, DWeb, and others.
4. Machine-Readable Context & Prompt Generation — V1 ships llms-full.txt for full-context AI ingestion and prompt generation for selected tech stacks, so developers can go from protocol discovery to building in a single session. Future versions add a protocol advisor chatbot, code generation, and AI agent integration.
5. Pro-social Design Integration — Connection to the Pro-social Design application and community, bridging protocol infrastructure with relational and emotional design.
6. Feedback & Contribution Mechanisms — Built in from day one. Entry-level feedback, site-wide suggestions, contributor pathways for new data submissions, and survey mechanisms for qualitative stories.

All data is human-verified before publication. The data quality lifecycle distinguishes claimed from demonstrated capability, with contributor attribution and source references tracked per entry.

Key Differentiators

• Protocol interoperability, informed by social interoperability: OpenHaven maps the technical landscape while grounding it in the understanding that social convergence — community resonance, dialogue, trust — is a precursor to technical convergence. Software serves the social foundation, not the other way around.
• Use Cases → Affordances → Tools navigation: Start from human needs, surface the capabilities required, then map to protocols. Outcome-first, not technology-first.
• Built for AI-assisted workflows: Full machine-readable context (llms-full.txt), prompt export for selected tech stacks, and an architecture designed to evolve toward chatbot exploration and code generation. V1 makes the landscape understandable; future versions make it directly actionable.
• Connector, not platform: OpenHaven points to existing communities and conversations rather than building a competing social layer.
• Evidence-based, not advocacy-based: The Navigator serves all positions in the convergence debate by providing verified data, not pushing an agenda.
• Collective voice: A home the movement is proud to point to — a tangible representation of the work being done for collective betterment.

Ecosystem Context

OpenHaven is embedded in a broader constellation of convergence efforts — funding pipelines, narrative infrastructure, use case definition, community experiments, and open social ecosystem design. These efforts are increasingly finding each other. OpenHaven's role is specific — protocol discovery and navigation — but its value compounds as adjacent efforts mature and as the people driving them use the Navigator as a shared reference point.

Who It's For

OpenHaven serves four audiences, each with a distinct relationship to the protocol landscape:

How We'll Know It's Working

• People are finding what they need — users are entering through use case domains and arriving at relevant, verified protocol lists without prior technical knowledge
• The community is sharing it — coalition members, builders, and contributors are actively sending OpenHaven links to their networks as the canonical reference
• Convergence is becoming visible — the abstraction layer spanning protocols is more legible, and it's clearer which protocols are best positioned for collective coordination
• Feedback is flowing — suggestions, updates, and real stories are coming through the built-in mechanisms ("I found X through OpenHaven and it changed how we coordinate")
• Funding conversations reference it — at least one grant application or funder conversation uses OpenHaven as an evidence base
• Hope is growing — community feedback reflects a stronger sense of cohesion and momentum, with less energy spilled from fragmented effort