Cairnscale working example
When the same event arrives twice.
A duplicate delivery is an ordinary integration failure. This small check makes its effect on stock and reporting visible.
Replay and recover
Run the five-row order fixture twice. Both runs start from the same stock snapshot and return £9. Event e2 is delivered twice and applied once. Change the value on the second e2 and the checker flags a conflicting event for a person to review.
Download the editable order ledger (CSV) and the reconciliation script (JavaScript) into the same folder. With Node installed, run node fixture.mjs. The inputs are invented and the check runs locally.
Before connecting a real system
Agree which system owns each value, who can change access and where the source and recovery copy may be held. The production design also needs durable event storage, access tests and a restore rehearsal. For AI-assisted decisions, agree labelled examples, an error threshold and who reviews an uncertain result.
Discuss a similar job
The systems involved, the decision that needs a person and any hosting or access constraints.
We work entirely online. A description is enough to start. Keep records, credentials and attachments for the transfer method we agree.
Start an email enquiryEnquiry privacy · hello@cairnscale.uk