Entities and relationships

Each entity has its own public identity, and the relationships between them do not all carry the same weight.

Core entities

Entity	Represents	Public context it carries
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, projects, listings, events, and company activity
Project	A shipped product or protocol	Description, category, ecosystem, team credit, reviews, updates, launches, deployments, and token context
Launch	One week on the project launch board, with its own page	Its own name and tagline, week, result, medal, upvotes, and what changed for a relaunch
Listing	A job, grant, bounty, hackathon, accelerator, event calendar, or event	Publisher, audience, eligibility, dates, location, rewards or compensation, and destination
Conversation	A direct or group conversation between accepted participants	Message-request state, participants, roles, and invite access

A project is published either by a company hub or by an individual builder. That choice decides who can edit it and whose name appears on it.

Relationship	Between	How it is established
Experience	Builder and company	Entered by the builder, then optionally verified
Company membership	Builder and company	Invitation accepted; owner, admin, or member
Project team credit	Builder and project	Offered or requested, then accepted by the other party
Recommendation	Builder and builder	Written by one profile about another
Skill endorsement	Builder and builder	One endorsement per person per skill
Follow	Builder and builder, or builder and company	One-directional; no acceptance required
Publisher	Builder or company, and listing	Chosen at publish time

Interactions are not available everywhere. The surfaces differ by type.

Interaction	Where it is available
Review	Projects only. One review per person per project, rated 1 to 5, editable at any time
Comment	Jobs, grants, bounties, accelerators, hackathons, and events. Not on projects, companies, event calendars, or profiles
Upvote	Projects (each vote goes to the current launch), jobs, grants, bounties, accelerators, hackathons, event calendars, events, and blog posts
Going	Event calendars, events, and hackathons
Follow	Builder profiles and company hubs

You cannot review a company, a job, or an event. You cannot comment on a project or a company hub.

Verified experience is stronger evidence than a self-entered role, and it is evidence about one role only.
Accepted team credit connects a builder to a project. It does not establish which parts they built.
Company access is a workspace permission. It is not a public employment claim, and a public team listing is not a permission.
Following, Going, upvotes, reviews, and comments record activity or opinion. They verify nothing.

Evaluate the entity itself and the evidence attached to the specific claim. A relationship elsewhere on the platform is context, not a guarantee.

Choose the correct identity for personal work and company operations.

Compare company, project team, and group conversation roles.