Create the ARCHIE_REACTIONS fan-out stream #1170
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#1170
Reference in new issue
Block a user
Create the ARCHIE_REACTIONS JetStream stream under the fan-out
jetstream.LimitsPolicy, alongside the existing ARCHIE_TASKS stream.
Step 1 of docs/prds/pr-review-remediation.md. The parent decision
(docs/prds/event-sources-and-reactions.md section 2) already requires a second
stream with fan-out retention, and archie-core-7d5u.2 parameterised
Config.Retention for exactly this, but no reaction stream exists.
bootstrap.go:501-502 binds the only stream to archie.task.> under
WorkQueuePolicy, so any publish to archie.reaction.* fails against no matching
stream: js.PublishMsg returns an error and the caller sees it as a publish
failure.
This is first because nothing after it can be exercised without it. PR #859
built a reaction producer without it and every webhook delivery would have
answered HTTP 500.
Acceptance: a publish to archie.reaction.* lands in ARCHIE_REACTIONS; two
consumers on overlapping filter subjects both receive it (the fan-out property
WorkQueuePolicy cannot provide, per the trap in CLAUDE.md).
Notes
2026-09-19 analysis: this bead is DONE in code — PR #875 (merged, commit
9e8427bc) provisioned the ARCHIE_REACTIONS stream under LimitsPolicy and TestConnectNATSCreatesReactionStream/TestReactionStream* pins all three acceptance criteria (publish lands; LimitsPolicy; two consumers on overlapping filters both receive) in internal/app/archied/reaction_stream_test.go, green on origin/main. It was left in_progress only because another session holds the lease. Close when that session releases it.Close reason
Closed
Imported from beads
archie-core-8li9.1· GitHub #915 · type feature · priority P1 · created 2026-09-18 · closed 2026-09-18