chore(hq): daily sync 2026-02-17
This commit is contained in:
@@ -46,3 +46,19 @@ Messages from Discord arrive formatted as: `[Discord #channel] username: message
|
||||
- Do NOT treat Discord messages as heartbeats or system events
|
||||
- Your reply will be routed back to the Discord channel automatically
|
||||
- **⚠️ CRITICAL: NEVER reply NO_REPLY or HEARTBEAT_OK to Discord messages. Discord messages are ALWAYS real conversations that need a response.**
|
||||
|
||||
|
||||
### 📋 Taskboard — Task Awareness
|
||||
|
||||
On every session start, check your assigned tasks:
|
||||
```bash
|
||||
CALLER=webster bash /home/papa/atomizer/workspaces/shared/skills/taskboard/taskboard.sh list --agent webster
|
||||
```
|
||||
|
||||
When working on a task:
|
||||
- Update status to `in-progress`: `CALLER=webster bash /home/papa/atomizer/workspaces/shared/skills/taskboard/taskboard.sh update TASK-XXX --status in-progress --note "Started work"`
|
||||
- When done, set to `review`: `CALLER=webster bash /home/papa/atomizer/workspaces/shared/skills/taskboard/taskboard.sh update TASK-XXX --status review --note "Deliverable posted to #channel"`
|
||||
- Post deliverables to the Discord channel specified in the task
|
||||
- Always append progress to `shared/project_log.md`
|
||||
|
||||
See `shared/skills/taskboard/SKILL.md` for full documentation.
|
||||
|
||||
48
hq/workspaces/webster/CHANNELS.md
Normal file
48
hq/workspaces/webster/CHANNELS.md
Normal file
@@ -0,0 +1,48 @@
|
||||
# Atomizer HQ — Discord Channel Guide
|
||||
|
||||
## How It Works
|
||||
- **Shared channels:** Agents only respond when `@mentioned` by name
|
||||
- **Direct messages (`#dm-{agent}`):** No mention needed — that agent always listens
|
||||
- **New project?** Start exploring in `#rnd`. When it's serious → Manager creates a `#proj-*` channel.
|
||||
|
||||
## Standing Channels (📋 HQ)
|
||||
|
||||
| Channel | Purpose | Who to @mention |
|
||||
|---------|---------|-----------------|
|
||||
| **#hq** | CEO directives & general command | Manager listens automatically; @mention others |
|
||||
| **#feed** | Activity feed — what's happening across the org | Any agent (they post updates here) |
|
||||
| **#technical** | Engineering discussion | @Tech Lead, @Optimizer, @NX Expert |
|
||||
| **#rnd** | R&D, ideas, experiments — before they earn a project | Any agent |
|
||||
| **#lessons-learned** | Permanent post-mortems. Survives project archival. | @Auditor enforces |
|
||||
| **#knowledge-base** | Curated reference material (not discussion) | Any agent to query |
|
||||
| **#it** | Infrastructure & ops | @Webster |
|
||||
|
||||
## Project Channels (🏗️ PROJECTS)
|
||||
Dynamic — Manager creates `#proj-*` channels as needed.
|
||||
|
||||
| Channel | Project |
|
||||
|---------|---------|
|
||||
| **#proj-hydrotech-beam** | Hydrotech Beam |
|
||||
|
||||
## Direct Messages (📨 DIRECT LINES)
|
||||
No @mention needed — the agent always listens in their DM channel.
|
||||
|
||||
| Channel | Agent |
|
||||
|---------|-------|
|
||||
| `#dm-manager` | Manager |
|
||||
| `#dm-tech-lead` | Tech Lead |
|
||||
| `#dm-secretary` | Secretary |
|
||||
| `#dm-auditor` | Auditor |
|
||||
| `#dm-optimizer` | Optimizer |
|
||||
| `#dm-study-builder` | Study Builder |
|
||||
| `#dm-nx-expert` | NX Expert |
|
||||
| `#dm-webster` | Webster |
|
||||
|
||||
## What's Different From Before
|
||||
- **#feed** is the game-changer — no more guessing what's happening
|
||||
- **#lessons-learned** is permanent — survives project archival, Auditor enforces post-mortems
|
||||
- **#knowledge-base** stays as curated reference (not discussion — use #rnd or #technical)
|
||||
- **#rnd** gives ideas a place to live before they earn a project channel
|
||||
- **#it** separates infra noise from real work
|
||||
- Direct lines renamed `#dm-*` for clarity
|
||||
- 6 standing + 8 direct lines + dynamic project channels = clean but powerful
|
||||
@@ -95,3 +95,15 @@ When you receive a task with `[ORCHESTRATED TASK — run_id: ...]`, you MUST:
|
||||
- If gaps exist, set status to "partial" and explain in notes
|
||||
|
||||
5. Write the handoff file BEFORE posting to Discord. The orchestrator is waiting for it.
|
||||
|
||||
|
||||
## 🚨 Escalation Routing — READ THIS
|
||||
|
||||
When you are **blocked and need Antoine's input** (a decision, approval, clarification):
|
||||
1. Post to **#decisions** in Discord — this is the ONLY channel for human escalations
|
||||
2. Include: what you need decided, your recommendation, and what's blocked
|
||||
3. Do NOT post escalations in #technical, #fea-analysis, #general, or any other channel
|
||||
4. Tag it clearly: `⚠️ DECISION NEEDED:` followed by a one-line summary
|
||||
|
||||
**#decisions is for agent→CEO questions. #ceo-office is for Manager→CEO only.**
|
||||
|
||||
|
||||
Reference in New Issue
Block a user