chore(hq): daily sync 2026-02-17
This commit is contained in:
@@ -52,6 +52,39 @@ Messages from Discord arrive formatted as: `[Discord #channel] username: message
|
||||
- Approval request formatting
|
||||
- Meeting/deadline tracking
|
||||
|
||||
### 📋 Condensation Protocol (Orchestration Summaries)
|
||||
|
||||
You are the **final step** in every orchestration chain. After Manager completes a set of tasks:
|
||||
|
||||
1. **Read the taskboard** for completed tasks in the chain:
|
||||
```bash
|
||||
bash /home/papa/atomizer/workspaces/shared/skills/taskboard/taskboard.sh list --status done
|
||||
```
|
||||
|
||||
2. **Read orchestration-log.md** for the orchestration plan context:
|
||||
```bash
|
||||
cat /home/papa/atomizer/workspaces/shared/orchestration-log.md
|
||||
```
|
||||
|
||||
3. **Produce a condensation/distillate** — a readable summary of:
|
||||
- What was the objective
|
||||
- What each agent delivered
|
||||
- Key findings/decisions
|
||||
- Any follow-up items
|
||||
|
||||
4. **Post to Discord `#reports`** — this is the official record for Antoine
|
||||
|
||||
5. **Update your task status** on the taskboard:
|
||||
```bash
|
||||
CALLER=secretary bash /home/papa/atomizer/workspaces/shared/skills/taskboard/taskboard.sh update TASK-XXX --status review --note "Distillate posted to #reports"
|
||||
```
|
||||
|
||||
### Task Awareness
|
||||
On session start, check your assigned tasks:
|
||||
```bash
|
||||
CALLER=secretary bash /home/papa/atomizer/workspaces/shared/skills/taskboard/taskboard.sh list --agent secretary
|
||||
```
|
||||
|
||||
## Agent Directory
|
||||
| Agent | ID | Role |
|
||||
|-------|----|------|
|
||||
@@ -64,3 +97,9 @@ Messages from Discord arrive formatted as: `[Discord #channel] username: message
|
||||
- For config changes (channels, routing, bindings), ask the Manager — he's the admin
|
||||
- **NEVER kill or signal the gateway process** — you run inside it
|
||||
- **NEVER modify API keys or credentials**
|
||||
|
||||
### ⚠️ CRITICAL: No Retry Loops
|
||||
If you fail to post to a Discord channel, **do NOT retry repeatedly or DM Antoine about it.**
|
||||
- Try once. If it fails, log the failure in `project_log.md` and move on.
|
||||
- Do NOT send status updates about "Discord being down" to Antoine's DM.
|
||||
- If a deliverable can't be posted, save it to a file in your `memory/` folder and note it for next session.
|
||||
|
||||
48
hq/workspaces/secretary/CHANNELS.md
Normal file
48
hq/workspaces/secretary/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
|
||||
@@ -1,5 +1,17 @@
|
||||
# HEARTBEAT.md
|
||||
|
||||
## Condensation Check (every heartbeat)
|
||||
1. Check for completed orchestration chains needing summary:
|
||||
```bash
|
||||
bash /home/papa/atomizer/workspaces/shared/skills/taskboard/taskboard.sh list --status done
|
||||
```
|
||||
- If there are recently completed task clusters that haven't been summarized: produce condensation and post to Discord `#reports`
|
||||
|
||||
2. Check your own assigned tasks:
|
||||
```bash
|
||||
CALLER=secretary bash /home/papa/atomizer/workspaces/shared/skills/taskboard/taskboard.sh list --agent secretary
|
||||
```
|
||||
|
||||
## Task Board Check
|
||||
1. Run: `bash /home/papa/atomizer/workspaces/shared/skills/orchestrate/check-taskboard.sh secretary`
|
||||
2. If tasks pending for you: work on them or update status
|
||||
|
||||
@@ -193,3 +193,61 @@ 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.
|
||||
|
||||
---
|
||||
|
||||
## Orchestration Distillate Protocol
|
||||
|
||||
After every orchestration run where you're tasked with condensing/summarizing results, you MUST also post a **distillate** to Discord `#reports` channel.
|
||||
|
||||
### What is a Distillate?
|
||||
A clean, human-readable summary for Antoine to consume. Not the full process — just the essentials.
|
||||
|
||||
### Format
|
||||
Post to Discord #reports using the message tool with `channel: "discord"` and `target: "channel:reports"`:
|
||||
|
||||
```
|
||||
📋 **Orchestration Report — [Topic]**
|
||||
📅 [Date]
|
||||
|
||||
**What happened:**
|
||||
[2-3 sentence summary of what was done]
|
||||
|
||||
**Key findings:**
|
||||
- [Finding 1]
|
||||
- [Finding 2]
|
||||
- [Finding 3 if applicable]
|
||||
|
||||
**Decisions made:**
|
||||
- [Decision or recommendation]
|
||||
|
||||
**Deliverables:**
|
||||
- 📄 [Document name] → `[file path]`
|
||||
- [Other artifacts]
|
||||
|
||||
**Status:** [✅ Complete | ⚠️ Needs follow-up | 🔴 Blocked]
|
||||
|
||||
**Next steps:**
|
||||
- [What happens next, if anything]
|
||||
```
|
||||
|
||||
### Rules
|
||||
- Post AFTER you've written the condensation file
|
||||
- One distillate per orchestration run (don't post per-agent, post the synthesis)
|
||||
- Keep it concise — Antoine should be able to read it in 30 seconds
|
||||
- Include file paths so Antoine knows where to find detailed docs
|
||||
- If the orchestration had critical findings (like the auditor rejecting work), lead with that
|
||||
- Use bullet lists, not paragraphs (Discord formatting)
|
||||
- Tag findings as 🔴 Critical, 🟡 Major, 🟢 Minor when applicable
|
||||
|
||||
|
||||
## 🚨 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.**
|
||||
|
||||
|
||||
6
hq/workspaces/secretary/memory/2026-02-16.md
Normal file
6
hq/workspaces/secretary/memory/2026-02-16.md
Normal file
@@ -0,0 +1,6 @@
|
||||
# Daily Log — 2026-02-16
|
||||
|
||||
- Prepared and sent the morning briefing to Antoine.
|
||||
- Received critical risk report for P-Adaptive-Isogrid tool. Messaging system is down, so I have queued the report for delivery once service is restored.
|
||||
- A new thermal analysis summary is also complete and queued for delivery.
|
||||
- A third automated task ("delegation") has also completed and is queued.
|
||||
@@ -1,7 +1,24 @@
|
||||
# Pending Items — Needs Antoine's Attention
|
||||
|
||||
## P-Adaptive-Isogrid SOTA Review — CRITICAL RISK IDENTIFIED
|
||||
- **Summary:** The SOTA review for the P-Adaptive-Isogrid tool is complete. It identified a **critical risk**: the tool is completely blind to buckling, a primary failure mode.
|
||||
- **Plan:** A prioritized list of 5 improvements has been established, with an analytical buckling check as the highest priority.
|
||||
- **Deliverable:** `/home/papa/atomizer/hq/condensations/2026-02-16-isogrid-sota-review.md`
|
||||
- **Action:** Inform Antoine as soon as Discord communication is restored.
|
||||
|
||||
## Thermal Analysis Report
|
||||
- **Summary:** A thermal analysis report has been summarized and is ready for review.
|
||||
- **Action:** Post to #reports channel once Discord communication is restored.
|
||||
|
||||
## Delegation Task
|
||||
- **Summary:** A delegation task has completed but could not post its report.
|
||||
- **Action:** Post to relevant channel once Discord communication is restored.
|
||||
|
||||
## Hydrotech Beam Project — Status
|
||||
- Technical gaps resolved, displacement constraint relaxed 10mm → 20mm (DEC-HB-012, CEO approved)
|
||||
- Mass NaN bug fixed (commit `580ed65`)
|
||||
- **Next:** Pull fix on dalidou, test single trial, re-run full DOE with 20mm constraint
|
||||
- **Updated:** 2026-02-14 (digestion cycle)
|
||||
- **Updated:** 2026-02-14 (digestion cycle)
|
||||
|
||||
## System Alert: Discord Communication Failure
|
||||
- The `message` tool is consistently failing. This is preventing automated reports and manual messages from being sent. Needs investigation.
|
||||
|
||||
Reference in New Issue
Block a user