Universal Record model

RecordId

BuildWithHQ uses a universal record identity so first-class and custom entities can share common platform behavior. Examples can include files, calendar events, messages, contacts, knowledge items, jobs, discussion objects, and other module entities.

Why it matters

A common RecordId lets cross-cutting systems anchor to the same object identity: security context, tenant scope, module scope, location scope, lifecycle state, relations, AI provenance, audit history, favorites, and workflows.

RecordRelations

RecordRelations connects records to other records. This is the basis of the “anything can relate to anything” model. Relation operations must preserve tenant/security boundaries rather than becoming an alternate path around authorization.

Design rule

Feature-specific tables may contain domain fields, but important business entities should participate in the universal record layer when they need common BuildWithHQ behavior.