Operations and results

An accepted request and a completed outcome are different events. Future business APIs must preserve the operation identity through durable work and authorized result retrieval.

Follow one operation

A well-scoped operation starts from immutable inputs and prerequisites. Acceptance records the intent; progress describes work actually observed; terminal state explains what completed, failed, stopped or remained uncertain.

Use saved result references to retrieve durable artifacts. A webhook is a notification, not the only place the result should exist. The consumer's delivery acknowledgement is separate from the authoritative artifact.

Partial and uncertain results

A processed source page may yield no qualifying product. A product may be persisted before its media is hosted or approved. A channel export may exist before its destination accepts it. These are not interchangeable completion counts.

An uncertain provider outcome requires investigation of that same operation, not a blanket retry that might duplicate cost or real-world effects.

Stop and continue

Stopping prevents future authorized work where possible; it cannot undo already-incurred costs. A safe continuation derives the remaining frozen scope on the server. It does not accept a browser-generated replacement item list.

This release

Only the authentication release contract is in scope for new keys. These lifecycle rules describe planned business integration, not an available job-submission or queue-control API.