Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Verify campaign attribution in three independent windows
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
Treat a time-bounded messaging campaign as three independently verifiable behaviors: eligibility or ledger attribution, outbound delivery, and inbound reply attribution. A deployed flag proves none of them. Check code-owned half-open boundaries, then query aggregate persisted evidence for each lane. Keep ledger totals separate from delivery totals because attribution may be retained when delivery is not queueable. A reply tail may extend beyond the outbound window and should have its own boundary. Persisted provider acceptance is not end-device receipt. Without provider and runtime evidence, transport health and delivery remain unverified.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review