# boss_skill.md (Seed Template — v0 / pre-deployment defaults) > **Status:** Seed defaults. Each rule below is `status: seed` and replaced by `status: confirmed` after the boss audit pass in W2 of deployment. > > **Why ship a seed at all:** Atlas needs *some* rules from day 1 — otherwise W1 has no judgment criteria and the first Inventory Report cannot be generated. These seed defaults represent generic Chinese SME boss behavior; they are deliberately conservative and easy to override. > > **Boss override format:** Boss replies to the W2 audit email with one line per rule: `R-NN: keep | edit "" | drop | add ""`. --- ## L1 — Expression DNA > How the boss writes. Used by `claw-report-writer` to match the boss's voice in the daily Brief. ### E-01: Default sentence length — `seed` - Average 15–25 characters per sentence in Chinese; 15–25 words in English - Bias toward short over long when status report; long when reasoning is requested - Source: 30-email random sample from W1 outgoing - Used by: report-writer ### E-02: Default greetings / closings — `seed` - Greeting: omit (skip "您好" in internal mail; keep for external) - Closing: omit signature when replying within a thread - Used by: report-writer ### E-03: Signature phrases (to be discovered) — `seed` - _(Empty in seed; W1 distillation populates 3–5 actual signature phrases)_ - Used by: report-writer ### E-04: Tonal default — `seed` - Direct, low-hedge ("我看可以" rather than "我觉得也许可以") - No 客套话 / corporate filler - Used by: report-writer --- ## L2 — Mental Models > The 3–7 frameworks the boss reaches for. Used by `claw-project-tracker` and `claw-people-observer` to interpret signals the boss's way. ### M-01: 主要矛盾优先 — `seed` - **One-liner:** Always solve the binding constraint first; everything else can wait. - **Detection:** When boss replies to a multi-issue email, they typically address only one item — the one they consider 主要矛盾. - **Atlas application:** When ranking "Top 3 actions" in the daily Brief, the #1 must be the leverage-maximizing action, not the urgent-but-low-leverage one. ### M-02: 落地率优先于动作量 — `seed` - **One-liner:** A finished thing beats five busy things. - **Detection:** Boss treats "Active for 60 days with no closure" as a problem, even if there's recent activity. - **Atlas application:** People-observer must surface `completed_30d` and `stalled_ratio` together; raw activity counts alone are misleading. ### M-03: 责任要落到一个人 — `seed` - **One-liner:** Two responsible = no one responsible. - **Detection:** Boss frequently asks "谁负责?" / "谁在跟?" when projects stall. - **Atlas application:** RACI Accountable being missing or ambiguous is a hard alert (`R-RACI-A-missing`), surfaced even before stall threshold is hit. --- ## L3 — Decision Heuristics > The ~50-rule core (seed contains 10; W1 distillation expands to ~30–50). The L1/Atlas-PRD-v0.3 ruleset. ### R-01: 5-day silence rule — `seed` - **If** a project has had no two-way communication in ≥ 5 working days **and** has an outstanding `Waiting-For` **then** mark `Stalled`. - **Threshold variable:** `stall_threshold_days` (default 5; boss can override globally or per-customer) - **Evidence count needed to confirm:** 5+ instances of boss flagging projects at this rough timeframe - **Audit:** writes to `audit/rule_fires.csv` on every fire ### R-02: Customer-side urge rule — `seed` - **If** customer side has prompted ≥ 2 times in 14 days **then** escalate project to red, surface in Andon. - **Threshold:** `customer_urge_count` = 2 ### R-03: Boss CC = elevated priority — `seed` - **If** boss is explicitly CC'd on a thread (vs BCC or absent) **then** the project's priority is auto-tagged `+1`. ### R-04: Decision-maker direct intervention — `seed` - **If** an external decision-maker (per `customers/*.json::客户方决策链.决策者`) speaks up after silence **then** fire Andon alert; recommend boss respond directly within 24h. ### R-05: Strong-negative VoC trigger — `seed` - **If** customer-side message contains strong-negative phrases (`再这样我就找别家`, `我们考虑停止合作`, `让我非常失望`, etc.) **then** customer CHS drops 1 tier immediately, regardless of computed score. - **Wordlist** maintained in `state/voc/strong_negative_zh.txt` and `_en.txt`; boss can extend. ### R-06: Terminal-keyword closing — `seed` - **If** thread contains terminal keywords (`验收`, `结案`, `关闭`, `signed off`, `accepted`, `completed`) from the customer or boss **then** mark project `Completed`. - Special case: boss says "先放放" / "先 hold" → mark `Someday`, not `Completed`. ### R-07: Drop after 60-day silence — `seed` - **If** project state was `Stalled` or `Someday` **and** no signal in 60 days **then** transition to `Dropped`. - **Important:** Atlas surfaces a notice 7 days before the auto-drop, giving boss a chance to revive. ### R-08: Overload threshold (people layer) — `seed` - **If** a person's `active_projects > 6` **and** `stalled_ratio > 0.3` **then** flag `R-overload` in their card. - This flags the *condition*, not a verdict on the person. ### R-09: Customer health tier transitions — `seed` - CHS calculation per spec; tier breaks at 80 (Green/Yellow) and 60 (Yellow/Red). Tier downgrades fire Andon; tier upgrades go to weekly rollup only (no Andon spam for good news). ### R-10: Boss-touch recommendation rule — `seed` - **If** customer is Red **and** decision-maker has spoken up in past 14 days **then** Brief recommends "本周内 boss 亲自电话". - **If** customer is Yellow **and** stalled ≥ 2 weeks **then** Brief recommends "建议 boss email 主动联系". - **If** Green **then** no Brief mention unless tier-up event. ### R-11: Project-merge proposal — `seed` - **If** two project candidates share ≥ 70% participants and ≥ 50% keyword overlap over a 30-day window **then** propose merge in `state/projects/_to_merge.json` for boss confirm. ### R-12: Identity-merge proposal — `seed` - **If** two `people/` cards have signature-line match (same phone, same title) **and** project overlap **then** propose merge in `state/people/_to_merge.json`. --- ## L4 — Anti-Patterns > What the boss explicitly does NOT accept. Atlas avoids these in any output. ### AP-01: 不接受"以为别人在跟" — `seed` - Atlas never frames a stall as "no one knew who was supposed to do this" — that's a verdict-free observation. Always assign the missing role explicitly: "Accountable 缺失 (R-RACI-A-missing)." ### AP-02: 不在客户面前批评内部员工 — `seed` - (V0: irrelevant — Atlas doesn't write to customers. Preserved for V2 when write actions arrive.) ### AP-03: 不让数据替代判断 — `seed` - Atlas surfaces signals; never says "员工 X 应该被解雇". Verdict language is the boss's domain. ### AP-04: 不重复未被处理的 Andon — `seed` - Once an Andon fires, suppress same-trigger re-fire within 24 hours of acknowledgment. Don't badger the boss with the same red flag twice in one day. --- ## L5 — Honest Boundaries > What Atlas cannot or will not do. These are immutable in V0; cannot be overridden by boss. ### HB-01: 不替老板回复邮件 - V0 / V0.5: Atlas never sends email to anyone except the boss themselves (and EA if boss authorized). - V1+: Drafts only, never auto-sends. ### HB-02: 不给员工评级 - Atlas never assigns 9-Box potential, A/B/C labels, PIP triggers, hire/fire recommendations. - Atlas computes performance-dimension data; boss assigns the verdict. ### HB-03: 跨客户数据隔离 - A report on Customer A never references Customer B data, even if relevant. - This is enforced at `claw-report-writer` level via the `report_scope` filter. ### HB-04: 不预测老板的潜力评估 - Atlas does not auto-fill the 9-Box potential dimension. It stays `null` until the boss writes a value. ### HB-05: 不在邮件原文之外编造证据 - Every judgment cites real `source_email_ids`. If Atlas can't cite, it doesn't claim. "信息不足" is a valid output. --- ## Source Index | Bucket | Source emails | Status | |---|---|---| | B1 Outgoing-by-intent | _(to be populated W1)_ | seed | | B2 Mid-thread interventions | — | seed | | B3 Short replies | — | seed | | B4 Long replies | — | seed | | B5 Pressure threads | — | seed | | B6 Closing threads | — | seed | ## Audit Log | Date | Event | |------|-------| | (deploy date) | v0 seed instantiated; all rules `status: seed` pending W2 boss audit | | (W2 audit date) | _(to be filled)_ Boss audit; rules transition `seed → confirmed` per per-rule decisions | --- _File version: seed-v0.1_ _Last updated: 2026-05-09_ _Owner of edits: boss (via reply-to-Brief override format) + quarterly distiller diff_