Aglet

How to verify event delivery without silent downstream gaps

Verification must show that a source change produces the expected event and that consumers reach the intended outcome without silently dropping or repeating work. Exercise normal delivery, a controlled failure and retry, replay where supported, and inspect identities, versions, and final state.

Check whether the outcome improved

  1. Follow one event end to end

    Create the representative source change and record source commit, event identifier, type, version, acceptance, consumer claim, handler result, acknowledgment, projection update, and visible outcome. Compare each boundary with the neighboring successful case. Confirm event payload structure without retaining sensitive content.

  2. Exercise failure, retry, and replay

    Cause a controlled producer, transport, consumer, or projection failure at one boundary, then allow retry or safe replay. Confirm the event is not lost, the consumer is idempotent, and final state appears once. Record how a permanent failure becomes visible and reviewable.

  3. Check ordering and downstream completeness

    Deliver related events with a delayed or failed member and verify required sequence, version, projection fields, notifications, audit entries, and API visibility. Exercise empty or filtered outcomes where relevant. Confirm an event that is valid but not needed does not create an incorrect downstream change.

What to carry forward

Classify delivery as complete, regressed, unchanged, or inconclusive with boundary, identity, retry, and final-state evidence attached. It passes only when expected events are traceable, failures are recoverable or explicit, downstream effects occur once, and no silent gap remains.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow