Community Property Records: Connecting Decisions, Work and Money

What should a community be able to verify?

Shared ownership becomes more useful when people can answer ordinary questions: What did we approve? Who is doing the work? What was spent? What changed?

Built By DAO's approach connects participation to a record of decisions and delivery. This article explains the information a community-owned property needs, while our property operations article follows the work itself.

Four records that belong together

A practical property record connects four kinds of information:

| Record | What it answers | Example | | -------- | -------------------------------------------- | ---------------------------------------------------------- | | Decision | What was authorized, and by whom? | Approval to improve a shared courtyard | | Work | What needs to happen, and who owns the task? | Design, materials, installation and review | | Money | What budget was allocated and spent? | Approved scope, supplier invoice and payment | | Outcome | Did the work achieve its purpose? | Completed installation, inspection and ongoing maintenance |

These are illustrative examples, not a report of a completed BBD project. Together, they create a chain people can follow from a proposal to a working improvement.

A transaction is only one part of the record

A blockchain transaction can record an authorized movement of an asset. It cannot, by itself, establish that a roof was repaired properly or a workshop is safe to use. Those conclusions require evidence from the physical work and people qualified to review it.

The same distinction applies to ownership. A balance shown in software needs an understandable relationship to the relevant legal entity, agreements and participation rules. The record should help people inspect that relationship rather than make them infer it from a token name.

In BBD's model, contribution, housing participation and investor capital have different roles. The dual-token documentation explains why those records are separated. A record of contribution is not automatically an investor subscription or a promise of cash distribution.

Show people the information they need

Transparency does not mean publishing every resident's personal details. A community can see a repair's status, budget and completion without exposing the private information in the original request.

The useful design question is: what does someone need to understand, verify or act on this decision? An operator may need contact information to schedule access. Other members may need only the scope, cost and status. Keeping those views distinct supports both accountability and privacy.

Make review part of contribution

A contribution record should explain the task, its acceptance criteria, the work submitted and the review outcome. That gives the contributor a visible account of what they helped build and gives the project a consistent basis for recognizing useful work.

Our contribution guide shows that journey. The record is most valuable when it stays connected to a real project outcome, such as usable equipment, organized materials or a completed planning task.

Use the record when decisions change

Projects evolve. A discovered building condition may change a rehabilitation budget. A supplier may miss a deadline. Members may identify a better use for a shared space.

A useful record retains the earlier decision and explains the revision: what changed, who authorized it and what it means for the work. This helps new participants understand a project without relying on someone else's memory.

Start with a place and a purpose

The goal is a property people can understand and help improve. Technology supports that goal when it connects decisions, work and resources in a way people can use.

Explore how BBD builds, then find a way to contribute or discuss a project partnership.