Deterministic simulation that classifies the retry-safety of external side effects. Never claims exactly-once.
-
Updated
Aug 4, 2026 - TypeScript
#
retry-safety
Here are 7 public repositories matching this topic...
Retry Safety Analyzer: deterministic HIGH/MEDIUM/SAFE when a side-effecting tool may have been retried. Offline import — never executes the trace. HIGH is risk, not proof. External validation open.
electron python idempotency local-first otlp langfuse llm-agents openinference agent-traces retry-safety
-
Updated
Aug 19, 2026 - Python
Execution safety for side-effecting AI agent tools.
distributed-systems mcp ai-agents idempotency crewai langgraph model-context-protocol agent-safety retry-safety safe-retries
-
Updated
Nov 5, 2026 - JavaScript
Enterprise idempotency kernel -- side effects under retries run exactly once. Payload fingerprinting, fence tokens, Postgres CAS, async-first.
-
Updated
Aug 12, 2026 - Python
Drop-in idempotency layer for POST endpoints: atomic Redis claiming, byte-identical replay, in-flight collapsing. Proof asserted in tests: 50 concurrent duplicate payment requests, exactly one charge. Includes the crash-window test middleware demos hide, closed with a DB uniqueness constraint (ADR explains which layer owns which guarantee).
python redis distributed-systems lua postgresql payments idempotency fastapi api-reliability retry-safety
-
Updated
Aug 12, 2026 - Python
Sashank Singh Digital Perspectives — technical writing about agent workflow testing, retry safety and software reliability.
-
Updated
Oct 26, 2026 - TypeScript
Idempotency kernel for TypeScript. 1,000 racing callers, exactly one execution — proven under forced races, zero dependencies.
-
Updated
Sep 4, 2026 - TypeScript
Add this topic to your repo
To associate your repository with the retry-safety topic, visit your repo's landing page and select "manage topics."