01must proveConfirmed | Evaluation returns eligible, ineligible or indeterminate; an indeterminate result becomes denial under closed, admission requiring review under open with review, or an unresolved outcome under defer. | calculation | service | test |
02must proveConfirmed | Evaluation verifies supplied subjects in the workspace before applying conditions, with an absent record yielding indeterminate and a not-found reason before the failure policy is applied. | invariant | service, database | test |
03must proveConfirmed | An omitted or empty required subject yields an indeterminate result with a missing-subject reason. | validation | service | test |
04must proveConfirmed | A failed data read becomes an indeterminate result with a read-failure reason under the binding policy rather than an exception, preserving results for the remaining batch entries. | policy | service | test |
05must proveConfirmed | An empty stored value fails its condition, such as an absent address, instead of making the evaluation indeterminate. | calculation | service | test |
06must proveConfirmed | Evaluation selects the version effective on the requested day and resolves relative dates from that day. | calculation | service | test |
07must proveConfirmed | Evaluation batches accept one to 50 requests and return results in request order, rejecting a larger batch as a whole. | validation | api | test |
08must proveConfirmed | Purpose declarations control caller admission: portal callers require portal support, console callers cannot use system-only purposes and services require system support, with eligibility read authority also required for console and service callers. | permission | api, service | test |
09must proveConfirmed | Portal requests evaluate only the signed-in member’s linked contact for display and treat supplied facts as asserted, rejecting foreign contacts, stronger consistency or an unlinked member. | permission | api | test |
10must proveConfirmed | Explanation levels are none, portal, administrator and full; administrator and full require eligibility read authority and exclude portal callers, with excessive requests rejected. | permission | service | test |
11must proveConfirmed | A closed-policy indeterminate result uses the rule’s portal message, with labelled explanations and no linked-record names exposed to portal readers. | policy | service | test |
12must proveConfirmed | People cannot request transactional evaluation over the web; in-process checks read and record within the consumer transaction, with equivalent SQL-function states for SQL-only expressions. | policy | api, service, database | test |
13must proveConfirmed | Provider evaluation uses declared batch sizes, a five-second budget and one retry, opening a 30-second circuit after five failures in one minute and returning indeterminate while open. | policy | service | test |
14must proveConfirmed | The eligibility data reader can inspect reporting-readable data only within the workspace and cannot write records. | permission | database | test |
15Confirmed | The product should publish evaluation for use inside consumer processes as the approved architecture describes; the available implementation remains internal to Platform. | policy | service | documented |