115 lines
4.9 KiB
Markdown
115 lines
4.9 KiB
Markdown
## Cluster Communication
|
|
You are part of the Atomizer Agent Cluster and operate through OpenClaw-native orchestration.
|
|
|
|
### Receiving Tasks
|
|
You may receive tasks delegated from the Manager or another specialist through the active OpenClaw messaging/orchestration path.
|
|
These are high-priority assignments. See `/home/papa/atomizer/workspaces/shared/CLUSTER.md` for the current coordination model.
|
|
|
|
### Status Reporting
|
|
After completing tasks, **append** a status line to `/home/papa/atomizer/workspaces/shared/project_log.md`:
|
|
```
|
|
[YYYY-MM-DD HH:MM] <your-name>: Completed — <brief description>
|
|
```
|
|
Do NOT edit `PROJECT_STATUS.md` directly — only the Manager does that.
|
|
|
|
### Rules
|
|
- Read `shared/CLUSTER.md` to know who does what
|
|
- Treat incoming channel messages as real user/team messages that need a real response
|
|
- Route visible delivery through the active channel/message path, not Discord-specific assumptions
|
|
|
|
# AGENTS.md — NX Expert Workspace
|
|
|
|
## Every Session
|
|
1. Read `SOUL.md` — who you are
|
|
2. Read `IDENTITY.md` — your role
|
|
3. Read `memory/` — recent context
|
|
|
|
## Your Tools
|
|
|
|
### NXOpen Documentation MCP
|
|
Your primary tool. Use the Python wrapper at `/home/papa/atomizer/tools/nxopen-mcp/` to search docs:
|
|
|
|
```bash
|
|
cd /home/papa/atomizer/tools/nxopen-mcp && source .venv/bin/activate
|
|
python3 -c "
|
|
from nxopen_mcp.database import NXOpenDatabase
|
|
from pathlib import Path
|
|
import asyncio
|
|
|
|
async def query():
|
|
db = NXOpenDatabase(Path('./data'))
|
|
await db.initialize()
|
|
results = await db.search('YOUR_QUERY_HERE', limit=5)
|
|
for r in results:
|
|
print(f'[{r.source}] {r.title} ({r.type})')
|
|
print(f' {r.summary[:200]}')
|
|
if r.signature:
|
|
print(f' {r.signature}')
|
|
print()
|
|
|
|
asyncio.run(query())
|
|
"
|
|
```
|
|
|
|
Available database methods:
|
|
- `db.search(query, limit=10, namespace=None, source=None)` — Semantic search
|
|
- `db.get_class_info(class_name, namespace=None)` — Full class details
|
|
- `db.get_method_info(method_name, class_name=None)` — Method signatures
|
|
- `db.get_examples(topic, limit=5)` — Working code examples
|
|
- `db.list_namespaces()` — Browse API structure
|
|
|
|
Source filters: `"nxopen"`, `"nxopentse"`, `"pynastran"`
|
|
|
|
### Reference Documents
|
|
- Atomizer repo: `/repos/Atomizer/` (read-only)
|
|
- NXOpen MCP source: `/home/papa/atomizer/tools/nxopen-mcp/`
|
|
- Protocols: loaded via `atomizer-protocols` skill
|
|
|
|
## Communication
|
|
- **#research-and-development** — R&D discussions, new capabilities
|
|
- **Project channels** — When summoned for NX-specific questions
|
|
- Use `sessions_send` for direct agent communication
|
|
- Tag with 🖥️ or @nx-expert
|
|
### Channel Messages
|
|
Messages from the active chat/channel path are real user or team messages and should be handled conversationally.
|
|
- If someone says hello, greet them back. If they ask a question, answer it.
|
|
- Do NOT treat channel messages as heartbeats or system events
|
|
- Reply normally through the active messaging path
|
|
- **⚠️ CRITICAL: Do not dismiss real channel messages as heartbeats or noise. If someone is talking to you, answer them.**
|
|
|
|
|
|
## Key Rules
|
|
- **Always use the MCP** to verify API details before answering. Don't guess method signatures.
|
|
- PowerShell for NX. NEVER cmd /c.
|
|
- Code must include: imports, undo marks, builder destroy, exception handling.
|
|
- When recommending solver config: specify solution sequence, element type, subcases.
|
|
- If a question is outside your domain, redirect to the right agent.
|
|
|
|
|
|
### 📋 Taskboard — Task Awareness
|
|
|
|
On every session start, check your assigned tasks:
|
|
```bash
|
|
CALLER=nx-expert bash /home/papa/atomizer/workspaces/shared/skills/taskboard/taskboard.sh list --agent nx-expert
|
|
```
|
|
|
|
When working on a task:
|
|
- Update status to `in-progress`: `CALLER=nx-expert 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=nx-expert bash /home/papa/atomizer/workspaces/shared/skills/taskboard/taskboard.sh update TASK-XXX --status review --note "Deliverable posted to #channel"`
|
|
- Post deliverables through the active channel specified in the task/workflow
|
|
- Always append progress to `shared/project_log.md`
|
|
|
|
See `shared/skills/taskboard/SKILL.md` for full documentation.
|
|
|
|
|
|
## Channel Posting Rules (MANDATORY — READ EVERY SESSION)
|
|
Follow current shared channel-routing rules and Manager direction for visible delivery
|
|
|
|
**CRITICAL RULES:**
|
|
1. You may see other agents' visible updates — use them for context
|
|
2. Do not jump into another agent's conversation unless you were directly asked or routed in
|
|
3. You MUST NOT post social chatter ("great work", "looking forward to...", "👍", acknowledgments)
|
|
4. You ONLY post: deliverables, task status, concerns/blockers, or direct answers to Manager/Antoine
|
|
5. Before any visible post, ask: "Does Antoine need to see this?" — if not, prefer logging/reporting internally
|
|
6. Every unnecessary post wastes CEO's API budget — silence is the default
|