Topics (Period 136)

This is a poll to determine priority of topics at the time of period 136 of Eden Fractal. It is part of stage 2 of Synchronous Respect Tree V1 game.

Spread your Respect-weighted votes among topics according to your understanding of what topics are the most important to discuss right now. This will help determine our discussion topics for the upcoming town hall and the following week.

From Dan Singjoy

TP: Eden Fractal Spring Break Proposal

During the first 25 minutes of Eden Town Hall #75, we discussed the draft proposal for a 4-week break from events and received positive feedback from the community. Tadas, Zaal, Rosmari, and Sebastian all expressed support, and we compared the 4-week option with shorter alternatives before forming consensus that 4 weeks makes sense. I'd encourage watching the discussion and Eden Town Hall 74 for more context.

I'm proposing that we approve the 4-week break proposal at this week's event (March 12), following the Eden+Fractal council consensus process. The proposal is that we take a 4-week break from events after the 6th Respect Game on March 26, returning for the second half of Season 12 on April 30. The break provides focused time for infrastructure development, rest, and reflection — and the proposal includes full rationale and details on what will happen during the break.

One thing I realized after our discussion last week is that while we compared the 4-week break with shorter breaks and formed consensus that 4 weeks makes sense, we didn't really discuss whether it might make sense to take a longer break. I'm happy to go with the 4-week break as discussed, but I wanted to share that there are some important infrastructure developments I'm working on that could potentially benefit from more focused time.

I've written up some thoughts on how we might think about using the flexibility clause we discussed — where the council retains the ability to adjust the return date during the break if needed. To be clear, I'm proposing we approve the 4-week break returning April 30th as previously discussed, and I'm sharing these additional thoughts for consideration during the break itself if the council decides it makes sense to extend.

TP: Eden Fractal Community Agreement

Creating a community agreement has been one of our outstanding goals for years, and it's becoming increasingly important as we work toward scaling our processes in the new year. A clear agreement helps set expectations, protect the community, and provide a foundation for scaling — including making it clear that Respect tokens represent community opinions, establishing consent for video recording and content sharing, and defining governance participation expectations.

We've discussed this extensively over the years, including detailed conversations during Eden Fractal events 37 and 38 and in related communities. We now have a legislative consensus process through Eden+Fractal to formally approve such an agreement, which removes a key blocker. I'm working on resources to help us coordinate on this, and this is a great topic for the community to start discussing. The agreement could potentially be stored in Firmament on GitHub as a communally approved document. This is a topic worth discussing at our upcoming town hall as we consider scope, priorities, and next steps.

TP: Eden Fractal Intent Document

Eden Fractal needs its own Intent Document, envisioned as an operating manual for community coordination that clearly defines technical specifications, governance processes, and community expectations. Optimism Fractal's Intent Document provides a strong starting point — it covers Respect Game meeting structure, distribution amounts, the consensus process, council formation, the executive contract, and more, and has been updated multiple times through their community's own consensus process as the community evolved.

As a first step, we can use Optimism Fractal's document as a foundation and then decide what should be tailored to Eden Fractal's unique structure and Epoch 2 operations. The document would be drafted through community collaboration, approved via our consensus process, and include mechanisms for future modifications. This would be a valuable topic to discuss at our upcoming town hall as we consider the scope, structure, and approach.

TP: Eden+Fractal Improvements

Eden+Fractal is our legislative consensus process for choosing delegates, deliberating on decisions, and making community decisions. The process was first introduced around Eden Fractal's 20th event back in 2022, and we've been practicing it consistently for the past six months during Epoch 2. When we started adopting it for Epoch 2, I created an implementation plan to guide how we'd operate it, informed significantly by discussions with Tadas and the community back in August and September 2025.

It's been working well overall, but there are clear areas for improvement. Delegate attendance has been a challenge, and our current tooling is basically an article and a Google spreadsheet — there's no dedicated app, and it requires a lot of manual coordination to manage effectively. There are also aspects of the original implementation plan that we haven't fully implemented yet.

Recent discussions about Firmament and Respect Trees may also relate to potential improvements. At Eden Town Hall 75, we had an extended discussion about this that may be worth revisiting and further examining. This would be a good time to take stock of how the process is serving the community and consider what refinements would be most valuable heading into the second half of the season.

TP: Exploring Matrix

I've been learning about Matrix over the past weeks and wanted to share some of what I've found. Matrix is an open-source, decentralized communication protocol that can do similar things to Telegram or Discord, but it aligns more closely with Eden Fractal's values around openness, decentralization, and composability — meaning we can build with it and on top of it.

A few things that stand out: Matrix has a spec-driven development process with a governance and proposal system on GitHub that could serve as useful inspiration as we start using spec-driven development ourselves. They also have both a federated version and are building Matrix P2P, a non-federated peer-to-peer version that shares some of the same goals that Dan Larimer's team had with Clarion OS. The project has been in active development for over 10 years and continues to evolve.

I think there are potential opportunities for us to use their tools, learn from their processes, and possibly collaborate. I'd like to share what I've learned and have an interactive conversation about it. You can learn more about Matrix in this video showing their latest updates.

TP: Recognizing Prior Contributions to Eden Fractal

*Author: Dan *https://t.me/edenfractal/5562/6283

Eden Fractal did not distribute Respect tokens between approximately events 63 and 120, which represents roughly a third to 40% of our total 135 events. This is a significant gap given that recognizing contributions is one of our core functions.

There are two distinct periods to consider. For events 63–83, Respect Games were played and consensus results were posted on EOS, but tokens were never distributed due to issues with the Eden Fractal MSIG. Records exist in video timestamps, consensus results posts, and onchain transaction history. For events 83–120, no Respect Games were played, but many people contributed significantly during this pivotal time for fractal governance development and received no Eden Fractal Respect.

Currently, the ORDAO account is controlled primarily by participants from Eden Fractal's first year and a half, with no recognition for contributions from approximately year 2 through year 3. One idea I'm exploring is using an AI agent to review the un-executed proposals on EOS, videos from events with no respect games, and generate attendance records to help inform retroactive Respect distribution proposals. I have some draft notes about this and am working on a more detailed article.

While discussing contributions to Eden Fractal directly, we could also begin considering higher-order fractal considerations — how Eden Fractal might recognize contributions from communities like Genesis Fractal, Eden on EOS, Optimism Fractal, ZAO Fractal, and others who have supported our mission. The priority should be recognizing direct contributions to Eden Fractal first, and then considering how to best recognize contributions from other fractals.

I'd welcome any thoughts or feedback from delegates and community members on the best approach.