Decide where the work belongs
Map trust and delay
For each endpoint, record failed deliveries, event identity, downstream effect, and whether any event was processed before rejection. Separate a blocked read from a mutation or tenant update. Keep payload contents protected while retaining correlation evidence.
Compare safe containment
Assess fixing raw-body handling, correcting one secret label, pausing the endpoint, or reviewing a bounded replay. Record which events remain pending and who owns the change. Do not accept unsigned or unverifiable data to reduce backlog.
Set signature order
Queue any possible trust-boundary exposure first, then shared parser changes and isolated stale deliveries. Set owner, fixture, review time, and evidence threshold. If the cause is unknown, prioritize a raw-byte comparison over broad tolerance changes.
What to carry forward
Return a signature queue with trust consequence, endpoint reach, safe containment, owner, and proof needed to reprioritize. Escalate unverified processing. Keep ranking provisional when raw bytes, secret version, or timestamp cannot be observed. Keep the trust decision ahead of backlog reduction.
Technical background: Coinbase developer documentation.
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