An administrator submits an interactive change for validation. Rhythm saves the proposed outcomes and combines their impact across batches. Validation leaves the target records intact. The administrator reviews that report before choosing Apply. Approval sends back the report’s fingerprint and cannot substitute another impact. A job submitted directly for application cannot use that approval action. Preview expiry is checked when someone acts on the job, so an old list row can still display Validated. CRM file imports run directly, whereas Platform offers bounded uploaded-dataset validation. The product should make file preview limits clear before staff submit a file.
Job submission preserves the input being reviewed.
Version protection handles edits between preview and application.
Destructive changes require this approval stage.
The Formal Contract
The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
Outcomes
Validation reports planned outcomes without changing the target records.Approval identifies the impact the administrator reviewed.An expired preview requires a new validation.
7 rules, 5 to be proved before approval. A rule's product intent is derived from its origin: 7 confirmed by a product decision, the rest inheriting this capability's confirmed.
Id
Rule
Kind
Enforced at
Provenance
01must prove
Confirmed
Validation runs the operation’s prevalidation checks and reports planned impact and refusals without saving changes to the target records.