FAILURE MAP
← Case archive

FA-6598 / HTTP semantics / Member archive

A read policy distinguishes safety from idempotency · case 03

A read policy distinguishes safety from idempotency.

Member previewVariant 3 · 3 implementations · 4 checks per implementation

Case contract

A read policy distinguishes safety from idempotency: return the result specified by the explicit input/output boundary fixtures.

Why this case matters

This deterministic http semantics model isolates the safe-methods policy at a network component boundary.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixtureActualExpectedOutcome
fixture 4truefalseFailed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.

Sign in to the archive ↗