adelorenzo/konstruct
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(03-operator-experience): create phase plan

Browse Source
This commit is contained in:
Adolfo Delorenzo
2026-03-23 21:03:30 -06:00
parent a42fa5f38a
commit 1ff61d9ba4
5 changed files with 1033 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
.planning/ROADMAP.md
View File

@@ -63,31 +63,33 @@ Plans:
**Requirements**: AGNT-07, LLM-03, PRTA-03, PRTA-04, PRTA-05, PRTA-06
**Success Criteria** (what must be TRUE):
1. An operator can connect Slack and WhatsApp to their tenant through a guided in-portal wizard without reading documentation
3. A new tenant completes the full onboarding sequence (connect channel → configure agent → send test message) in under 15 minutes
3. A new tenant completes the full onboarding sequence (connect channel -> configure agent -> send test message) in under 15 minutes
4. An operator can subscribe, upgrade, and cancel their plan through Stripe — and feature limits are enforced automatically based on subscription state
5. The portal displays per-tenant agent cost and token usage, giving operators visibility into spending without requiring access to backend logs
**Plans**: 4 plans
Plans:
- [ ] 03-01: Channel connection wizard (Slack + WhatsApp), onboarding flow, portal polish
- [ ] 03-03: Stripe subscription integration, cost tracking dashboard, usage metrics display
- [ ] 03-01-PLAN.md — Backend foundation: DB migrations, billing models, encryption service, channel/billing/usage API endpoints, audit logger token metadata
- [ ] 03-02-PLAN.md — Channel connection wizard (Slack OAuth + WhatsApp manual), onboarding flow with 3-step stepper, BYO API key settings page
- [ ] 03-03-PLAN.md — Stripe billing page with subscription management, status badges, Checkout and Billing Portal redirects
- [ ] 03-04-PLAN.md — Cost tracking dashboard with Recharts charts, budget alert badges, time range filtering
## Progress
**Execution Order:**
Phases execute in numeric order: 1 → 2 → 3
Phases execute in numeric order: 1 -> 2 -> 3
| Phase | Plans Complete | Status | Completed |
|-------|----------------|--------|-----------|
| 1. Foundation | 4/4 | Complete | 2026-03-23 |
| 2. Agent Features | 6/6 | Complete | 2026-03-24 |
| 3. Operator Experience | 0/2 | Not started | - |
| 3. Operator Experience | 0/4 | Not started | - |
---
## Coverage Notes
**LLM-03 conflict flagged:** LLM-03 (BYO API keys, encrypted at rest) is listed as a v1 requirement in REQUIREMENTS.md but is explicitly listed as out-of-scope in PROJECT.md ("BYO API key support — v2"). LLM-03 has been assigned to Phase 3 (least disruptive placement) but this conflict must be resolved before Phase 3 planning begins. Options: (1) confirm v2 deferral and move LLM-03 to REQUIREMENTS.md v2 section, or (2) confirm it's in scope for v1 and keep 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.
---
*Roadmap created: 2026-03-23*