> For the complete documentation index, see [llms.txt](https://docs.builtbydao.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.builtbydao.com/getting-started/what-is-built-by-dao.md).

# The Organization

**How Built By DAO is structured—legal entity, divisions, operational units, and physical infrastructure.**

***

{% hint style="info" %}

## 🏛️ Organization Overview

**🎯 Structure:** A legally-recognized DAO with physical infrastructure, organized into divisions and coordinated through on-chain governance.
{% endhint %}

|       📜 Legal      |         🏢 Divisions        |           👥 Teams          |     🏭 Physical     |
| :-----------------: | :-------------------------: | :-------------------------: | :-----------------: |
| **Wyoming DAO LLC** | **9 operational divisions** | **Guilds + Working Groups** | **Foundry network** |

***

## Legal Structure

Built By DAO is a **Wyoming DAO LLC**—one of the first jurisdictions to provide clear legal status for blockchain-governed organizations.

| Aspect               | Details                                                          |
| -------------------- | ---------------------------------------------------------------- |
| 📜 **Entity type**   | DAO Limited Liability Company                                    |
| 🏛️ **Jurisdiction** | Wyoming, USA                                                     |
| 🔐 **Governance**    | [On-chain voting](/governance/voting.md) per operating agreement |
| 🛡️ **Liability**    | Member liability limited per LLC structure                       |
| 📊 **Ownership**     | [EQTBLT](/token-economy/eqtblt.md) token holders                 |

This provides:

* Legal standing to hold property, sign contracts, and operate businesses
* Regulatory clarity for investors and partners
* Member protection through LLC structure
* On-chain governance with legal force

***

## The Urban Array Pairing

Built By DAO does not operate alone. It is paired **co-equally** with **Urban Array, a 501(c)(3) nonprofit**—the federal- and philanthropy-facing adapter for the work.

| Entity                                   | Role                                                                                                                                                                                                               |
| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| 🏛️ **Built By DAO** (Wyoming DAO LLC)   | The member-owned operating company. Builds, develops, holds the property and the earned-equity economy, and governs on-chain.                                                                                      |
| 🤝 **Urban Array** (501(c)(3) nonprofit) | The mission-facing adapter. Opens the non-dilutive funding surface—public grants, housing and workforce programs, philanthropic capital—and runs the charitable workforce-training and community-development side. |

**Why two entities:** the capital that makes deeply community-owned development possible—HUD and state housing funds, workforce grants, foundations—flows to mission-driven nonprofits, not to LLCs. Urban Array is the door to that capital; Built By DAO is the engine that turns it into owned homes, jobs, and neighborhood infrastructure. The two are co-equal partners, not parent-and-subsidiary.

```mermaid
flowchart TB
    BBD["🏛️ Built By DAO<br/>Wyoming DAO LLC<br/>member-owned operating co"]
    UA["🤝 Urban Array<br/>501·c·3 nonprofit<br/>mission-facing adapter"]
    BBD -- "co-equal partners" --- UA
    BBD --> Build["Builds · develops · holds property<br/>governs on-chain"]
    BBD --> Equity["Runs the earned-equity economy<br/>EQTBLT"]
    UA --> Grants["Opens non-dilutive funding<br/>grants · housing · philanthropy"]
    UA --> Workforce["Charitable workforce training<br/>community development"]
```

{% hint style="info" %}
At the Urban Array / grant-facing layer, the work is described in plain community-development terms—workforce training, housing, material reuse—not token mechanics. The earned-equity economy ([EQTBLT](/token-economy/eqtblt.md)) lives on the Built By DAO side.
{% endhint %}

{% hint style="warning" %}
The exact structure of the pairing and any flow of funds between the two entities is being finalized with counsel (nonprofit private-benefit, UBIT, and related rules). Treat the structural description here as the intended model, not final legal terms.
{% endhint %}

***

{% tabs %}
{% tab title="🏢 Divisions" %}

## 🏢 Operational Divisions

Built By DAO organizes work into nine divisions, each led by a chief officer and staffed by member roles:

| Division                                                                      | Focus                                                 |
| ----------------------------------------------------------------------------- | ----------------------------------------------------- |
| 🏗️ [**Construction & Property**](/divisions-and-roles/construction.md)       | Building, renovation, trades, and property operations |
| ⚙️ [**Engineering**](/divisions-and-roles/engineering.md)                     | Professional engineering and technical design         |
| 💻 [**Technology**](/divisions-and-roles/technology.md)                       | Smart contracts, platform, and security               |
| 📊 [**Analytics**](/divisions-and-roles/analytics.md)                         | Data, reporting, and performance measurement          |
| 🏛️ [**Governance**](/divisions-and-roles/governance.md)                      | Proposals, voting operations, and policy              |
| 💰 [**Finance**](/divisions-and-roles/finance.md)                             | Treasury operations, accounting, and compliance       |
| 👥 [**Membership & Community**](/divisions-and-roles/membership-community.md) | Onboarding, education, and member services            |
| 🤝 [**Volunteer & Community**](/divisions-and-roles/volunteer.md)             | Volunteer programs and community outreach             |
| 🏛️ [**DAO Leadership**](/divisions-and-roles/leadership.md)                  | Cross-division coordination and strategy              |

Materials recovery runs through the [circular economy program](/sustainability/circular.md) at [The Depot](/the-foundry/foundry/depot.md). [Member housing](/onboarding/member-housing.md) and [rent-to-equity](/equity-and-membership/how-it-works.md) operations run through the Construction & Property division.

{% content-ref url="/pages/evcOSKNCWgU7G60NSFC5" %}
[All Divisions](/divisions-and-roles/divisions.md)
{% endcontent-ref %}
{% endtab %}

{% tab title="👥 Guilds" %}

## 👥 Guild System

Guilds are skill-based communities that cross division boundaries.

***

### Purpose

| Function             | Description                                                      |
| -------------------- | ---------------------------------------------------------------- |
| 🎓 **Training**      | Skill development pathways                                       |
| 📜 **Certification** | [Merit NFTs](/token-economy/nfts.md) for demonstrated competency |
| 👥 **Mentorship**    | Connect experienced members with learners                        |
| 🔨 **Task matching** | Route [work](/contributors/tasks.md) to qualified members        |

***

### Guild Types

| Category                                                         | Examples                               |
| ---------------------------------------------------------------- | -------------------------------------- |
| 🔨 [**Trades**](/divisions-and-roles/construction/trades.md)     | Carpentry, Electrical, Plumbing, HVAC  |
| 💻 [**Technical**](/divisions-and-roles/technology.md)           | Development, Design, DevOps            |
| 📋 [**Operations**](/operations/operations.md)                   | Project Management, Logistics, Finance |
| 👥 [**Community**](/divisions-and-roles/membership-community.md) | Facilitation, Outreach, Education      |

***

### Guild Roles

| Role                    | Capabilities                         |
| ----------------------- | ------------------------------------ |
| 👤 **Member**           | Basic guild access, task eligibility |
| 🎓 **Welcomer**         | Onboard new guild members            |
| 🔍 **Quality Reviewer** | Review and approve work              |
| 📚 **Archivist**        | Maintain guild documentation         |
| 🔎 **Recruiter**        | Member recruitment                   |
| 👔 **Guild Lead**       | Full guild administration            |

***

### Merit System

Guilds issue **Merit NFTs** for skill recognition:

| Merit Level | Meaning          |
| ----------- | ---------------- |
| Level 1     | Basic competency |
| Level 2     | Proficient       |
| Level 3     | Advanced         |
| Level 4     | Expert           |
| Level 5     | Master           |

Merit is separate from membership rank—you can be a high-rank member with beginner guild skills, or vice versa.
{% endtab %}

{% tab title="🏭 The Foundry" %}

## 🏭 Foundry Infrastructure

The Foundry is Built By DAO's physical operational network—where real-world work happens.

***

### Seven Zones

| Zone                                                    | Function            | Activities                             |
| ------------------------------------------------------- | ------------------- | -------------------------------------- |
| 🌳 [**The Yard**](/the-foundry/foundry/yard.md)         | Material intake     | Receiving, sorting, initial processing |
| 📦 [**The Depot**](/the-foundry/foundry/depot.md)       | Storage & logistics | Inventory, warehousing, distribution   |
| 🔧 [**The Workshop**](/the-foundry/foundry/workshop.md) | Fabrication         | Construction, repair, training         |
| 🔥 [**The Forge**](/the-foundry/foundry/forge.md)       | Heavy manufacturing | Metalwork, advanced fabrication        |
| 🛤️ [**The Station**](/the-foundry/foundry/station.md)  | Operations          | Command, coordination, dispatch        |
| 🏛️ [**The Hall**](/the-foundry/foundry/hall.md)        | Community           | Gathering, events, education           |
| 🛏️ [**The Loft**](/the-foundry/foundry/loft.md)        | Administration      | Offices, planning, leadership          |

***

### The Circular Model

```mermaid
flowchart LR
    Decon["Deconstruction"] --> Recovery["Material<br/>Recovery"]
    Recovery --> Processing["Processing"]
    Processing --> Storage["Storage"]
    Storage --> Members["Members"]
    Members --> Training["Training"]
    Training --> Fabrication["Fabrication"]
    Fabrication --> NewBuild["New<br/>Construction"]
    NewBuild --> Decon
```

Materials flow in from deconstruction projects. Members learn skills while processing them. Skilled members build new infrastructure. Repeat.

***

### Foundry Access

| Member Status                                       | Access Level                          |
| --------------------------------------------------- | ------------------------------------- |
| 🌱 [Seeker](/membership/ranks/seeker.md)            | Supervised access, training zones     |
| 🌿 [Apprentice](/membership/ranks/apprentice.md)    | Workshop access with mentor           |
| 🔧 [Contributor+](/membership/ranks/contributor.md) | Full zone access based on guild merit |
| 👔 [Leadership](/membership/ranks.md)               | Zone management capabilities          |

See [Foundry Architecture](/the-foundry/foundry.md) for complete documentation.
{% endtab %}

{% tab title="⚙️ Working Groups" %}

## ⚙️ Working Groups

Working groups are operational teams focused on specific deliverables.

***

### How They Work

| Aspect             | Description                                                     |
| ------------------ | --------------------------------------------------------------- |
| 🎯 **Scope**       | Defined objectives and deliverables                             |
| 👔 **Leadership**  | Led by [Crew Lead](/membership/ranks/crew-lead.md) (Level 4+)   |
| 👥 **Composition** | Mixed [ranks](/membership/ranks.md), relevant guild skills      |
| 📋 **Tasks**       | Assigned through [project management](/operations/pm-system.md) |

***

### Group Types

| Type               | Examples                                  |
| ------------------ | ----------------------------------------- |
| 🏗️ **Project**    | Construction team, renovation crew        |
| ⚙️ **Operational** | Material processing, property maintenance |
| 📋 **Functional**  | Finance, communications, governance       |
| 🎯 **Initiative**  | New program development                   |

***

### Member Relationship

A single member might be:

| Structure            | Position                  |
| -------------------- | ------------------------- |
| 🎖️ **Rank**         | Contributor (Level 2)     |
| 🎨 **Guild**         | Carpentry (Merit Level 2) |
| 👥 **Working Group** | Depot Material Processing |
| 🏢 **Division**      | Materials                 |

Working group assignments change based on projects. Rank and guild membership are persistent.
{% endtab %}

{% tab title="🔗 How It Connects" %}

## 🔗 Organizational Integration

How the pieces work together:

***

### Task Flow

```mermaid
flowchart LR
    Gov["Governance"] --> Div["Division"]
    Div --> WG["Working<br/>Group"]
    WG --> Member["Member"]
    Member --> Task["Task"]
    Task --> EQTBLT["💎 EQTBLT"]
```

1. [Governance](/governance/governance.md) approves budgets and priorities
2. [Divisions](/divisions-and-roles/divisions.md) plan projects and allocate resources
3. [Working groups](/operations/working-groups.md) organize delivery
4. Members complete [tasks](/contributors/tasks.md)
5. [EQTBLT](/token-economy/eqtblt.md) mints automatically

***

### Coordination Mechanisms

| Mechanism                                             | Function                                 |
| ----------------------------------------------------- | ---------------------------------------- |
| 🗳️ [**Governance**](/governance/governance.md)       | Strategic direction, resource allocation |
| 🏢 [**Divisions**](/divisions-and-roles/divisions.md) | Operational planning                     |
| 👔 [**Leadership ranks**](/membership/ranks.md)       | Day-to-day coordination                  |
| 📋 [**Platform**](/developers/platform.md)            | Task management, tracking                |
| 💎 [**EQTBLT**](/token-economy/eqtblt.md)             | Incentive alignment                      |

***

### Information Flow

| Level             | Visibility                                                                                                                   |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| 🌐 **Public**     | [Governance proposals](/governance/proposals.md), [treasury](/governance/treasury.md), [contracts](/developers/contracts.md) |
| 👥 **Members**    | Projects, [tasks](/contributors/tasks.md), working groups                                                                    |
| 🏢 **Division**   | Detailed planning, budgets                                                                                                   |
| 👔 **Leadership** | Sensitive operations                                                                                                         |

Transparency is default. Restriction requires justification.
{% endtab %}
{% endtabs %}

***

<details>

<summary>📊 Organization Numbers</summary>

| Metric                                             | Count |
| -------------------------------------------------- | :---: |
| [**Divisions**](/divisions-and-roles/divisions.md) |   9   |
| [**Guild categories**](/membership/guilds.md)      |   4   |
| [**Foundry zones**](/the-foundry/foundry.md)       |   7   |
| [**Membership ranks**](/membership/ranks.md)       |   14  |
| [**Smart contracts**](/developers/contracts.md)    |   20  |
| **Platform tables**                                |  180  |

</details>

***

<details>

<summary>📜 Legal Documents</summary>

| Document                  | Purpose                     |
| ------------------------- | --------------------------- |
| **Operating Agreement**   | DAO governance rules        |
| **Member Agreement**      | Rights and responsibilities |
| **Lease Templates**       | Equity lease terms          |
| **Investment Agreements** | Investor terms by tier      |

Contact <legal@builtbydao.com> for document requests.

</details>

***

{% hint style="success" %}

## 🔗 Organization Deep Dives

{% endhint %}

| Topic              | Documentation                                         |
| ------------------ | ----------------------------------------------------- |
| 🏭 **Foundry**     | [Physical Infrastructure](/the-foundry/foundry.md)    |
| 🏢 **Divisions**   | [Division Details](/divisions-and-roles/divisions.md) |
| 👥 **Membership**  | [Rank System](/membership/membership.md)              |
| 🗳️ **Governance** | [How Decisions Are Made](/governance/governance.md)   |

***

## 🔗 Related Pages

{% content-ref url="/pages/S2jVGkVrgHonprR3uwiR" %}
[The Thesis](/getting-started/thesis.md)
{% endcontent-ref %}

{% content-ref url="/pages/K4LGhhlSHD4Pg68pR1BE" %}
[Overview](/the-foundry/foundry.md)
{% endcontent-ref %}

{% content-ref url="/pages/2CpsPXS2onSy2cA8plzX" %}
[Overview](/membership/membership.md)
{% endcontent-ref %}

{% content-ref url="/pages/SS8wIERv7K8t3TYmBbhQ" %}
[Overview](/governance/governance.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.builtbydao.com/getting-started/what-is-built-by-dao.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.