chore(hq): daily sync 2026-02-19
This commit is contained in:
1
hq/workspaces/shared/mc-update.sh
Symbolic link
1
hq/workspaces/shared/mc-update.sh
Symbolic link
@@ -0,0 +1 @@
|
||||
/home/papa/atomizer/mission-control/scripts/mc-update.sh
|
||||
@@ -26,3 +26,5 @@ _Append-only. Manager posts orchestration plans here before delegating work._
|
||||
- Secretary: Summarize findings into a recommendation report.
|
||||
**Dependencies:** Tech Lead's work depends on Webster's output. Secretary's work depends on the Tech Lead's output.
|
||||
**Expected output:** A final recommendation report posted by the Secretary.
|
||||
|
||||
- 2026-02-18 UTC | Manager subagent | Atomizer Project Standardization workflow executed: kickoff posted, specialists delegated (tech-lead/auditor/secretary), package + synthesis files published, final approval request posted.
|
||||
|
||||
@@ -26,3 +26,8 @@
|
||||
[2026-02-17 09:05] [manager] TASK-002: Cancelled — Secretary appears to be stuck; tool error on deliverable. Re-creating as TASK-004 assigned to manager to unblock.
|
||||
[2026-02-17 09:05] [manager] TASK-004: Created — Summarize system test orchestration (replaces TASK-002) (assigned to manager)
|
||||
[2026-02-17 09:05] [manager] TASK-004: Completed — Summary posted to #reports channel.
|
||||
[2026-02-18 23:16] webster: Completed — Secondary research validation report for Atomizer Project Standard (NASA-STD-7009B, ASME V&V 10, ECSS, OpenMDAO, Dakota, design rationale, LLM-native docs, modeFRONTIER).
|
||||
[2026-02-19 00:00] secretary: Completed — Drafted executive synthesis for Atomizer Project Standardization Package; direct #hq post blocked (missing Slack bot token).
|
||||
|
||||
- 2026-02-18 UTC | Standardization package assembled and ready for CEO approval. Files: shared/standardization/2026-02-18-atomizer-project-standardization-package.md ; shared/standardization/synthesis/2026-02-18-secretary-synthesis.md
|
||||
[2026-02-19 00:30 UTC] Auditor: Completed — Atomizer Project Standard spec audit (full report + executive summary)
|
||||
|
||||
69
hq/workspaces/shared/skills/mission-control-protocol.md
Normal file
69
hq/workspaces/shared/skills/mission-control-protocol.md
Normal file
@@ -0,0 +1,69 @@
|
||||
# Atomizer-HQ Mission-Dashboard Protocol
|
||||
|
||||
## Overview
|
||||
The Mission-Dashboard at `http://100.68.144.33:8091` is the **single source of truth** for all Atomizer HQ tasks. All agents MUST use it.
|
||||
|
||||
## Dashboard Location
|
||||
- **URL:** http://100.68.144.33:8091
|
||||
- **Data file:** ~/atomizer/mission-control/data/tasks.json
|
||||
- **CLI tool:** ~/atomizer/mission-control/scripts/mc-update.sh
|
||||
|
||||
## Task Lifecycle
|
||||
```
|
||||
backlog → in_progress → review → done
|
||||
```
|
||||
|
||||
| Status | Meaning |
|
||||
|--------|---------|
|
||||
| `permanent` | Recurring/standing tasks |
|
||||
| `backlog` | Waiting to be worked on |
|
||||
| `in_progress` | Agent is actively working |
|
||||
| `review` | Done, awaiting human review |
|
||||
| `done` | Approved by Antoine |
|
||||
|
||||
## Agent Responsibilities
|
||||
|
||||
### Manager
|
||||
- Creates new tasks (`mc-update.sh add`)
|
||||
- Assigns tasks to agents (via comments)
|
||||
- Moves approved work to `done`
|
||||
- ALL new projects/orchestrations MUST get a dashboard task
|
||||
|
||||
### All Agents
|
||||
- When starting work: `mc-update.sh start <task_id>`
|
||||
- Progress updates: `mc-update.sh comment <task_id> "update"`
|
||||
- Subtask completion: `mc-update.sh subtask <task_id> <sub_id> done`
|
||||
- When finished: `mc-update.sh complete <task_id> "summary"`
|
||||
|
||||
### Secretary
|
||||
- Reviews task board during reports
|
||||
- Flags stale in_progress tasks (>24h no update)
|
||||
|
||||
### Auditor
|
||||
- Verifies completed tasks meet DoD before review
|
||||
|
||||
## CLI Reference
|
||||
```bash
|
||||
MC=~/atomizer/mission-control/scripts/mc-update.sh
|
||||
|
||||
# Add new task
|
||||
$MC add "Title" "Description" [status] [project] [priority]
|
||||
|
||||
# Update status
|
||||
$MC status ATZ-xxx in_progress
|
||||
|
||||
# Add comment
|
||||
$MC comment ATZ-xxx "Progress update: completed phase 1"
|
||||
|
||||
# Mark subtask done
|
||||
$MC subtask ATZ-xxx sub_001 done
|
||||
|
||||
# Complete (→ review)
|
||||
$MC complete ATZ-xxx "Summary of what was done"
|
||||
```
|
||||
|
||||
## Rules
|
||||
1. **No shadow work** — if it's not on the dashboard, it didn't happen
|
||||
2. **Update before Slack** — update the task, THEN discuss in Slack
|
||||
3. **Every orchestration = a task** — Manager creates the task BEFORE spawning agents
|
||||
4. **Comments are the audit trail** — agents log progress as comments, not just Slack messages
|
||||
@@ -0,0 +1,76 @@
|
||||
# Atomizer Project Standardization Package
|
||||
|
||||
Date: 2026-02-18 UTC
|
||||
Owner: Manager (delegated to Tech Lead + Auditor + Secretary)
|
||||
|
||||
## 1) Technical Baseline (from Technical Lead)
|
||||
|
||||
### Scope
|
||||
Define a minimum, enforceable baseline for Atomizer HQ so all agents/workspaces produce consistent, reviewable outputs across engineering, orchestration, and reporting.
|
||||
|
||||
### Standard Components
|
||||
- Required identity files: `SOUL.md`, `IDENTITY.md`, `AGENTS.md`, `MEMORY.md`
|
||||
- Required operational files: `HEARTBEAT.md`, `TOOLS.md`, `USER.md`
|
||||
- Task tracking: taskboard transitions (`todo → in-progress → review/done`)
|
||||
- Logging: append-only updates to `shared/project_log.md`
|
||||
- Technical rigor: assumptions, units, BCs/loads, convergence, confidence in deliverables
|
||||
|
||||
### File/Folder Conventions
|
||||
- Daily notes: `memory/YYYY-MM-DD.md`
|
||||
- Durable lessons: `memory/knowledge/`
|
||||
- Review records: `memory/reviews/`
|
||||
- Shared coordination root: `/home/papa/atomizer/workspaces/shared/`
|
||||
- Manager-owned status docs must not be directly edited by specialists
|
||||
|
||||
### Orchestration Contract
|
||||
- Use `sessions_spawn` for scoped parallel/deep execution
|
||||
- Use `sessions_send` for clarification, handoff, escalation
|
||||
- Every specialist return follows:
|
||||
- `TASK:`
|
||||
- `STATUS: complete | partial | blocked | failed`
|
||||
- `RESULT:`
|
||||
- `CONFIDENCE: high | medium | low`
|
||||
- `NOTES: assumptions/risks/next validation`
|
||||
|
||||
### Acceptance Criteria
|
||||
- Required files present and non-empty
|
||||
- Taskboard updated at start/completion
|
||||
- Deliverables follow structured result contract
|
||||
- Shared log updated with timestamped outcome
|
||||
- No policy boundary violations
|
||||
|
||||
## 2) Audit Standard (from Auditor)
|
||||
|
||||
### Compliance Checks
|
||||
- Intake has scope + owner + deadline + mapped task ID
|
||||
- Manager routing and correct specialist handoff
|
||||
- Decision traceability via taskboard + `project_log.md`
|
||||
- Protocol adherence (no review-chain bypass)
|
||||
- Standardized outputs with assumptions/constraints/risks/repro notes
|
||||
- Proper escalation for blockers
|
||||
|
||||
### Common Failure Modes
|
||||
- Stale task status
|
||||
- Missing explicit ownership
|
||||
- Evidence-free claims
|
||||
- Merge/release before audit pass
|
||||
- Conflicting outputs left unresolved
|
||||
- Wrong channel/result routing
|
||||
|
||||
### Evidence Required
|
||||
- Taskboard transition history
|
||||
- Linked artifacts (plan/logs/metrics/diffs/review note)
|
||||
- Baseline vs final KPI table with units/constraints
|
||||
- Audit log with severity and closure proof
|
||||
- Final communication proof in designated channel/thread
|
||||
|
||||
### Approval Gates
|
||||
1. Intake gate
|
||||
2. Execution evidence gate
|
||||
3. Audit gate (PASS or CONDITIONAL with closure)
|
||||
4. Release gate (manager confirms critical/major closure)
|
||||
|
||||
## 3) Delivery Status
|
||||
- Package assembled and published to shared workspace
|
||||
- Team workflow pattern standardized for future projects
|
||||
- Ready for CEO approval and enforcement
|
||||
@@ -0,0 +1,23 @@
|
||||
# Executive Synthesis — Atomizer Project Standardization Package
|
||||
|
||||
Published by: Secretary (content prepared), relayed in Slack by Manager due current secretary direct-post token limitation.
|
||||
Date: 2026-02-18 UTC
|
||||
|
||||
## What Completed
|
||||
- Standardization baseline assembled from Technical Lead standard components + orchestration contract.
|
||||
- Audit compliance pack completed (checks, failure modes, evidence model, approval gates).
|
||||
- Consolidated package produced for immediate CEO review and adoption decision.
|
||||
|
||||
## Files Produced/Updated
|
||||
- `/home/papa/atomizer/workspaces/shared/standardization/2026-02-18-atomizer-project-standardization-package.md`
|
||||
- `/home/papa/atomizer/workspaces/shared/standardization/synthesis/2026-02-18-secretary-synthesis.md`
|
||||
|
||||
## What Remains
|
||||
- CEO approval decision.
|
||||
- Upon approval: enforce package conventions on new project orchestrations.
|
||||
|
||||
## Approval Ask
|
||||
Antoine: please reply with one of:
|
||||
- `✅ Approve` — adopt this standardization package now
|
||||
- `✏️ Approve with amendments` — list required edits
|
||||
- `⏸️ Hold` — defer adoption pending additional changes
|
||||
Reference in New Issue
Block a user