Policies & providers

Execution is driven by policy.EffectivePolicy, resolved by a controlplane.PolicyProvider.

Effective policy

Policies are per-key and have (today) three main sub-policies:

• Retry: Bounded attempts, backoff, jitter, timeouts, and budget references.
• Hedge: Parallel attempt execution (Fixed-Delay or Latency-Aware). See Hedging.
• Circuit: Short-circuiting logic for failing dependencies. See Circuit Breaking.

All policies are normalized/clamped via EffectivePolicy.Normalize() to prevent unsafe configs (busy loops, tiny timeouts, unbounded concurrency).

Providers

Providers implement:

GetEffectivePolicy(ctx context.Context, key policy.PolicyKey) (policy.EffectivePolicy, error)

Today, recourse ships with controlplane.StaticProvider for in-process policy maps.

Missing policy behavior

If policy resolution fails, the executor consults ExecutorOptions.MissingPolicyMode:

• retry.FailureDeny (default): fail fast with retry.ErrNoPolicy
• retry.FailureAllow: run a single attempt
• retry.FailureFallback: use a safe default policy