Explicit boundaries for partial saves

Context

Several console actions compose individually committed resources. A later failure can leave real earlier work behind.

Decision

Composite client saves retain successful earlier calls when a later step fails and report partial outcomes rather than attempting compensating browser writes.

Alternatives Considered

Browser compensation after partial saves: A compensating request can fail or overwrite intervening work, so it cannot provide transaction guarantees. Composite server operations: Combining record and owner, field and rules or object and owner requires a new operation contract and a product decision. Suppressing later-step errors: The person would mistake partial completion for a complete save.

Consequences

Record content, field definitions and activation can survive failed ownership or rule steps. Search follow-ups can lag completed definition changes. Cancellation does not reverse load batches that already committed.