Shared typed persistence for custom records

Context

Organizations need independent records beyond the fixed application catalogue. Those entries need ordinary identity, querying, connections and history.

Decision

Platform owns runtime custom categories and persists their entries in shared record rows and typed property-value rows, with plain property keys.

Alternatives Considered

Table-style values embedded on another record: Such content would lack the independent identity, history and relationships needed for a custom register. Separate custom-record macroservice: The approved architecture places this runtime configuration and storage in Platform. Dedicated table for each custom category: Category configuration would require schema migrations rather than runtime definitions.

Consequences

Activation supplies a dataset without deploying a per-object schema. Properties reuse shared custom-field conversion and validation. Supported numeric values carry scaled comparison shadows.