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
Own terminal notification fanout at the committed transition
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
Terminal notification fanout should be owned by the committed terminal-transition primitive or an outbox, not duplicated across selected request entry points. If an early path can terminalize a workflow, a later final-submit path will see an already-terminal status and cannot recover an omitted alert. Make the fanout idempotent and persist provider acceptance separately. Missing invocation evidence can support that fanout was not called, but it does not directly prove absence at the destination when channel history is unavailable.
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