docs: add Phase 6 — Web Chat interface for AI Employees
This commit is contained in:
@@ -64,6 +64,14 @@ Requirements for beta-ready release. Each maps to roadmap phases.
|
|||||||
- [x] **EMPL-04**: Wizard and templates accessible to platform admins and customer admins (RBAC-enforced, not operators)
|
- [x] **EMPL-04**: Wizard and templates accessible to platform admins and customer admins (RBAC-enforced, not operators)
|
||||||
- [x] **EMPL-05**: Agents created via wizard or template appear in Agent Designer for further customization
|
- [x] **EMPL-05**: Agents created via wizard or template appear in Agent Designer for further customization
|
||||||
|
|
||||||
|
### Web Chat
|
||||||
|
|
||||||
|
- [ ] **CHAT-01**: Users can open a chat window with any AI Employee and have a real-time conversation within the portal
|
||||||
|
- [ ] **CHAT-02**: Web chat supports the full agent pipeline — memory, tools, escalation, and media (same capabilities as Slack/WhatsApp)
|
||||||
|
- [ ] **CHAT-03**: Conversation history persists and is visible when the user returns to the chat
|
||||||
|
- [ ] **CHAT-04**: Chat respects RBAC — users can only chat with agents belonging to tenants they have access to
|
||||||
|
- [ ] **CHAT-05**: Chat interface feels responsive — typing indicators, message streaming or fast response display
|
||||||
|
|
||||||
## v2 Requirements
|
## v2 Requirements
|
||||||
|
|
||||||
Deferred to future release. Tracked but not in current roadmap.
|
Deferred to future release. Tracked but not in current roadmap.
|
||||||
@@ -148,11 +156,17 @@ Which phases cover which requirements. Updated during roadmap creation.
|
|||||||
| EMPL-03 | Phase 5 | Complete |
|
| EMPL-03 | Phase 5 | Complete |
|
||||||
| EMPL-04 | Phase 5 | Complete |
|
| EMPL-04 | Phase 5 | Complete |
|
||||||
| EMPL-05 | Phase 5 | Complete |
|
| EMPL-05 | Phase 5 | Complete |
|
||||||
|
| CHAT-01 | Phase 6 | Pending |
|
||||||
|
| CHAT-02 | Phase 6 | Pending |
|
||||||
|
| CHAT-03 | Phase 6 | Pending |
|
||||||
|
| CHAT-04 | Phase 6 | Pending |
|
||||||
|
| CHAT-05 | Phase 6 | Pending |
|
||||||
|
|
||||||
**Coverage:**
|
**Coverage:**
|
||||||
- v1 requirements: 25 total (all complete)
|
- v1 requirements: 25 total (all complete)
|
||||||
- RBAC requirements: 6 total (Phase 4, all complete)
|
- RBAC requirements: 6 total (Phase 4, all complete)
|
||||||
- Employee Design requirements: 5 total (Phase 5)
|
- Employee Design requirements: 5 total (Phase 5, all complete)
|
||||||
|
- Web Chat requirements: 5 total (Phase 6)
|
||||||
|
|
||||||
---
|
---
|
||||||
*Requirements defined: 2026-03-23*
|
*Requirements defined: 2026-03-23*
|
||||||
|
|||||||
@@ -114,7 +114,7 @@ Plans:
|
|||||||
## Progress
|
## Progress
|
||||||
|
|
||||||
**Execution Order:**
|
**Execution Order:**
|
||||||
Phases execute in numeric order: 1 -> 2 -> 3 -> 4 -> 5
|
Phases execute in numeric order: 1 -> 2 -> 3 -> 4 -> 5 -> 6
|
||||||
|
|
||||||
| Phase | Plans Complete | Status | Completed |
|
| Phase | Plans Complete | Status | Completed |
|
||||||
|-------|----------------|--------|-----------|
|
|-------|----------------|--------|-----------|
|
||||||
@@ -123,6 +123,7 @@ Phases execute in numeric order: 1 -> 2 -> 3 -> 4 -> 5
|
|||||||
| 3. Operator Experience | 5/5 | Complete | 2026-03-24 |
|
| 3. Operator Experience | 5/5 | Complete | 2026-03-24 |
|
||||||
| 4. RBAC | 3/3 | Complete | 2026-03-24 |
|
| 4. RBAC | 3/3 | Complete | 2026-03-24 |
|
||||||
| 5. Employee Design | 4/4 | Complete | 2026-03-25 |
|
| 5. Employee Design | 4/4 | Complete | 2026-03-25 |
|
||||||
|
| 6. Web Chat | 0/0 | Not started | - |
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
@@ -130,6 +131,21 @@ Phases execute in numeric order: 1 -> 2 -> 3 -> 4 -> 5
|
|||||||
|
|
||||||
**LLM-03 conflict resolved:** BYO API keys confirmed in v1 scope per user decision during Phase 3 context gathering. Implemented via Fernet encryption in Phase 3.
|
**LLM-03 conflict resolved:** BYO API keys confirmed in v1 scope per user decision during Phase 3 context gathering. Implemented via Fernet encryption in Phase 3.
|
||||||
|
|
||||||
|
### Phase 6: Web Chat
|
||||||
|
**Goal**: Users can chat with AI Employees directly in the portal through a real-time web chat interface — no external messaging platform required
|
||||||
|
**Depends on**: Phase 5
|
||||||
|
**Requirements**: CHAT-01, CHAT-02, CHAT-03, CHAT-04, CHAT-05
|
||||||
|
**Success Criteria** (what must be TRUE):
|
||||||
|
1. A user can open a chat window with any AI Employee and have a real-time conversation within the portal
|
||||||
|
2. The chat interface supports the full agent pipeline — memory, tools, escalation, and media (same capabilities as Slack/WhatsApp)
|
||||||
|
3. Conversation history persists and is visible when the user returns to the chat
|
||||||
|
4. The chat respects RBAC — users can only chat with agents belonging to tenants they have access to
|
||||||
|
5. The chat interface feels responsive — typing indicators, message streaming or fast response display
|
||||||
|
**Plans**: 0 plans
|
||||||
|
|
||||||
|
Plans:
|
||||||
|
- [ ] TBD (run /gsd:plan-phase 6 to break down)
|
||||||
|
|
||||||
---
|
---
|
||||||
*Roadmap created: 2026-03-23*
|
*Roadmap created: 2026-03-23*
|
||||||
*Coverage: 25/25 v1 requirements + 6 RBAC requirements + 5 Employee Design requirements mapped*
|
*Coverage: 25/25 v1 requirements + 6 RBAC requirements + 5 Employee Design requirements mapped*
|
||||||
|
|||||||
0
.planning/phases/06-web-chat/.gitkeep
Normal file
0
.planning/phases/06-web-chat/.gitkeep
Normal file
Reference in New Issue
Block a user