Evaluate dated conditions for named records

Purpose

Applications ask whether identified records satisfy their conditions on a particular day. The results can distinguish a known answer from an absent fact.

How It Works

An application supplies a dataset, record identities and named conditions. Platform resolves the dataset and compiles the conditions together. The evaluation uses the workspace calendar and can anchor relative dates to another day. Boolean answers can remain unknown when their facts are missing. Collection calculations return numbers for the application to compare. The result includes only records found within the workspace. A user cannot invoke this internal operation directly. Database grants still limit what the system reader can read. Current-only source views continue to describe the present, so historical conditions need dated source information.

Relationships

Internal condition evaluation uses resolved datasets and read-only query execution for named subjects.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes: Applications distinguish a failed condition from a missing fact.Dated evaluations use the workspace calendar.
Surfaces: job

Controls

19 controls apply, from the corpus control catalogue.

TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-LOG-001 TC-LOG-004 TC-LOG-005 TC-PI-001 TC-PI-005 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-VEN-001 TC-VEN-002 TC-VEN-003

Business Rules

6 rules, 6 to be proved before approval. A rule's product intent is derived from its origin: 0 confirmed by a product decision, the rest inheriting this capability's proposed.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Proposed	Only a system caller can evaluate conditions over named records; a user caller is refused. proved by `ATS-PFM-QRY-020-01`, `TST-PFM-QRY-266`	permission	service	test services-platform:modules/queries/tests/integration/services/execute/compile-predicates.integration.spec.js#refuses a user execution, because predicates are evaluated by the macroservice itself
`02`must prove Proposed	An evaluation accepts one to one thousand nonblank subject ids and one to one hundred predicates with distinct nonblank names; invalid lists or incompatible predicate options are refused. proved by `ATS-PFM-QRY-020-02`	validation	service	observed services-platform:modules/queries/services/execute/compile-predicates.ts:validPredicates
`03`must prove Proposed	Boolean conditions preserve an unknown result for missing facts by default, while the alternate null policy evaluates them using the ordinary query filter’s meaning. proved by `ATS-PFM-QRY-020-03`, `TST-PFM-QRY-266`	calculation	service	test services-platform:modules/queries/tests/integration/services/execute/compile-predicates.integration.spec.js#keeps a negated operator unknown over an absent value, and answers it as the filter does when NULL means false
`04`must prove Proposed	Collection calculations support count, sum, minimum and maximum; empty collections give zero for count and sum and no value for minimum and maximum. proved by `ATS-PFM-QRY-020-04`	calculation	service	observed services-platform:modules/queries/services/execute/compile-query.ts:subjectPredicateCompiler
`05`must prove Proposed	A supplied evaluation day anchors relative dates in the workspace calendar, including calendar shifts; invalid days and date tokens used on unsuitable fields are refused. proved by `ATS-PFM-QRY-020-05`, `ATS-PFM-QRY-020-07`, `TST-PFM-QRY-266`	calculation	service	test services-platform:modules/queries/tests/integration/services/execute/compile-predicates.integration.spec.js#resolves the same shift from the as-of day, so a contact eighteen today was not the day before
`06`must prove Proposed	Evaluation reads only the named records in the current workspace through a read-only database role, and its logs omit subject ids, fact values and query text. proved by `ATS-PFM-QRY-020-06`	invariant	service, database	observed services-platform:modules/queries/services/execute/compile-predicates.ts:evaluateSubjectPredicates

Planning

Implementation

Evaluate dated conditions for named records ​

Purpose ​

How It Works ​

Relationships ​