Confirmation message setting

The Lifecycle

Transitions Explained

The product stores a confirmation selection for a purchase-time consumer. A shared selection names a workspace template; an owned selection uses content Platform stores for that product. HTTP replacement keeps an omitted selection, merges supplied owned content and requests clearing when leaving owned mode. Domain saving can retain an owned selection by omission, but cannot compose or clear that owned content.

What Cannot Happen

Unsellable kinds reject confirmation settings. A newly selected shared template must belong to the correct workspace and purpose and have no record owner. The console currently exposes no confirmation controls. Sending the selected message belongs to the purchasing consumer.

Concurrency and Timing

The product lock remains held while Platform answers and response data is read. A remote refusal aborts the local transaction. Platform success is not reversed if the response is lost, response assembly fails or Accounting cannot commit; no durable reconciliation is provided here.