Forkline Delivery Lab | PitchFORKLINE / DELIVERY LABThe event vanished.
The ticket did not.
Test the gap between queue approval and outside work. A reproducible local integration for Web3 ticketing, membership and fulfillment developers.
01 / THE FAILUREApproval is not a receipt.
An event can be eligible at enqueue and orphaned at dispatch. A receiver can commit while its acknowledgement is lost. Neither rolling back an index nor blindly retrying resolves both cases.
02 / THE BUILDA real worker. A separate receiver.
Compiled Solidity fixture and pinned EVM observations → shared eligibility engine → SQLite outbox → loopback HTTP receiver → separate ticket ledger. Restart the worker and reconcile its receipt.
03 / THE DIFFERENCEReproduce the failure.
Keep the outside effect.
Same waiting rule, same order: the enqueue-only consumer issues one orphaned fixture ticket; Forkline holds the command. If a ticket already exists, retain its receipt, latch the incident and stop further guarded delivery.
04 / EVIDENCE & NEXT STEPAn integration test you can rerun.
Executed database and HTTP checks include dropped acknowledgements, true child-process death, restart, receipt lookup and duplicate commands. No real assets or field savings. Next: maintained live-node adapter and an authorized developer pilot.