Skip to main content

Property

A named field on an Object that gives Records somewhere to hold a value.

type: data-model · status: published · abstraction: entity

What it is​

A Property is a field definition attached to an Object: its name, its Value Type, whether it is required, whether it accepts multiple values (a list rather than a single item), whether those values must be unique, and any other constraints or defaults. Properties can be canonical (part of a canonical Object) or tenant-added extensions. Relationship Properties are the mechanism by which one Record points at another.

Why it exists​

Properties keep the schema declarative. Because every field is a first-class, typed, described entity rather than a hardcoded column, the platform can render UI, validate input, run analytics, map integrations and let AI agents reason about data without any per-customer code.

Relationships​

Outgoing

  • is typed by → Value Type (many-to-one) — Every Property declares one Value Type.

Incoming

  • is part of ← Object — An Object's shape is the set of Properties declared on it.

Neighbourhood​

Stakeholder summaries​

  • Product — Property design drives form UX, validation and list-view configuration.
  • Investor — Declarative fields are why new modules and industries ship in weeks rather than quarters.
  • Marketing — Add the fields you need, when you need them. No tickets, no developers.
  • Engineering — Typed field definitions referencing a Value Type, owned by either the platform or the tenant, with relationship properties resolving to other Objects.