Deprecated: a tenant's rule settings are orgSettings on GET and PATCH /api/tenant. This route still serves the per-project rows of a tenant several projects share.
Replaces the settings for project, or the tenant-wide row without it, whole. A patient whose metadata.project has a row reads that row; any other patient reads the tenant-wide row. The two are not merged. A tenant-wide write first makes a tenant's only project row its tenant-wide row, as PATCH /api/tenant does. Audited as UPDATE_ORG_SETTINGS.
For each patient the write reaches, judged by its own settings over the org's: a band changed ends the episode judged under the old one THRESHOLD_CHANGED; a code switched off (its band "NO_THRESHOLD", or out of bed enabled: false) has its active alert resolved and its open episode closed THRESHOLD_CHANGED at the save, the other codes' left alone; an acknowledged out-of-bed absence, whose episode the ack closed, has its still-active alert resolved; a band deleted closes nothing.
With ifAbsent=true the row is created only when none exists and never replaced, so a default seeded at enrolment cannot overwrite a concurrent save; the answer adds created and carries the stored document either way, and only a creation is audited.
A body whose settings has no triggers key keeps the stored triggers (the home defaults seeded by Signals, or triggers pushed through the config routes); a body that sends triggers, {} included, replaces them.
The body may carry resolvedAt (ISO 8601), when the caller resolved this write: it lands only over a stored write resolved earlier, or stored without one, and is otherwise refused 409 STALE_SETTINGS with nothing written or audited. A write without resolvedAt always lands and keeps the stored stamp.
Signals stores settings as given and reads it only through the triggers it holds (triggers, the home's and the resident's own): what each other key means is theirs, so the object is checked for shape and size only. The default pack reads bands — per code { low?, high? }, { mode: 'baseline', pct, low?, high? } (outside either band fires; a patient's own baseline band with no sides of its own is judged alone) or "NO_THRESHOLD" — and outOfBed: { limitSeconds, enabled?, window?: { start: 'HH:MM', end: 'HH:MM', timeZone } }. A patient's own key wins over the org's; extra keys are ignored. See tech/RULES-ENGINE.md.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||