Names of the objects whose persist-time overlay invalidated their Pull watermark.
Pure, so the decision that matters — persist DETECTED it, evolution must ACT on it, and on
nothing else — is pinnable without a database.
Two exclusions, both guarding against OVER-firing. Resetting a watermark costs a full re-fetch of
the object, so a rule that fires when nothing relevant changed quietly turns every refresh into a
fleet-wide full sync:
a CREATED row is never a change. A brand-new object has no watermark to invalidate.
restrictTo, when given, limits the answer to that set (the evolution passes its CONTINUING
entity maps). An object with no continuing map has no Pull watermark this run can reset, so
reporting it would inflate the change set — and HasChanges — with a name nothing acts on.
Matched case-insensitively, as every catalog-to-map reconciliation in this codebase is.
Returned names keep the CATALOG's casing, which is what the source object is called.
Names of the objects whose persist-time overlay invalidated their Pull watermark.
Pure, so the decision that matters — persist DETECTED it, evolution must ACT on it, and on nothing else — is pinnable without a database.
Two exclusions, both guarding against OVER-firing. Resetting a watermark costs a full re-fetch of the object, so a rule that fires when nothing relevant changed quietly turns every refresh into a fleet-wide full sync:
restrictTo, when given, limits the answer to that set (the evolution passes its CONTINUING entity maps). An object with no continuing map has no Pull watermark this run can reset, so reporting it would inflate the change set — andHasChanges— with a name nothing acts on. Matched case-insensitively, as every catalog-to-map reconciliation in this codebase is. Returned names keep the CATALOG's casing, which is what the source object is called.