Compliance Definition
A catalog definition of a possible duty, document or identifier.
Definition Kind, jurisdiction and source flags classify the catalog item. Cadence is linked to the shared catalog; Cadence - OLD is historical. Applicability to a company is recorded in Compliance Obligation. This is an adjacent operations entity, not part of the current Slack KPI collection path.
Use and boundaries
Field names below are the current product labels. * and ° are UI markers, not database constraints. A preferred single-record selection is not a global cardinality constraint either. The related guide explains operational rules.
Fields
| Field | Storage | Source, options or boundary |
|---|---|---|
| Name | Text | Stored value. |
| Definition Kind | Single select | Obligation, Document, Identifier, Unresolved |
| Entity Type | Text | Text reference; not a linked record. |
| Jurisdiction | Text | Stored value. |
| Required Source Flag | Checkbox | Stored value. |
| Cadence - OLD | Single select | Daily, Weekly, Biweekly, Monthly, Quarterly, Annual, On Demand |
| Notes | Long text | Stored value. |
| Compliance Obligations | Linked records | Compliance Obligation |
| Cadence | Linked records | Cadence (mirror) |
| Cadence (Key) | Lookup | Cadence → Key |
| Tags | Linked records | op:tags · optional labels from the Core Tags catalog; classification only. |
Example and maintenance
Illustrative example: “Annual license renewal” is a catalog duty before applicability is assigned.
Use the existing fictitious records to inspect relationships in the guide. Before changing fields, check lookups, formulas, intakes and workflow contracts. This page documents structure; a field does not prove that an integration populates it.