assistant-claw/HEARTBEAT.md
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.5 KiB

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.