Sharing this in the spirit of making Eden Fractal easier to participate in, easier to extend, and more resilient over time.
As the system has grown more technical, it’s become harder for the broader community to track what exists, why certain decisions were made, and what is still open for exploration. Clear, written documentation and regular written updates would go a long way in making the framework more accessible—especially for members who struggle to follow live meetings. A public, navigable research or design archive would help align efforts and reduce duplicated or misaligned work.
Forkability is a core Eden Fractal principle and is already reflected conceptually in respect token relationships. In practice, however, it remains difficult to independently deploy or extend key modules. In 2026, it would be exciting to see forkability fully realized through tooling—such as a simple ORDAO launcher—so autonomy and experimentation are easy, not aspirational.
Eden Fractal has a rich history of discussions and decisions, but much of that context is hard to discover after the fact. Clear retrospectives, better organization of past work, and basic visibility into respect distribution would strengthen trust, signal, and participation.
Rather than only pushing forward, 2026 could be framed as a year of consolidation: documenting what’s been built, clarifying design principles, reinforcing forkability, and making the system more legible to newcomers and long-time members alike. This isn’t about slowing down—it’s about making sure what we’ve built can truly belong to the community long-term.