Add built‑in discussions and chat, similar to GitHub Discussions and Slack, but fully native to the system. Conversations should be connected directly to tasks, branches, functions, logs, and documentation—not split across external tools.
The goal is to make progress easy to track and verify, without relying on Discord or Slack, which often create human‑in‑the‑loop delays and lost context.
Core Goals:
- Conversations live with the work
- Context is always attached
- Progress is visible and traceable
Requirements:
Discussion Threads:
- Long‑form discussions (like GitHub Discussions)
- Can be attached to:
- Tasks / issues
- Branches
- Functions or groups of functions
- Docs and design notes
- Support references between discussions and tasks
Chat:
- Short, real‑time or async chat (Slack‑like)
- Messages can reference:
- Tasks
- Functions
- Logs
- Commits
- Chat messages are not lost—they stay linked to context
Native Linking:
- One click to:
- Jump from a task to related discussion
- Jump from discussion to affected code
- No copy‑paste of links between tools
- References are first‑class objects, not plain text
Progress & Verification:
- Ability to see:
- What is being discussed for a task
- What decisions were made
- What code/logs support those decisions
- Reduce “lazy work” caused by:
- Context switching
- Re‑explaining the same thing
- Unverifiable chat messages
History & Search:
- Discussions and chat are searchable
- Conversations remain readable over time
- Clear timeline tied to task and code changes
Acceptance Criteria:
- No need for external chat tools
- Discussions are easy to follow later
- Tasks show real, visible progress
- Conversations improve clarity instead of creating noise
Notes:
This system treats communication as part of the code graph, not as disposable messages. Talking about work should be as structured and traceable as doing the work.
Add built‑in discussions and chat, similar to GitHub Discussions and Slack, but fully native to the system. Conversations should be connected directly to tasks, branches, functions, logs, and documentation—not split across external tools.
The goal is to make progress easy to track and verify, without relying on Discord or Slack, which often create human‑in‑the‑loop delays and lost context.
Core Goals:
Requirements:
Discussion Threads:
Chat:
Native Linking:
Progress & Verification:
History & Search:
Acceptance Criteria:
Notes:
This system treats communication as part of the code graph, not as disposable messages. Talking about work should be as structured and traceable as doing the work.