eda: scope Channel and Forge action positions (investigation, blocked on execution-time gaps) #442

Closed
opened 2026-10-27 13:36:20 +00:00 by sam · 0 comments
Owner

Investigation ticket -- decide the typed-contract shape for the two remaining named action positions (Channel, Forge) before implementing either. Blocked on archie-core-t2db.17 (idempotency) since both are naturally side-effecting positions; investigation/scoping can proceed now, implementation cannot land before .17 resolves.

Grounded by a crew investigation pass (2026-09-03): Channel already exists as internal/channels.Channel (embeds gateway.Gateway + ConfigSchema/ValidateConfig, telegram/email/webhook implementations registered at daemon startup). Forge already exists as internal/forge.Forge = IssueForge + PullRequestForge + RepoForge, with New(...) switching on github/gitea/none; the daemon poller currently special-cases forge operations directly rather than through any addressable position.

Design

See docs/prds/channel-forge-positions.md (committed 2026-09-03). Forge is fully scoped and ready to implement once t2db.17 lands: native-Go-by-name (not Module-kind) over the existing internal/forge.Forge interface, close-issue/link-branch as the safe first operations, create-pr deferred. Channel is NOT resolved -- the crew investigation's assumption that channels.Channel has an addressable send capability is FALSE (verified: only Name/Start/Stop + config validation exist, no Send method anywhere in internal/channels or internal/gateway). This is now an open product/architecture decision for Sam: whether 'Channel action' means (1) a new playbook-scoped notification capability distinct from the interactive chat channels, or (2) reusing the interactive channels with some new conversation-scoping mechanism for a non-chat trigger. Do not implement a Channel position until Sam decides which.

Acceptance criteria

A design-doc addition (new docs/prds/ file or a section in eda-playbook-engine.md, your call which fits better -- state why) resolving: typed-contract shape for each position, Args/Result shapes, and the host-access/resolution mechanism. No implementation in this ticket.

Close reason

Channel resolved in docs/prds/channel-forge-positions.md (commit 44dde189): notification is a messaging-domain contract, not a channel type; destinations configured in [notify], never named by a playbook; delivery over the existing Gateway connection as a new ChatService server-streaming RPC. Forge was already scoped. Implementation of either position is blocked on archie-core-t2db.24 (the playbook_dispatches ledger). PRD status is Draft, pending Sam's approval.


Imported from beads archie-core-t2db.19 · GitHub #737 · type task · priority P2 · created 2026-09-02 · closed 2026-09-21

Investigation ticket -- decide the typed-contract shape for the two remaining named action positions (Channel, Forge) before implementing either. Blocked on archie-core-t2db.17 (idempotency) since both are naturally side-effecting positions; investigation/scoping can proceed now, implementation cannot land before .17 resolves. Grounded by a crew investigation pass (2026-09-03): Channel already exists as internal/channels.Channel (embeds gateway.Gateway + ConfigSchema/ValidateConfig, telegram/email/webhook implementations registered at daemon startup). Forge already exists as internal/forge.Forge = IssueForge + PullRequestForge + RepoForge, with New(...) switching on github/gitea/none; the daemon poller currently special-cases forge operations directly rather than through any addressable position. ### Design See docs/prds/channel-forge-positions.md (committed 2026-09-03). Forge is fully scoped and ready to implement once t2db.17 lands: native-Go-by-name (not Module-kind) over the existing internal/forge.Forge interface, close-issue/link-branch as the safe first operations, create-pr deferred. Channel is NOT resolved -- the crew investigation's assumption that channels.Channel has an addressable send capability is FALSE (verified: only Name/Start/Stop + config validation exist, no Send method anywhere in internal/channels or internal/gateway). This is now an open product/architecture decision for Sam: whether 'Channel action' means (1) a new playbook-scoped notification capability distinct from the interactive chat channels, or (2) reusing the interactive channels with some new conversation-scoping mechanism for a non-chat trigger. Do not implement a Channel position until Sam decides which. ### Acceptance criteria A design-doc addition (new docs/prds/ file or a section in eda-playbook-engine.md, your call which fits better -- state why) resolving: typed-contract shape for each position, Args/Result shapes, and the host-access/resolution mechanism. No implementation in this ticket. ### Close reason Channel resolved in docs/prds/channel-forge-positions.md (commit 44dde189): notification is a messaging-domain contract, not a channel type; destinations configured in [notify], never named by a playbook; delivery over the existing Gateway connection as a new ChatService server-streaming RPC. Forge was already scoped. Implementation of either position is blocked on archie-core-t2db.24 (the playbook_dispatches ledger). PRD status is Draft, pending Sam's approval. --- _Imported from beads `archie-core-t2db.19` · GitHub #737 · type task · priority P2 · created 2026-09-02 · closed 2026-09-21_
sam added the mediumtask labels 2026-10-27 13:36:20 +00:00
sam self-assigned this 2026-10-27 13:36:20 +00:00
sam closed this issue 2026-10-27 13:36:21 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#442