# The Organization **How Built By DAO is structuredβ€”legal entity, divisions, operational units, and physical infrastructure.** *** {% hint style="info" %} ### πŸ›οΈ Organization Overview {% endhint %} | πŸ“œ Legal | 🏒 Divisions | πŸ‘₯ Teams | 🏭 Physical | | :-----------------: | :-------------------------: | :-------------------------: | :-----------------: | | **Wyoming DAO LLC** | **5 operational divisions** | **Guilds + Working Groups** | **Foundry network** | {% hint style="info" %} **🎯 Structure:** A legally-recognized DAO with physical infrastructure, organized into divisions and coordinated through on-chain governance. {% endhint %} *** ## 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 *** {% tabs %} {% tab title="🏒 Divisions" %} ### 🏒 Operational Divisions Built By DAO organizes work into five divisions: *** #### πŸ”¨ Construction Division | Function | Description | | ------------------------------------------------------------ | ---------------------------------------- | | πŸ—οΈ **Building** | New construction and renovation projects | | πŸ”§ **Maintenance** | Property upkeep and repairs | | πŸ“‹ [**Trades**](/divisions-and-roles/construction/trades.md) | Carpentry, electrical, plumbing, HVAC | | πŸŽ“ [**Training**](/contributors/training.md) | Skills development programs | *** #### ♻️ Materials Division | Function | Description | | ---------------------- | ------------------------------------------------------------------------ | | 🏚️ **Deconstruction** | Careful disassembly for [material recovery](/sustainability/circular.md) | | πŸ“¦ **Processing** | Sorting, cleaning, quality assessment | | πŸͺ **Inventory** | Storage and cataloging at [The Depot](/the-foundry/foundry/depot.md) | | πŸ”„ **Distribution** | Material allocation to projects | *** #### 🏠 Properties Division | Function | Description | | ------------------ | ----------------------------------------------------------------------------------------------------------------------- | | πŸ”‘ **Management** | Residential and commercial operations | | πŸ’° **Finance** | [Rent collection](/equity-and-membership/rent-payments.md), [equity conversion](/equity-and-membership/how-it-works.md) | | πŸ‘₯ **Residents** | [Member housing](/onboarding/member-housing.md) services | | πŸ“Š **Development** | Property acquisition and planning | *** #### πŸ’» Technology Division | Function | Description | | ----------------- | ------------------------------------------------------------ | | ⛓️ **Blockchain** | [Smart contract](/developers/contracts.md) development | | πŸ–₯️ **Platform** | [Web application](/developers/platform.md) and tools | | πŸ“Š **Data** | [Analytics](/divisions-and-roles/analytics.md) and reporting | | πŸ” **Security** | System protection and [auditing](/developers/security.md) | *** #### πŸ‘₯ Community Division | Function | Description | | ---------------------------------------------- | ------------------------------------------------------------- | | πŸ‘‹ [**Onboarding**](/onboarding/onboarding.md) | New member integration | | πŸŽ“ **Education** | [Training](/contributors/training.md) and development | | 🀝 **Outreach** | External relations | | πŸ›οΈ **Governance** | [Proposal](/governance/proposals.md) support and coordination | | {% 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 ``` Deconstruction β†’ Material Recovery β†’ Processing β†’ Storage ↓ New Construction ← Fabrication ← Training ← Members ``` 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 ``` Governance β†’ Division β†’ Working Group β†’ Member β†’ Task β†’ 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 %} ***
πŸ“Š Organization Numbers | Metric | Count | | -------------------------------------------------- | :---: | | [**Divisions**](/divisions-and-roles/divisions.md) | 5 | | [**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** | 140+ |
***
πŸ“œ Legal Documents | Document | Purpose | | ------------------------- | --------------------------- | | **Operating Agreement** | DAO governance rules | | **Member Agreement** | Rights and responsibilities | | **Lease Templates** | Equity lease terms | | **Investment Agreements** | Investor terms by tier | Contact for document requests.
*** {% 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: 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= ``` 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.