01must proveConfirmed | Platform’s console binding routes require binding-management authority and do not separately verify permission to edit the referenced consumer record. | permission | api | observed |
02must proveConfirmed | A binding requires an application-owned registered purpose, compatible required subjects and facts, batch-capable conditions for populations and no provider conditions for SQL-only purposes, including referenced expressions. | validation | service | test |
03must proveConfirmed | Binding parameters must be declared, satisfy their types, collection forms, choices and bounds, and supply every required value without a default. | validation | service | test |
04must proveConfirmed | Bindings follow the published expression or pin a published or superseded version of that rule; absent, draft, foreign or newly retired pins fail, while existing retired pins remain stored. | validation | service, database | test |
05must proveConfirmed | A binding inherits its purpose’s failure policy unless it explicitly selects closed, open with review or defer. | policy | service | test |
06must proveConfirmed | Each consumer can bind a rule once, and deprecated or archived rules reject new bindings. | invariant | service, database | test |
07must proveConfirmed | Binding updates recheck compatibility and require the version read, rejecting stale updates without changing the binding. | validation | service | test |
08must proveConfirmed | Suspended bindings reject evaluation rather than returning an ineligible result, and bindings of archived rules cannot be resumed. | lifecycle | service | test |
09must proveConfirmed | Deleting a binding removes its plans while preserving recorded decisions. | lifecycle | service, database | test |
10must proveConfirmed | Binding lists require a rule or consumer application, support consumer filtering and cursors and accept no more than 100 consumer references in one request. | validation | api, service | test |
11must proveConfirmed | Consumer applications manage bindings through service-only dispatch under their own principal, with that service recorded as the actor. | permission | api | test |
12must proveConfirmed | Plan responses carry a version tag affected by rule versions, failure policy, portal wording and referenced expressions, with a matching tag returning not modified. | calculation | api, service | test |
13must proveConfirmed | Console plan responses omit internal queries, provider details and explanation templates, while consumer services receive the complete plan. | permission | service | test |
14must proveConfirmed | The product editor’s eligibility card maintains a Platform binding to a shared or product-private rule without storing the rule on the product; private rules stay outside the shared catalogue until promoted. | policy | console | observed |