Skip to content

ADR Update Note — 2026-09-26

Audience: developers and maintainers. This note summarizes the bot architecture decisions recorded on 2026-09-26 across the two coordinated repos. Read the linked ADRs for full context — this note is a map, not a substitute.

The two repos and their concerns

Repo Owns Audience
agentic-program Bot engineering: creation, KB strategy, escalation path Developers
wecom-suite Bot adoption: usage, training, user-facing docs All employees

Rule: each fact has exactly one home. Cross-reference by link, never copy (wecom-suite ADR-0006).

What changed on 2026-09-26

agentic-program

  1. ADR-0002 — Native Bot KB Strategy. Bot knowledge sets are built from staged COS/git Markdown uploaded directly to WeCom 知识集 (≤1,000 files per set, one scope per bot). Lexiang is off the critical path — no new content is pushed to Lexiang for bot consumption. Fidelity starts KB-strict (仅根据知识集回答); the mode is per-bot and reversible in the admin console. A sync script (repos → staged Markdown → knowledge-set files) will be owned in this repo. Partially supersedes ADR-0001 (knowledge-source linkage only; the WeCom Smart Robot platform decision stands).

  2. ADR-0003 — Agentic Escalation Path. One technical architecture, three stages: Q&A → tool plugins (拓展能力) → API mode (external brain). The WeCom surface, KB staging, and sync script persist across all stages. When a bot first needs write access, open a separate project with governance deliverables (permissions model, audit, approval flows); sensitive writes never run on native 拓展能力 alone — put ADP governance or the WorkBuddy gateway in front.

wecom-suite

  1. ADR-0006 — Bot Docs Separation of Concerns (the repo-split rule above) and the new Bot Adoption page: what bots exist, how to use them, strict-mode expectations, feedback path.

Lexiang re-entry triggers (from ADR-0002)

Do not reintroduce Lexiang unless one of these becomes real:

  1. A bot must execute tasks and Lexiang/ADP tooling wins the evaluation.
  2. Real-time WeCom → KB sync is required.
  3. Multiple bots need one governed, deduplicated, versioned shared KB.
  4. A scope outgrows the 1,000-file-per-set model.

Phased roadmap

Phase Scope Status
1 Q&A bot pilot: KB staging, bot creation, pilot group, dashboard review Next
2 Tool-assisted bots (MCP/API plugins on read-only operations) Blocked by Phase 1 review
3 Agentic project: governance ADRs, write-capable bots via API mode Opens when a bot needs write access

Known cleanups

  • The doc → Lexiang publish script (broken since 2026-08-11, plantuml_markdown missing) is parked — not a bot blocker.
  • docs/context/ pillar files exist locally; remote main was missing them until the 2026-09-26 history realignment (see .session.md).

Full ADR index