Atlas refactor bd0be97630 Refactor: drop Vega framing, promote Atlas to repo root

This repo IS Atlas (总助 Claw / 老板视角项目执行雷达). The earlier
two-profile framing (Atlas + Vega placeholder) was a misread — Vega is
the agent persona answering Multica issues, not the product. Vega has
no relationship to assistant-claw the product.

Changes:
- Move atlas/* to top-level (git mv preserves history)
- Remove empty Vega placeholders prompts/.gitkeep, tools/.gitkeep
- Delete atlas/ wrapper directory (now empty)
- Update path references in INTEGRATION-hermes.md, scripts/mirror-...sh,
  docs/decisions/0001-mirror-nuwa-skill.md
- Rewrite README.md as Atlas-only, remove dual-profile language

After this commit:
- Top-level OpenClaw 8 files (IDENTITY/SOUL/USER/AGENTS/TOOLS/MEMORY/
  BOOTSTRAP/HEARTBEAT + CLAUDE symlink + zh-CN mirrors)
- skills/{6 sub-skills + DESCRIPTION + README}
- mcp-tools/{spec + Python implementation}
- state-schemas/{project, person, customer + README}
- autopilots/{5 atlas-*.yaml}
- client-deck/, docs/decisions/, scripts/

The ~/.hermes/skills/atlas/ destination convention preserved (atlas as
a skill namespace on the operator's machine, distinct from source path).

2026-05-09 17:54:18 +08:00

2.8 KiB

Raw Permalink Blame History

TOOLS.md - Atlas Tool Configuration

Each Atlas instance is deployed inside the client's network. Tool credentials and endpoints are configured at install time.

Communication

Primary channel to boss: Email (Brief delivered to boss's inbox, signed Atlas / 总助)
Andon alerts: Email + (optional) WeChat push via 企业微信 robot webhook
Boss override channel: Boss replies to Brief email; Atlas parses reply for OVERRIDE: <rule-id> <new-value> markers

Email Ingestion (Read-Only)

Tool	Status	Notes
email-fetch (IMAP)	V0 default	Standard IMAP/SSL; supports incremental UID sync
email-fetch (Gmail API)	V0 alternative	OAuth2; more reliable than IMAP for Gmail
email-fetch (Exchange / EWS / MS Graph)	V0 alternative	For corporate Exchange / O365
wechat-fetch	V0.5	Read-only; via 企业微信 API or third-party MCP server
feishu-fetch	V1	飞书开放平台 OpenAPI

Email Extraction Pipeline

See mcp-tools/email-extractor.md for the full design (7-stage pipeline).

State Storage

Backend: Filesystem JSON (V0). SQLite migration at >1000 projects (~30-line script).
Location: state/ under workspace root, never outside client network.
Backup: git repo (private, client-controlled). State changes commit nightly with daily-snapshot tag.

Report Rendering

Tool	Output
report-render (markdown→PDF)	For attachable Brief PDF
report-render (markdown→HTML inline-email)	For email body
report-render (markdown→WeChat-card)	V0.5 — when WeChat output enabled

Mental Model Distillation

claw-boss-distiller — vendored from nuwa-skill (MIT). Reads boss outgoing email corpus → 5-layer boss_skill.md.
Refresh cadence: quarterly + on-demand.

Audit & Observability

rule-audit — append-only log: which rules fired, on which emails, producing which judgments. Boss can grep this.
state-diff — between any two daily snapshots, render a state-change diff (which projects flipped state, which alerts fired).

Model Providers

Primary LLM: Configurable per client deployment. Default: Claude Sonnet 4.6 for daily runs, Claude Opus 4.7 for quarterly distillation.
Embedding (V1 only): for L3 semantic retrieval, not in V0.

Network & Privacy

Air-gapped option: All processing inside client VPC; only Brief PDF leaves network (delivered to boss's inbox).
DPA required: Data Processing Agreement signed before W1.
Data retention: Raw email cache 90 days; extracted state files indefinite (client-owned).
Right-to-delete: Single command wipes all Atlas state for a person / customer / project.

Update this file whenever a tool integration is added, configured, or deprecated.

2.8 KiB Raw Permalink Blame History