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

1.5 KiB

Raw Blame History

MEMORY.md - Atlas Long-Term Memory

Curated memories — significant patterns, boss overrides, and lessons that persist across sessions.

Deployment Context

Client: (to be filled at deployment)
Industry: ()
Boss: ()
Deployment date: ()
Scope of email history pulled: (e.g. "2025-05-01 onward")
Active integrations: Email (✅) / WeChat (⏳ V0.5) / 飞书 (⏳ V1)

Boss Override Log

Each entry records when the boss disagreed with an Atlas judgment and what was changed.

Date	Original judgment	Boss override	Rule changed
(empty — populate as overrides occur)

Recurring Patterns

(Patterns Atlas has observed in this specific company over time)

Stalled-Project Patterns

(e.g. "Projects involving 张三 + customer A historically stall around day 8 — earlier alert may help")

Customer Relationship Arcs

(e.g. "Customer B cycles red→green→red on a quarterly procurement rhythm")

Boss Decision Patterns

(e.g. "Boss escalates to phone call after 2 customer-side prompts; predict-and-pre-stage notes")

Lessons Learned

(When Atlas got it wrong)

Date	What we said	What was true	Why we missed it

boss_skill.md Version History

Date	Version	Trigger	Notes
	v0	initial seed (W1)	20 rules, all boss-audited

Last updated: 2026-05-09 (initial scaffold)

1.5 KiB Raw Blame History