assistant-claw/atlas/HEARTBEAT.md
Vega (Atlas scaffolding) ce9f27320a Add Atlas profile under atlas/ — boss-perspective project execution radar
This adds the full Atlas (总助 Claw / 老板视角项目执行雷达) scaffolding as a
sibling profile to the existing Vega general-purpose assistant. All Atlas content
lives under atlas/ to keep the existing top-level skeleton intact.

What's included:

- atlas/IDENTITY.md, SOUL.md, USER.md, AGENTS.md, MEMORY.md, BOOTSTRAP.md,
  HEARTBEAT.md, TOOLS.md (+ zh-CN mirrors) — full OpenClaw 8-piece set
  matching the zero-cca convention
- atlas/skills/ — 6 sub-skills with frontmatter:
  claw-email-parser / claw-project-tracker / claw-people-observer /
  claw-customer-radar / claw-boss-distiller / claw-report-writer
- atlas/skills/claw-boss-distiller/ — adapter notes for nuwa-skill, 5-layer
  boss_skill seed template (23 rules across Expression DNA / Mental Models /
  Decision Heuristics / Anti-Patterns / Honest Boundaries), and a complete
  synthetic distillation demo (10 input emails -> validated 5-layer output)
- atlas/mcp-tools/email-extractor/ — Python implementation of stages 1-3
  (fetch + decode + dequote), 7 pytest tests passing, CLI: atlas-extract
- atlas/state-schemas/ — formal JSON schemas for project / person / customer
  cards with the no-employee-rating hard constraint baked in
- atlas/client-deck/ — 2-page client-facing pitch document
- autopilots/atlas-*.yaml — 5 autopilot configs (daily / weekly / monthly /
  quarterly + andon event-triggered) for a future Multica-side scheduler

Notes:

- nuwa-skill (MIT, https://github.com/alchaincyf/nuwa-skill) NOT vendored;
  fetch at deploy time via instructions in
  atlas/skills/claw-boss-distiller/upstream/README.md
- Vega-side prompts/skills/tools/autopilots/docs scaffold left untouched
- Top-level README.md updated with a brief Atlas pointer; rest preserved
2026-05-09 17:00:29 +08:00

53 lines
2.5 KiB
Markdown

# HEARTBEAT.md - Atlas Periodic Check-ins
_Tasks to rotate through during scheduled runs. Different entry points pull different items._
## Daily (run by autopilot at 07:30, entry B)
- [ ] Pull incremental emails since last sync (`email-fetch`)
- [ ] Run `email-extractor` on new messages
- [ ] Update `state/projects/` cards for any project touched yesterday
- [ ] Update `state/people/` for behavior signals (response time, override-required, escalation)
- [ ] Update `state/customers/` CHS — fire Andon if any customer crosses threshold
- [ ] Generate Daily Brief; deliver to boss
- [ ] Append today's `memory/YYYY-MM-DD.md`
## Weekly (Monday 08:00, entry C)
- [ ] Compute weekly state-diff vs last Monday
- [ ] Identify projects that aged into Stalled this week
- [ ] Identify people whose project density jumped >2 (overload signal)
- [ ] Render Weekly Rollup (done / in-progress / blocked / upcoming)
- [ ] Review boss override log from past 7 days; flag any rule that was overridden ≥ 2 times for next quarterly distillation
## Monthly (1st of month 09:00, entry C variant)
- [ ] Per-customer one-page Health Report
- [ ] Identify any customer who has been Yellow ≥ 3 weeks without recovery
- [ ] Top-N report: most overloaded people, most stalled projects, highest-revenue at-risk customers
## Quarterly (1st of Jan/Apr/Jul/Oct, entry D)
- [ ] Re-run `claw-boss-distiller` over past 90 days of outgoing email
- [ ] Diff new draft vs current `boss_skill.md`
- [ ] Surface diffs in 3 buckets: rules to add / rules to revise / rules to retire
- [ ] Schedule boss review session
- [ ] After review: bump `boss_skill.md` version, archive prior version under `boss_skill.history/`
## Event-Triggered (real-time, no schedule)
- [ ] First time a project transitions to `Stalled` → Andon alert
- [ ] First time a customer drops a tier (green→yellow, yellow→red) → Andon alert
- [ ] Strong-negative VoC quote detected (e.g. "再这样我就找别家了") → Andon alert
- [ ] Boss replies to a Brief with `OVERRIDE: <rule-id>` → log override, propose rule edit
## Maintenance (any run, low frequency)
- [ ] Check `unclustered/` queue — any threads that need boss to disambiguate?
- [ ] Check `state/audit/rule_usage.csv` — any rule with 0 fires in 60 days? Candidate for retirement.
- [ ] Run `state-diff` integrity check — no orphaned project IDs, no people without active projects, no customers without related project history
---
_Keep heartbeats lean. Daily run should complete in <2 minutes for a typical 50-email-per-day inbox. If it's slower, profile and trim._