> 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/developers/platform.md).

# Dashboard Integration

The Built By DAO dashboard is a React, Express, and PostgreSQL application. It coordinates member onboarding, projects and tasks, skills, housing, governance, treasury and rewards, investor workflows, notifications, and administration.

## Current surfaces

| Area             | Required behavior                                                                                                                                             |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Membership       | Read identity and rank; prepare authorized mint, promotion, lowering, suspension, and designation actions                                                     |
| Work rewards     | Carry accepted evidence into policy-qualified, role-authorized, confirmed and idempotently indexed WORK settlement                                            |
| Housing Loyalty  | Display property schedules, lease-stamped rates, qualifying rent, and `RENT` provenance                                                                       |
| Governance       | Use the current square-root voting curve, rank/designation weights, and proposal lifecycle                                                                    |
| Treasury         | Show balances, policy limits, proposal state, allocations, and exact role requirements                                                                        |
| Business revenue | Reflect the 100% DAOBusiness-to-Treasury sweep and explicit founder-fund allocations                                                                          |
| Investors        | Identity and accreditation review, expiring signed terms, on-chain payments and bank-transfer confirmation; keep these separate from the QOF or note security |

## Transaction experience

Every contract-writing surface should show:

1. the action and consequences in plain language;
2. the connected address, network, role, and resource scope;
3. the transaction awaiting wallet confirmation;
4. broadcast and confirmation progress;
5. a useful failure or replacement state;
6. the confirmed result and explorer link when available.

Read-only views identify stale or unavailable data. They do not show zero balances or empty history as though synchronization succeeded.

## Deployment manifest

The application consumes a versioned, validated manifest containing the chain ID, deployment identifier, contract addresses, ABI hashes, implementation metadata, and policy seed version. Startup fails safely when the manifest is incomplete or incompatible.

## Availability

Production member transactions use Base mainnet. Read the application’s selected release manifest for its network, contract identity, and interfaces rather than copying addresses from documentation. A feature is available when its required contracts, current policy, member permissions, and program terms are satisfied; the dashboard should explain any unmet requirement. See [Developer Overview](/developers/developers.md) for integration rules.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.builtbydao.com/developers/platform.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.