bd0be97630
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).
|
||
|---|---|---|
| .. | ||
| customer.md | ||
| person.md | ||
| project.md | ||
| README.md | ||
State Schemas
Atlas's state lives as JSON files under state/. Three primary entities + auxiliary collections.
Primary entity schemas
| File | Spec | Owner |
|---|---|---|
state/projects/PRJ-*.json |
project.md | claw-project-tracker |
state/people/<name>.json |
person.md | claw-people-observer |
state/customers/CUST-*.json |
customer.md | claw-customer-radar |
Auxiliary collections
| File | Purpose |
|---|---|
state/index.json |
Top-level rollup: counts, tier distribution, last update |
state/people/aliases.json |
Alias map for identity resolution |
state/customers/domain_map.json |
Email-domain → customer ID map |
state/extracted/YYYY-MM/<thread_id>/<msg_id>.json |
Canonical Email JSON output of email-extractor |
state/runs/YYYY-MM-DD.json |
Daily run snapshot |
state/runs/alerts.json |
Andon alert queue (append-only) |
state/audit/project_transitions.csv |
Every state transition |
state/audit/people_signals.csv |
Every BARS / CCAR signal asserted |
state/audit/boss_overrides.csv |
Every boss override applied |
state/audit/rule_fires.csv |
Per-rule fire counter |
state/unclustered/<thread_id>.json |
Threads claw-project-tracker couldn't cluster |
boss_skill.md |
The L1+L2+...+L5 mental model file (see claw-boss-distiller/) |
boss_skill.history/YYYY-Q*.md |
Quarterly archive of confirmed boss_skill versions |
Universal conventions
- All timestamps: ISO 8601 UTC with
Zsuffix - All amounts: number + ISO 4217 currency code
- All
source_email_ids: arrays, never single string - All
rule_refs: machine-readable rule IDs (R-NN, GTD-WF, BARS-proactivity-3, etc.) _metablock on every entity:created_at,updated_at,atlas_version, plus entity-specific fields
Privacy & retention
- All state files live INSIDE the client's network. Never copied out.
- Per-customer / per-person right-to-delete commands purge JSON + emit tombstones to
audit/ - Daily snapshot under
state/runs/enables point-in-time rollback (last 90 days kept; older compressed to monthly)
Schema versioning
- Atlas writes its own version into
_meta.atlas_version - Schema changes require a migration script under
scripts/migrations/v0.X-to-v0.Y.py - Atlas refuses to read state written by a newer schema version (forward-incompatible by design)
Validation
Each schema doc above will be paired with a JSON Schema (.schema.json) when claw skills are implemented in code. Atlas validates every write; invalid writes go to state/.invalid/ for debugging.