---
id: overview-channels
title: "Overview Channels"
description: "Understand how the six Corp v1 project channels divide responsibilities and hand work to one another."
---

import Drawio from '@theme/Drawio';
import channelsDiagram from '!!raw-loader!./diagrams/channels.drawio';

# Overview Channels

A project receives exactly six purpose-specific Discord channels. The channels are concern boundaries, not isolated teams: evidence and decisions move forward through explicit handoffs.

<Drawio content={channelsDiagram} title="Corp v1 project channel flow" toolbar="zoom layers lightbox" responsive maxHeight={720} />

| Channel | Owns | Typical handoff |
|---|---|---|
| General | Announcements, questions, shared coordination | Routes product intent to Scope and broadcasts outcomes |
| Scope | Ideas, Epics, Features, value, acceptance outcomes, solution approval | Sends an approved Feature to Architecture |
| Architecture | Requirements, ADRs, Draw.io views, technical design, implementation Tasks | Sends prepared Tasks to Kanban |
| Kanban | Board, Focus, flow visibility, explicit human Task admission | Sends admitted work to Delivery |
| Delivery | Planning, implementation, pull requests, CI evidence, blockers | Sends a validated release candidate to Releases |
| Releases | Readiness, versions, deployment, rollback, post-release outcomes | Reports deployment state and outcomes to the project |

Each channel loads its mapped project-adopted channel skill. Relevant engineering skills are loaded alongside it for branching, monorepo structure, scripts, CI/CD, GitOps, documentation, and templates. A green build or agent statement never substitutes for a required human approval or deployed readback.