assistant-claw/skills/claw-boss-distiller/demo
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
..
INPUT Refactor: drop Vega framing, promote Atlas to repo root 2026-05-09 17:54:18 +08:00
OUTPUT Refactor: drop Vega framing, promote Atlas to repo root 2026-05-09 17:54:18 +08:00
README.md Refactor: drop Vega framing, promote Atlas to repo root 2026-05-09 17:54:18 +08:00

claw-boss-distiller — Demo Run

A synthetic distillation, end-to-end, on a fictional 中国 SME 老板 "王总". Use this to:

  1. Show clients what boss_skill.md actually looks like before they commit
  2. Validate the pipeline shape end-to-end before real client data arrives
  3. Smoke-test changes to claw-boss-distiller (regression baseline)

Scenario

  • Boss: 王总, founder + CEO of 一家约 80 人的企业服务公司 (toB SaaS), based in 上海
  • Span: ~25 active projects, ~12 active customers, internal team of ~15 PMs/engineers/sales
  • Email volume: ~40 incoming/day, ~20 outgoing/day
  • Demo input: 10 boss-outgoing emails over a 14-day window (compressed sample; real distillation reads 6 months ≈ 2400+ emails)
  • Languages: mostly 中文, occasional English term

Pipeline (matches SKILL.md and ADAPTER.md)

INPUT/wang-emails-*.txt   (10 mock outgoing emails)
        ↓
[Bucket sort]   classify each email into B1B6
        ↓
[Triple verify]   patterns must clear cross-domain + generative + exclusive
        ↓
[Synthesize 5 layers]   Expression DNA / Mental Models / Decision Heuristics / Anti-Patterns / Honest Boundaries
        ↓
OUTPUT/boss_skill.demo.md  (status: draft; awaits boss audit)
OUTPUT/run-summary.md      (counts + verification trace)

Files

demo/
├── README.md                           # this file
├── INPUT/
│   ├── 01-催办-zhangsan-PRJ001.txt
│   ├── 02-决策-supplier-pick.txt
│   ├── 03-表扬-wang-onboarding.txt
│   ├── 04-否决-feature-request.txt
│   ├── 05-转交-li-customer-D.txt
│   ├── 06-mid-thread-intervention.txt
│   ├── 07-pressure-customer-A.txt
│   ├── 08-closing-PRJ022.txt
│   ├── 09-short-reply-FYI.txt
│   └── 10-long-reasoning-Q3-strategy.txt
└── OUTPUT/
    ├── boss_skill.demo.md              # the produced 5-layer document
    └── run-summary.md                  # the distillation log

How to read the demo

  1. Read 23 INPUT emails to get a feel for 王总's voice
  2. Read OUTPUT/boss_skill.demo.md and notice how each rule cites which input emails
  3. Read OUTPUT/run-summary.md to see which candidate patterns were promoted vs filtered out by triple verification

Caveats

  • 10 emails is far below the real W1 corpus size. Real runs produce richer Expression DNA and more decision heuristics.
  • 王总 is fictional; any resemblance to real bosses is coincidental.
  • The demo deliberately includes one ambiguous case (email #4) to show how the pipeline marks low_confidence.