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

docs(01): capture phase context

Browse Source
This commit is contained in:
Adolfo Delorenzo
2026-03-23 09:19:53 -06:00
parent f39508d297
commit d032d81171
3 changed files with 94 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
.planning/ROADMAP.md
View File

@@ -21,19 +21,21 @@ Decimal phases appear between their surrounding integers in numeric order.
### Phase 1: Foundation
**Goal**: Operators can deploy the platform, a Slack message triggers an LLM response back in-thread, and no tenant can ever see another tenant's data
**Depends on**: Nothing (first phase)
**Requirements**: CHAN-01, CHAN-02, CHAN-05, AGNT-01, LLM-01, LLM-02, TNNT-01, TNNT-02, TNNT-03, TNNT-04
**Requirements**: CHAN-01, CHAN-02, CHAN-05, AGNT-01, LLM-01, LLM-02, TNNT-01, TNNT-02, TNNT-03, TNNT-04, PRTA-01, PRTA-02
**Success Criteria** (what must be TRUE):
1. A user can send a Slack @mention or DM to the AI employee and receive a coherent reply in the same thread — end-to-end in under 30 seconds
2. Tenant A's messages, agent configuration, and conversation data are completely invisible to Tenant B — verified by integration tests with two-tenant fixtures
3. A request that exceeds the per-tenant or per-channel rate limit is rejected with an informative response rather than silently dropped
4. The LLM backend pool routes requests through LiteLLM to both Ollama (local) and Anthropic/OpenAI, with automatic fallback when a provider is unavailable
5. A new AI employee can be configured with a custom name, role, and persona — and that persona is reflected in responses
6. An operator can create tenants and design agents (name, role, persona, system prompt, tools, escalation rules) via the admin portal
**Plans**: TBD
Plans:
- [ ] 01-01: Monorepo scaffolding, Docker Compose dev environment, shared Pydantic models, DB schema with RLS
- [ ] 01-02: LiteLLM backend pool service with Ollama + Anthropic/OpenAI providers and Celery async dispatch
- [ ] 01-03: Channel Gateway (Slack adapter), Message Router (tenant resolution), basic Agent Orchestrator (single agent, no memory/tools)
- [ ] 01-04: Next.js admin portal with Auth.js v5, tenant CRUD, and Agent Designer module
### Phase 2: Agent Features
**Goal**: The AI employee maintains conversation memory, can execute tools, handles WhatsApp messages, and escalates to humans when rules trigger — making it a capable product rather than a demo
@@ -56,18 +58,16 @@ Plans:
### Phase 3: Operator Experience
**Goal**: An operator can sign up, onboard their tenant through a web UI, connect their messaging channels, configure their AI employee, and manage their subscription — without touching config files or the command line
**Depends on**: Phase 2
**Requirements**: AGNT-07, LLM-03, PRTA-01, PRTA-02, PRTA-03, PRTA-04, PRTA-05, PRTA-06
**Requirements**: AGNT-07, LLM-03, PRTA-03, PRTA-04, PRTA-05, PRTA-06
**Success Criteria** (what must be TRUE):
1. An operator can create a tenant, configure an AI employee's name, role, persona, tools, and escalation rules entirely through the portal web UI
2. An operator can connect Slack and WhatsApp to their tenant through a guided in-portal wizard without reading documentation
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
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**: TBD
Plans:
- [ ] 03-01: Next.js 16 admin portal foundation with Auth.js v5, API layer, tenant CRUD
- [ ] 03-02: Agent configuration UI, channel connection wizard (Slack + WhatsApp), onboarding flow
- [ ] 03-01: Channel connection wizard (Slack + WhatsApp), onboarding flow, portal polish
- [ ] 03-03: Stripe subscription integration, cost tracking dashboard, usage metrics display
## Progress
@@ -77,9 +77,9 @@ Phases execute in numeric order: 1 → 2 → 3
| Phase | Plans Complete | Status | Completed |
|-------|----------------|--------|-----------|
| 1. Foundation | 0/3 | Not started | - |
| 1. Foundation | 0/4 | Not started | - |
| 2. Agent Features | 0/4 | Not started | - |
| 3. Operator Experience | 0/3 | Not started | - |
| 3. Operator Experience | 0/2 | Not started | - |
---