{
  "id": 12625383,
  "title": "The Third Leg of the Parity Test",
  "url": "https://urgent.news/2026/10/07/the-third-leg-of-the-parity-test",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-07T12:31:29.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/steefjan_wiggers_34a415b/the-third-leg-of-the-parity-test-j1b"
  },
  "original_language": "en",
  "account": "The third leg of the parity test for backend consistency revolves around preserving auth, error behavior, and idempotency across different doors. Authorization Stays in the Kitchen addressed the first leg, while confusion telemetry and recovery messages handled the second. This post focuses on the third leg, which proves most crucial for agents due to their retry behavior. Agents make retries based on their judgment, triggered by factors like timeouts, ambiguous errors, truncated responses, and failed calls. The MCP protocol does not prohibit second-order retries; instead, it serves as a control case to demonstrate the failure mode. The companion repo's new driver validates this failure mode, showing that two calls with identical orders result in two separate orders. This scenario reflects a common production incident involving agents and non-idempotent writes. The series rule holds that neither door contains business logic, and deduplication is handled at the kitchen's level. The kitchen maintains a store keyed on the caller's idempotency key, storing a fingerprint of the request and the original confirmation. It responds with four possible outcomes: placed, replayed, conflict, or invalid. If the idempotency key is found in the store and matches the current request's fingerprint, the system returns the original confirmation without creating new data. Conversely, a different request with the same key results in a conflict, indicating a caller error that should be rejected with an appropriate message. The REST door uses the Idempotency-Key request header, as specified in an IETF httpapi draft co-authored by Stripe, Adyen, and other payment APIs. This header allows for a completed operation to replay its original result and rejects reused keys with different payloads using a 422 status code. On the MCP door, the lack of headers necessitates embedding the idempotency key as an argument, which requires proper documentation and SDK-driven implementation. The MCP door's description hash changes with modifications, enabling telemetry to attribute behavior shifts accurately. However, the idempotency key relies on agent discipline, as the protocol offers no guarantees beyond probabilistic defense.",
  "summary": "Months ago, a commenter on this series proposed a test: if the same backend really stands behind both doors, then auth, error behavior, and idempotency must be preserved across them. Authorization Stays in the Kitchen settled the first leg. The confusion telemetry and recovery messages settled the second . This post settles the third, and it turns out to be the leg that matters most for agents,…",
  "key_points": [
    "The third parity test leg focuses on preserving auth, error behavior, and idempotency across doors.",
    "Agents trigger retries based on timeouts, ambiguous errors, truncated responses, and failed calls.",
    "The MCP protocol allows second-order retries, serving as a control case to demonstrate failure mode."
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}