Dependency Failure Policies by Selling Context

Context

External assessment can fail while a buyer is browsing or preparing a sale. The implemented response depends on the calculation mode and the failed dependency.

Decision

Required pricing extensions fail closed for checkout work, while display paths can flag unavailable answers; unavailable code-part checks refuse claims and automatic unavailable parts are skipped.

Alternatives Considered

Continue every sale after dependency failure. The sale could bind an amount whose required handler never answered.

Reject every display after any dependency failure. A failed price dependency would remove otherwise useful browsing information.

Consequences

Preview and placement reject required extension failures and record operational diagnostics. Display qualification can fall back to Standard with a warning, and binding qualification receives its transaction-time check. Stored unresolved handler references can make checkout unavailable.