Atomizer/hq/workspaces/technical-lead/TOOLS.md

TOOLS.md — Technical Lead

Shared Resources

• Atomizer repo: /home/papa/repos/Atomizer/ (read-only)
• Obsidian vault: /home/papa/obsidian-vault/ (read-only)
• Job queue: /home/papa/atomizer/job-queue/ (read — for result analysis)

Skills

• atomizer-protocols — Company protocols (load every session)
• atomizer-company — Company identity + LAC critical lessons

Key References

• QUICK_REF: /home/papa/repos/Atomizer/docs/QUICK_REF.md
• Architecture: /home/papa/repos/Atomizer/docs/ARCHITECTURE.md
• Extractors: /home/papa/repos/Atomizer/docs/generated/EXTRACTOR_CHEATSHEET.md
• Zernike fundamentals: /home/papa/repos/Atomizer/docs/physics/ZERNIKE_FUNDAMENTALS.md
• NX integration: /home/papa/repos/Atomizer/docs/api/nx_integration.md

Knowledge Base

• LAC optimization memory: /home/papa/repos/Atomizer/knowledge_base/lac/optimization_memory/
• Session insights: /home/papa/repos/Atomizer/knowledge_base/lac/session_insights/
• Protocols source: /home/papa/repos/Atomizer/docs/protocols/

Solver Reference

SOL	Type	Use Case
101	Linear static	Standard structural analysis
103	Normal modes	Modal/frequency analysis
105	Buckling	Linear buckling
106	Nonlinear static	Large deformation, contact
200	Design optimization	Nastran-native optimization
153	Steady thermal	Thermal analysis

Orchestration Skill

• Script: /home/papa/atomizer/workspaces/shared/skills/orchestrate/orchestrate.sh
• Required caller flag: --caller tech-lead
• Allowed targets: webster, nx-expert, study-builder, secretary
• Optional channel context: --channel-context <channel-name-or-id> --channel-messages <N>

📊 Mission-Dashboard (MANDATORY)

The Atomizer-HQ Mission-Dashboard is the single source of truth for all tasks.

• Dashboard: http://100.68.144.33:8091
• Data: ~/atomizer/mission-control/data/tasks.json
• CLI: ~/atomizer/workspaces/shared/mc-update.sh
• Protocol: ~/atomizer/workspaces/shared/skills/mission-control-protocol.md

Commands

MC=~/atomizer/workspaces/shared/mc-update.sh
$MC add "Title" "Description" [status] [project] [priority]
$MC start <task_id>
$MC comment <task_id> "Progress update"
$MC subtask <task_id> <sub_id> done
$MC complete <task_id> "Summary of work done"
$MC status <task_id> <new_status>

Rules

1. No shadow work — every project/orchestration MUST have a dashboard task
2. Update task before posting to Slack — dashboard is the record, Slack is discussion
3. Log progress as comments — this is the audit trail