BRASSWIRE LAB #02 · ISSUE #002 RUNS IN YOUR BROWSER · NOTHING IS SENT

Could a retry make your automation write or charge twice?

For small digital businesses that connect forms, CRMs and payment tools with AI steps. See how an extraction step can pass wrong numbers along without any error, and how a strict check plus an idempotency key (one unique ID per event) stops a retried webhook from creating duplicates. About two minutes.

ILLUSTRATIVE SIMULATION · runs entirely in your browser. Invoices, event IDs and amounts are made-up sample data, not measurements.

TEST 01 // STRICT DECIMAL + ARITHMETIC GATE
TEST 02 // A WEBHOOK THAT TIMES OUT AND IS RETRIED

Simulate a downstream CRM timing out 3 times while actually processing event #evt_8841.

0
WEBHOOKS
0
CRM WRITES
0
DUPLICATES
[ledger] Simulated ledger ready (in-memory stand-in for a SQLite table). Toggle the idempotency lock and fire retries.

What this leaves out: real systems fail in more ways than these samples (partial writes, events arriving out of order, keys that expire on the provider's side). This demo uses JavaScript numbers; use a decimal type for money in production. Check each tool's own documented retry behaviour before you rely on it.

STARTER BUILD PROMPTS (PASTE INTO CLAUDE, CURSOR OR A SIMILAR TOOL)

    

Sources & what we checked