Skip to content

ref(chat): Enforce service Slack boundary#317

Open
dcramer wants to merge 1 commit intomainfrom
ref/chat-service-slack-boundary
Open

ref(chat): Enforce service Slack boundary#317
dcramer wants to merge 1 commit intomainfrom
ref/chat-service-slack-boundary

Conversation

@dcramer
Copy link
Copy Markdown
Member

@dcramer dcramer commented May 9, 2026

Enforce the chat architecture rule that domain services should not import Slack infrastructure directly. The service layer now depends on small injected ports for Slack-backed image hydration, while Slack and chat SDK details stay in the composition/runtime layer.

Architecture Boundary

Adds a dependency-cruiser rule preventing src/chat/services from importing src/chat/slack, and records the rule in the local agent instructions and chat architecture spec.

Service Cleanup

Moves chat SDK thread backfill handling into turn preparation and narrows the vision service dependency from Slack-specific helpers to listThreadReplies and downloadFile ports.

Move Slack-backed conversation image and backfill details out of domain services so services depend on small injected ports instead of Slack infrastructure. Add an architecture guard and update the contract docs to keep the boundary enforceable.

Co-Authored-By: GPT-5 Codex <codex@openai.com>
@vercel
Copy link
Copy Markdown

vercel Bot commented May 9, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
junior-docs Ready Ready Preview, Comment May 9, 2026 11:19pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant