Autonomous AI Agent

The production autonomous AI Agent engine inside the Qontak chatbot stack. Today the autonomous engine only runs in chatbot-ml-dev (a prototype with no FE/BE separation, rollout control, or plan gating); this initiative productionises it so Chatbot Specialists and customer Bot Builders can draft an agent from a prompt, configure its Behavior · Capabilities · Routing, attach knowledge + actions, preview, and ship — coexisting with the legacy session-based /ai-agent modal. The 26Q2 driver is 15 autonomous agents across 15 customer IDs inside the already-entitled Plus / Ultimate / 360 tiers.

Master index (ANCHOR)

• autonomous-ai-agent-anchor.md — the ANCHOR PRD: the initiative master index (identity, Phase Index, north-star metrics, decisions). It carries no acceptance criteria of its own (those live in the phase PRDs), so it sits at the initiative root rather than under prds/. Synced with the Confluence Autonomous AI Agent — Phase 1: New Engine Migration and reconciled against code (chatbot, chatbot-fe) + Jira (Epic BOT-4191).

Phases

Phase	Scope	Status	Epic
Phase 1 — New Engine Migration	Production autonomous-agent List / Create / Config (Profile · Capabilities · Routing) + Shared Actions — the new configuration model, coexisting with the legacy modal	PRD draft; partial — shipped on /v2/ai_agents autonomous mode (BOT-4235, Done); Shared Resources (KB) + preview rail pending	BOT-4191
Phase 2 — Migrate Existing (Internal) Configurations	Migration plan moving agents already configured internally on the legacy Tree-Diagram config onto the new engine + new config model (picks up Phase 1 Non-Goals #1/#3)	TBD — Engineering + Data/ML team; data to be provided	TBD
Phase 3 — New-Configuration Iteration	Iterate the new config from the Design Validation research (15 IDIs): visual Logic Map, terminology overhaul, Milestone/Routing fixes, inline validation, snippets	Planned	TBD

Reconciliation note (2026-06-22): the Confluence draft describes a new FrontendService::V3 namespace, /ai-agent/autonomous routes, and an autonomous_ai_agent rollout flag. The code shipped differently — FrontendService::V2 (/v2/ai_agents autonomous mode), /bot-automation/* FE routes, and an ai_agent_engine_version === 2 org-setting gate. The full drift table is in the Phase-1 PRD's "Implementation Reconciliation" section.

Sibling initiatives (not phases of this one): AI Agent Testing (BOT-3351) now owns the batch test-runner + judging scope this PRD deferred; AI Agent Knowledge overlaps the Shared Resources surface. Both are separate programs with their own anchors — confirm the hand-offs before the Phase-2/3 PRDs are written.

Scope Changes

• Backend — FrontendService::V2 autonomous-agent endpoints, skill_pack adapter, capability validators, OSS-first KB ingestion.
• Frontend — /bot-automation/* List / Create / Config (AiAgentEditor) + Actions; engine-version routing vs the legacy modal.
• Data — upstream noncore-mrag / chatbot-ai / mekari-agent contracts; KB vectorisation.

QA Lane

Lane B — keeps a human QA gate. Triggers: real-time chat flow (autonomous agent handles live customer conversations) + multi-org data isolation (agent knowledge and actions span customer workspaces). Classified by DRI on 2026-06-26. See .claude/reference/qa-lanes.md for the decision rules.

Contents

• prds/ — phase PRDs (each with its own ACs → Jira Epic) land here.
• rfcs/ — Request for Comments (technical design proposals). The Confluence RFC (QON 51184074800) can be mirrored here.
• tests/ — E2E / acceptance test specs.
• delivery/ — TPM timeline, status reports, decision records.