From 74a6b219cc9ac3696497ddee48caf9009fd02046 Mon Sep 17 00:00:00 2001 From: Bryan Helmkamp Date: Mon, 23 Feb 2026 16:19:10 -0500 Subject: [PATCH] Fix spec: FAIL does not trigger retries, only RETRY does The test criteria incorrectly said FAIL outcomes should be retried. The pseudocode (Section 3.5) and the C reference implementation both return immediately on FAIL. Only RETRY status triggers the retry loop. Co-Authored-By: Claude Opus 4.6 --- docs/specs/attractor-spec.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/specs/attractor-spec.md b/docs/specs/attractor-spec.md index 58584362c..c62c672a1 100644 --- a/docs/specs/attractor-spec.md +++ b/docs/specs/attractor-spec.md @@ -1861,7 +1861,7 @@ This section defines how to validate that an implementation of this spec is comp ### 11.5 Retry Logic -- [ ] Nodes with `max_retries > 0` are retried on RETRY or FAIL outcomes +- [ ] Nodes with `max_retries > 0` are retried on RETRY outcomes (FAIL returns immediately) - [ ] Retry count is tracked per-node and respects the configured limit - [ ] Backoff between retries works (constant, linear, or exponential as configured) - [ ] Jitter is applied to backoff delays when configured