> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dapp.ing/llms.txt
> Use this file to discover all available pages before exploring further.

# Entities and relationships

> Understand how builders, company hubs, dApps, listings, and public relationships fit together on dApp.ing.

dApp.ing connects people, organizations, products, and opportunities. Each has a distinct public identity, and relationships add context without making every claim equally authoritative.

## Core entities

| Entity          | Represents                                                         | Common public context                                                                                                  |
| --------------- | ------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------- |
| Builder profile | One person and their professional identity                         | Experience, projects, skills, recommendations, intentions, connected accounts, and selected wallets                    |
| Company hub     | An organization or ecosystem                                       | Official details, team, products, opportunities, events, resources, and company activity                               |
| dApp            | A product or project                                               | Description, category, ecosystem, team credit, reviews, deployments, token context, and available on-chain information |
| Listing         | A job, grant, bounty, hackathon, accelerator, event, or side event | Publisher, audience, eligibility, dates, location, rewards or compensation, and destination                            |
| Conversation    | Direct or group communication between accepted participants        | Message-request state, participants, roles, and invite access                                                          |

## Relationships add context

A builder can list experience at a company, receive dApp team credit, recommend another builder, endorse a skill, or follow an entity. A company can publish listings and add teammates with different access.

These relationships do not all mean the same thing:

* **Verified experience** is stronger evidence than a self-entered role.
* **Accepted team credit** connects a builder to a dApp but does not prove every contribution.
* **Company access** allows management actions; it is not automatically a public employment claim.
* **Following, Going, upvotes, reviews, and comments** show activity or opinion, not identity verification.

Evaluate the entity itself and the evidence attached to the specific claim. A relationship elsewhere on the platform should not be treated as a guarantee.

## Related guides

<CardGroup cols={2}>
  <Card title="Personal profiles and company hubs are different" icon="users" href="/help/companies/personal-profiles-and-company-hubs-are-different">
    Choose the correct identity for personal work and company operations.
  </Card>

  <Card title="Build and share your proof page" icon="badge-check" href="/help/getting-started/build-and-share-your-proof-page">
    Turn your work and professional intentions into a useful public page.
  </Card>
</CardGroup>
