kagentz-bot
705c29a4e0
CI / validate (pull_request) Failing after 1s
Architecture change: DM-First (v2) replaces @mention-in-stream (v1) as primary agent interaction channel. See ADR-001-dm-topology and ADR-002-dm-routing. Key changes: - New DM-first Zulip adapter (adapter_dm.py) deployed on CT 112 - Registers empty narrow to receive ALL events - Demuxes DMs (type: 'private') vs stream events - Replies to DMs back in private thread, stream replies to #agent-hub - Uses blocking long-poll (dont_block=False) to eliminate rate limiting - Rewritten ARCHITECTURE.md, CONTEXT.md, PRD.md for v2 DM-First - New ADRs: ADR-001 (DM Topology), ADR-002 (DM Routing) - Archived old ADRs: 001, 002, 005 (topic-topology, mention-routing, mention-detection) - Updated ADRs: 003 (agent-naming), 004 (per-agent-bots), 006 (all-bots-model) - Updated PI extension (index.ts) with DM-aware patterns - Tanko agent confirmed responding in both DM and @all-bots in #agent-hub
12 lines
414 B
Markdown
12 lines
414 B
Markdown
# ADR 3: Agent Naming Convention (Unchanged)
|
|
|
|
**Date**: 2026-04-28 | **Status**: Still active — DM architecture does not affect naming
|
|
|
|
### Decision
|
|
Each agent bot has a display name in `{name}-bot` format: `tanko-bot`, `mumuni-bot`, etc.
|
|
|
|
### Consequences (Unchanged)
|
|
- DM address: `@**tanko-bot**` (same as @mention format)
|
|
- Email format: `tanko-bot@chat.sysloggh.net`
|
|
- Consistent naming across all 6 agents
|