Decision: project channels stay primary interface for Hermes and Claude Code

Decision

Henry chose a single-project-channel workflow for the new agent stack. Each project channel remains the main mental container. Hermes/project agent owns normal channel interaction, while Claude Code is invoked inside that same channel/thread for dev/gstack sessions. We will not create separate dev-only Claude Code channels per project.

Architecture

• Project channel: Henry + Hermes project agent + invoked Claude Code agent
• gbrain: shared memory/retrieval
• Paperclip: task/dependency/governance state
• Claude Code: interactive dev/gstack cockpit, invoked explicitly

Implementation Plan

Documented in private repo widerwings-inc/widerwings-agent-infra at docs/project-channel-agent-architecture.md.

Rationale

Henry already uses project-specific Discord channels for context separation. Splitting dev into separate channels would make context messy and force Henry to choose the tool before the work is understood. The new setup should preserve one project room while routing specialist work under the hood.