Cadence (mirror)
Local Cadence usage in KPIs & OKRs; shared definition in Core.
The shared definition and source fields are in Core / Cadence. This page explains only usage in KPIs & OKRs.
Use and boundaries
Maintain source values in Core Record Types. Key and Lifecycle Status drive collection. The current workflow uses explicit date rules by Key; Repeat Frequency and Period Hours are not a general RRULE interpreter. By Day is consulted for daily-working-days. Only links added locally belong to this base.
Locally used fields
Key, Lifecycle Status, By Day, Period Key Format.
These are consumer labels and may differ from the source. Local operational links and derived values:
| Field | Storage | Local usage |
|---|---|---|
| Recurrence Configurations | Linked records | Recurrence Configuration |
| Metrics | Linked records | Metric |
| Compliance Definitions | Linked records | Compliance Definition |
| Tags | Linked records | op:tags · local label; does not update Core |
Where to correct
Correct shared data in Core Record Types[Cadence]. Adjust links to tasks, targets and other operational records here. Check the column mapping, refresh interval and write-back behavior in the sync settings before relying on them. Do not assume editing a mirror updates Core. See Maintain shared records.