# DN Agent Retry Boundary Lab v0.1
+
+Published 3 November 2026. Eight fixed event sequences, each executed against two abstract designs. This is a deterministic single-process ordered simulation, not a payment protocol or production implementation.
+
+Completed-response cache model: key = principal plus payment key; completed fingerprints are checked; no in-flight reservation; response entries disappear on the explicit expiry event. An admitted arrival commits one abstract effect before its completion record.
+
+Reserved logical-operation ledger model: key = principal plus logical operation; atomic admission before the abstract effect; retained payment-key/fingerprint binding; durable operation state survives response-cache expiry. Same-operation arrivals either replay completion or block while in flight/uncertain. A lost-completion event leaves an unresolved operation and does not prove recovery.
+
+Fingerprints include logical-operation ID, destination, amount and asset. All identities and authorizations are invented and assumed valid. Distinct principals are separate scopes. Two effects for two different principals are not counted as a duplicate. Duplicate effects count additional effects for the same principal and logical-operation ID.
+
+The durable ledger, atomic admission and stable logical IDs are assumptions, not capabilities tested by these scripts. The model does not test actual parallel threads, databases, process death, distributed locks, storage loss, network partitions, signatures, provider API behavior or settlement. A production design must reconcile external side effects and uncertain outcomes. The local model is not a drop-in gate for payments.
+
+Files: scenarios.json declares schedules and assumptions; model.mjs is the exact standalone model; results.json contains 16 executed cases and expected counts; results.csv provides the comparison; reproduce.mjs rechecks the declared expectations. Download model.mjs, results.json and reproduce.mjs into one folder and run `node reproduce.mjs`. No dependencies or network are required. Results include the SHA-256 of model.mjs. A source hash is not a trusted timestamp or publisher signature.
+
+No model calls, paid requests, provider calls, signatures or real payments were used in the local execution. These 16 cases are not a reliability rate or a vendor score.
+
+License: CC BY 4.0. Attribute Decentralised News, link to https://decentralised.news/ai-agent-idempotency-retry-risk and retain the limitations. Native provider documentation and third-party artifacts retain their own terms. Submit corrections through the DN Contact page with a scenario identifier and reproducible evidence.
+