archie-core-7d5u.1 -- closes with the decision recorded. Investigated three
mechanisms already in the tree rather than designing from scratch:
- No out-of-process extension boundary exists or is needed; in-process typed
families throughout, and plugins-and-extensions.md does not need amending.
- Reaction delivery reuses internal/eventbus's Publisher/Consumer contract,
but NOT the existing nats.Client unmodified: it hardcodes
jetstream.WorkQueuePolicy (client.go:65), the competing-consumer policy
correct for ARCHIE_TASKS and wrong for fan-out reactions -- two reactions on
overlapping subjects would hit the exact silent-starvation trap CLAUDE.md
already documents. Retention needs to become a Config field; reactions get
a second stream.
- Reactions in these two epics are producer-only (curator's WakeOnPrimaryInput
for cheap wake, or the existing pollNATS->publishTask shape for real work).
No veto/mutate-in-flight capability is being built here.
- No single generic Source interface. workintake.TaskEnvelope already is
forge intake's typed contract and needs no new type -- its IdempotencyKey is
keyed on owner/repo/number, not delivery source, so a webhook-sourced
envelope dedups against a poll-discovered one for free. What's genuinely
shared is a small cross-cutting package for HMAC/rate-limit/capture/approval
mechanics, owned by neither domain.
Retitled and rescoped archie-core-7d5u.3 to match: it was still asking for
'one registry for every kind of inbound caller,' which this decision
explicitly rejects. Removed a false blocking dependency of t2db.1 on 7d5u.4
(GitHub-specific receiver) -- they are siblings sharing the new cross-cutting
package, not a chain -- and linked them instead.