{"schema_version":1,"experiment_id":"eoa_inverse_innovation_exp09_archetype_breadth150_20260804","research_id":"eoa_inverse_innovation_exp09_light_prior_art_20260804","cell_id":"representation_independent_interface_contract__computer_science","search_lanes":{"direct_problem_and_intervention":{"queries":["idempotency registry interface claim complete fingerprint conflict expiration concurrency contract","idempotency key state machine black box conformance storage backend","idempotency middleware Store interface begin commit fingerprint inflight cached Redis MemoryStore","GitHub idempotency registry adapter claim complete fingerprint lease interface"],"source_ids":["SRC1","SRC2"],"no_result_note":null},"synonyms_and_historical_terms":{"queries":["idempotent consumer deduplication store compare payload concurrent request semantics","idempotency record repository lock pending completed request hash","idempotent receiver saved response lease TTL dedup store","same client request ID different intent late arriving request"],"source_ids":["SRC1","SRC2","SRC3"],"no_result_note":null},"products_practices_and_standards":{"queries":["IETF Idempotency-Key HTTP header fingerprint concurrent outstanding request expiry","Stripe idempotent requests same key parameters concurrent 24 hours","idempotency library storage adapter memory redis postgres conformance suite","lease based idempotency state machine pluggable store"],"source_ids":["SRC1","SRC2","SRC3"],"no_result_note":null},"component_combination":{"queries":["property based state machine testing idempotency storage adapter contract","stateful testing compare database implementation with in-memory model","parallel state machine testing idempotency store atomicity expiry token CAS","black box contract tests idempotency backend substitution"],"source_ids":["SRC2","SRC4"],"no_result_note":null}},"sources":[{"source_id":"SRC1","title":"draft-ietf-httpapi-idempotency-key-header-07: The Idempotency-Key HTTP Header Field","publisher":"Internet Engineering Task Force","url":"https://datatracker.ietf.org/doc/html/draft-ietf-httpapi-idempotency-key-header","source_type":"OFFICIAL_STANDARD","claims_supported":["This standards-track Internet-Draft specifies fingerprints, key validity and expiry, completed-result replay, payload-mismatch errors, and conflict responses for concurrent outstanding requests.","It requires resources to publish their idempotency policy but does not prescribe an internal storage representation or adapter-conformance architecture."]},{"source_id":"SRC2","title":"idemlease package documentation","publisher":"repenguin22 via Go Packages","url":"https://pkg.go.dev/github.com/repenguin22/idemlease@v1.1.0","source_type":"FIRST_PARTY_PRODUCT","claims_supported":["Implements a storage-agnostic lease-based idempotency state machine with opaque keys, fingerprints and payloads, Begin and Finish operations, claim tokens, expiry, replay, in-flight rejection, fingerprint mismatch, completion and release.","Provides memory, Redis and PostgreSQL stores behind a pluggable Store interface.","Ships shared RunStoreTests, RunStateMachineTests and RunHTTPTests conformance suites that pin atomicity, expiry, token compare-and-swap behavior and client-observable outcomes.","States the bounded guarantee that at most one execution holds a valid lease for a scoped key, while identifying re-execution risks after lease expiry or persistence failure."]},{"source_id":"SRC3","title":"Idempotent requests","publisher":"Stripe","url":"https://docs.stripe.com/api/idempotent_requests","source_type":"FIRST_PARTY_PRODUCT","claims_supported":["Stripe stores and replays the first result for a key, including failures.","It rejects reuse with different parameters, distinguishes requests that conflict with a concurrently executing request, and permits new execution after records are pruned.","It advises against placing sensitive data in idempotency keys."]},{"source_id":"SRC4","title":"Stateful tests — Hypothesis documentation","publisher":"Hypothesis","url":"https://hypothesis.readthedocs.io/en/latest/stateful.html","source_type":"OFFICIAL_GUIDANCE","claims_supported":["Rule-based stateful testing generates sequences of primitive actions rather than isolated examples.","Its database example executes the same operations against a real implementation and a simplified in-memory behavioral model and checks for discrepancies.","It supports invariants after each generated step and bounded controls for example counts and sequence lengths."]}],"problem_evidence":{"status":"PARTLY_SUPPORTED","finding":"The sources make the underlying problem visible: correctness depends on atomic ownership, in-flight handling, fingerprints, replay, release and expiry rather than merely get/put/delete signatures, and the idemlease documentation explicitly limits guarantees by store type, lease expiry and persistence failure. However, this bounded search did not locate a documented production incident in which replacing one nominally compatible idempotency-registry backend with another caused the proposed duplicate-execution or valid-retry failure.","source_ids":["SRC1","SRC2","SRC3"]},"closest_prior_art":[{"name":"idemlease lease-based idempotency state machine and conformance suites","source_ids":["SRC2"],"overlap":"Substantially matches the proposed core: a storage-agnostic state machine, opaque values and claim tokens, Begin/Finish corresponding to claim/complete/release, scoped at-most-one valid lease, explicit replay/in-flight/fingerprint/expiry outcomes, memory/Redis/PostgreSQL implementations, and shared store, state-machine and externally observable conformance suites.","remaining_difference":"The proposal additionally emphasizes an observe operation, representation-leakage probes, explicit contract versioning and migration review, declared consistency/clock/capacity envelopes, and a mirrored substitution canary. The source does not establish that these additions materially improve its already-close contract and test architecture."},{"name":"IETF Idempotency-Key enforcement semantics","source_ids":["SRC1"],"overlap":"Defines representation-independent external outcomes for first use, completed replay, concurrent outstanding requests, fingerprint mismatch and expiration policy.","remaining_difference":"It is an HTTP-facing work-in-progress specification, not an internal registry interface with claim tokens or a shared adapter-qualification suite."},{"name":"Hypothesis rule-based stateful differential testing","source_ids":["SRC4"],"overlap":"Provides the proposed mechanism of generating operation sequences, maintaining an abstract model, exercising a real storage implementation and detecting behavioral discrepancies and invariant violations.","remaining_difference":"It is a general testing framework and example, not an idempotency-registry contract or concurrent multi-backend qualification suite."},{"name":"Stripe idempotent-request behavior","source_ids":["SRC3"],"overlap":"Implements result replay, fingerprint-equivalent parameter checking, concurrent-conflict treatment and record expiration in a deployed service.","remaining_difference":"It specifies one provider's observable API behavior and does not expose a substitutable registry adapter boundary or its conformance tests."}],"prior_art_disposition":"SUBSTANTIAL_COLLISION","contrastive_claim_remaining":"Relative to the already-close idemlease architecture, adding explicit observe semantics, representation-leakage probes, versioned deployment envelopes and a mirrored backend-substitution canary will detect contract-relevant adapter differences that its shipped store, state-machine and HTTP conformance suites do not detect.","contrastive_claim_falsifier":"Run the candidate's additional leakage, envelope and mirrored-trace checks alongside the existing idemlease conformance suites on the same two isolated adapters; the remaining claim is falsified if the added checks expose no distinct observable obligation or mismatch, or if every purported additional obligation is already enforced by the existing suites.","gates":{"adequate_source_search":{"status":"PASS","rationale":"The search covered direct terminology, older deduplication and idempotent-receiver language, an IETF standards-track draft, deployed first-party behavior, pluggable memory/Redis/PostgreSQL products, lease-based state machines, and model-based sequence testing. Four direct sources from four publisher identities were retained and opened.","source_ids":["SRC1","SRC2","SRC3","SRC4"]},"supported_problem":{"status":"PASS","rationale":"The behavioral dimensions and duplicate-execution risk are directly supported, while the specific backend-replacement incident scenario is only indirectly supported; this satisfies the partly-supported threshold.","source_ids":["SRC1","SRC2","SRC3"]},"distinct_testable_claim":{"status":"PASS","rationale":"Although the core intervention substantially collides with idemlease, a narrow marginal claim remains testable: whether leakage probes, explicit deployment envelopes and a mirrored substitution canary find differences beyond its existing conformance suites.","source_ids":["SRC2","SRC4"]},"bounded_next_test":{"status":"PASS","rationale":"A finite comparison using at most 200 traces of at most 20 operations against two isolated adapters can run both the existing idemlease suites and the candidate's additional probes, recording only differential outcomes, invariant violations and added coverage.","source_ids":["SRC2","SRC4"]},"no_obvious_safety_or_authority_stop":{"status":"PASS","rationale":"Synthetic scoped keys, inert payloads, isolated stores, bounded traces and no production write admission keep the test reversible and within platform-test authority. Sensitive request data must remain excluded, and the test must halt on external side effects or environment spillover.","source_ids":["SRC2","SRC3"]}},"screen_survival":false,"world_novelty_boundary":"This bounded four-source screen found a substantial public collision and therefore rejects screen survival; it does not determine world novelty, patentability, market size, expert acceptance, production substitutability or realized value. Unsearched patents, repositories, papers, internal systems and older implementations may contain additional or closer prior art."}