The outcome of deciding a request: serve it, or refuse it with a reason. Every client-facing reply renders one of these.

A refusal: why the request was refused, and an intuitive message for the client.

Why a request was refused. A policy refusal is final for this request. An unavailability is an inability to decide, whose Transience separates a retryable 503 from a terminal 500.

Serve transient outages, rate limits, timeouts, and open breakers as 503. Serve internal or parse faults as 500. WillResolve and WontResolve encode that distinction.

A Retry-After delay, in whole seconds. A 'newtype' so a raw count of seconds is never confused with some other integer when it reaches a response header or a sweep's wait.

The name of the rule that decided a refusal, for the audit trail and the denial body.

Refuse a request that could not be decided. The Transience it carries is what artifactStatus renders as a 503 or a 500, so a caller states that rather than a status.

Project a rules Decision into a serve outcome. An Undecidable decision rejects as Unavailable, which is fail-closed: a version no rule could vet is never admitted.

The HTTP status a concrete-artifact request renders to. A packument request has no single status, because the pipeline chooses one over the survivors: PackumentStatus models that.

Map a serve outcome to its concrete-artifact status: 503 only where it will resolve, so a WontResolve unavailability is a 500. An upstream 404 is no serve decision and never appears.

The HTTP status an ArtifactStatus renders as.

The HTTP status a packument request renders to, chosen over the merged survivor set. There is no 404: the package exists, and a genuine absence is decided before the merge.

A packument's status from the per-version outcomes: with no survivor the most recoverable cause wins, 502 under 503 as a transient origin may yet answer, and an empty input is a 403.

The longest suggested RetryAfter among transient causes, or Nothing when none of them suggested a delay.

An operator-configured message appended to every denial, typically where to ask for help. Stored trimmed, so an all-blank value contributes nothing.

Build a HelpMessage, trimming surrounding whitespace.

Append a non-blank operator HelpMessage to a denial message, separated by a single space. A blank or absent help message contributes nothing.

A refusal's text in its two parts, so an ecosystem renders whichever its own denial surface carries and the help message is not dropped for one with no envelope to hold both.

Pair a decided reason with the mount's configured help message, if it has a non-blank one.

The refusal as one line: the reason, with the help message appended after a single space.