Purpose

This document outlines why the current ORDAO / OREC documentation does not yet meet the needs of a decentralized, forkable DAO, and proposes clear documentation conventions required for Eden Fractal to operate autonomously over time.

This is not an evaluation of effort or intent. It is an evaluation of whether the documentation enables independent understanding, deployment, extension, and forking by parties other than the original author.

Summary Assessment

The existing documentation functions primarily as explanatory or reflective writing about the system rather than operational documentation for the system.

While it contains insight, it does not yet allow:

• a new contributor to deploy ORDAO independently,
• a third party to audit or reason about system invariants,
• or a subgroup to fork the protocol without relying on undocumented context.

As a result, critical knowledge remains centralized, which limits DAO autonomy.

What Is Currently Missing

1. Entry Point & Navigation

• No “Start Here” or documentation index
• No clear mapping of docs to audience (user / contributor / auditor)
• No table of contents or doc hierarchy

2. Deployment Documentation

• No step-by-step guide for deploying a new ORDAO / OREC instance
• No list of required tools, versions, or environment assumptions