docs: add channels architecture scoping document#3328
Draft
adamleithp wants to merge 6 commits into
Draft
Conversation
Add a scoping doc for the Bluebird channels model: inventory of what already exists (channel folders, CONTEXT.md injection, channel-filed task threads, canvas/PR artifacts, TaskChannel feed), the gaps against the target UX, and eight sized workstreams (unified channel identity, artifact registry, context lifecycle, cross-channel mentions, steering grants, real-time feed, MCP surface, channel organization) with sequencing and open product questions. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CbhUuXuEy319snoLL3KSya
Expand the MCP workstream to cover full thread/transcript access and channel-scoped plus cross-channel search; add natural-language channel creation with ownership negotiation as a v2 item under organization; add a speculative channel-agent workstream (@agent/channel-name) as the capstone over mentions, context lifecycle, and the MCP tools. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CbhUuXuEy319snoLL3KSya
Grow the artifact registry workstream to store artifact content itself (blobs for generated HTML/images/files, snapshots alongside live PR and canvas refs), capture at every ingress, and serve both the UI and agent-context retrieval paths. Add a doc-rot prevention v2 to the context lifecycle: staleness signals from provenance, scout-shaped verification passes, and per-section freshness surfaced in the UI. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CbhUuXuEy319snoLL3KSya
Spell out where the work starts: the client-side channels feature seam in this repo can begin immediately, while canonical channel identity, the artifact model, and the context summarizer land in posthog/posthog first, with the dependency order between the five opening steps. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CbhUuXuEy319snoLL3KSya
Code will ship on web and mobile, so durable names must not bake in "desktop". Client-side code moved or created from now on uses product-os (folder, class, token names) over the legacy desktop_file_system endpoint; the backend endpoint/MCP-domain rename is folded into the channel-identity ADR while aliasing is still cheap. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CbhUuXuEy319snoLL3KSya
|
Merging to
After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here |
Commit the step-1 execution plan as a companion to the architecture doc: what moves from canvas/ into a new packages/core/src/channels/ feature, the product-os rename of the shared fs client, what explicitly stays put, and the verification greps and acceptance criteria. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01CbhUuXuEy319snoLL3KSya
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The channels feature is growing across multiple systems (desktop file-system folders, task-product channels, artifacts, context, mentions) without a unified vision or sequencing plan. This creates risk of duplicated work, architectural debt, and unclear priorities for the team.
Changes
Added
docs/plans/channels-architecture.md, a comprehensive scoping document that:@channel-namepulls context into threadsThe document is grounded in the current codebase (as of July 2026) and marked as a scoping draft behind the
project-bluebirdflag.How did you test this?
N/A — this is a planning document. It was reviewed for consistency with the current codebase structure and dependencies.
Automatic notifications
https://claude.ai/code/session_01CbhUuXuEy319snoLL3KSya