milo
2d5c636b9d
- Refresh ROADMAP.md to reflect current Forgejo milestones and open feature issues\n- Add .env logging controls and update src/logger.py to honor them (console/file/error toggles, per-handler levels)\n- Fix indentation bug in src/autochat.py so emoji reactions work\n- Truncate and standardize logs; document logging usage in .env
134 lines
4.8 KiB
Markdown
134 lines
4.8 KiB
Markdown
# 📍 DeltaBot Development Roadmap
|
||
|
||
This roadmap is an actionable summary of current milestones and feature issues. It mirrors the milestones on the Forgejo repository and links to issues (local issue numbers).
|
||
|
||
---
|
||
|
||
## 🚀 Alpha Build Ready — Core features (Milestone)
|
||
Focus: deliver core capabilities so Delta is useful and reliably persona-driven.
|
||
|
||
Open high-priority items (Alpha):
|
||
- #37 — 🧠 LoRA Support — improve model fine-tuning/load-time behavior
|
||
- #36 — Memory — persistence for context beyond immediate messages
|
||
- #26 — Web usage — optional web-enabled features (codex/integration)
|
||
- #25 — 🔁 Enable Modelfile Support — support alternate model packaging
|
||
- #24 — 💸 Set up Monetization — billing/paid features plumbing
|
||
- #22 — 📡 Remote Admin Panel — admin web UI / remote control
|
||
- #17 — 🖼️ Image Generation — generate images via local models
|
||
- #16 — 👀 Image Interpretation — describe and analyze posted images
|
||
- #10 — Post "Reply" — post as reply-to instead of plain message
|
||
|
||
Closed/implemented Alpha items: #8, #9, #15, #30, #31
|
||
|
||
Suggested next steps for Alpha:
|
||
- Break large items (Remote Admin Panel, Image Generation) into sub-tasks.
|
||
- Prioritize Memory (#36) and Post "Reply" (#10) to stabilize context handling.
|
||
- Add clear acceptance criteria to each open Alpha issue.
|
||
|
||
---
|
||
|
||
## 🧪 Beta Build — Polishing & optional features (Milestone)
|
||
Focus: polish, scaling, and user-experience improvements.
|
||
|
||
Open Beta items:
|
||
- #35 — Respect token budget (~1000 tokens max)
|
||
- #34 — 📌 Pin system messages
|
||
- #33 — 🧠 Add memory persistence (overlaps with Alpha Memory)
|
||
- #27 — Multi model support — support local switching/multiple endpoints
|
||
- #18 — 🎭 Multi Personality — multiple personas selectable per server/channel
|
||
|
||
Suggested next steps for Beta:
|
||
- Decide which Alpha items must land before Beta starts.
|
||
- Resolve overlaps (Memory appears in both Alpha and Beta) and consolidate the plan.
|
||
|
||
---
|
||
|
||
## 📦 Backlog / Unmilestoned Features
|
||
Lower-priority, exploratory, or undecided items to consider batching into future milestones.
|
||
|
||
- #23 — 📢 Broadcast / Announcement Mode
|
||
- #21 — 📈 Analytics Dashboard
|
||
- #20 — Shopper Assist
|
||
- #19 — 🚨 Content-aware moderation assist
|
||
- #14 — 📊 Engagement-based adjustment
|
||
- #13 — Context-aware scheduling
|
||
- #12 — Bot can be given some power to change the server a bit
|
||
- #11 — 🗓️ Scheduled specific times/dates
|
||
|
||
Suggested backlog housekeeping:
|
||
- Group these into thematic milestones: e.g. "Admin Tools", "Analytics", "Media & Vision".
|
||
- Add rough estimates (S/M/L) and owners for each item.
|
||
|
||
---
|
||
|
||
## How to use this roadmap
|
||
- Update issue bodies with acceptance criteria and subtask checklists.
|
||
- Assign owners and estimate effort for each Alpha item.
|
||
- Use the Forgejo milestone due dates to prioritize development sprints.
|
||
|
||
---
|
||
|
||
_Generated: Sep 19, 2025 — synchronized with repository milestones and open feature issues._
|
||
# 📍 DeltaBot Development Roadmap
|
||
|
||
This roadmap tracks the major phases of DeltaBot — from MVP to full AI companion chaos. ✅ = complete
|
||
|
||
---
|
||
|
||
## 🚀 v1.0 – MVP (Minimum Viable Persona)
|
||
> Core features to make Delta feel alive, sassy, and functional
|
||
|
||
- [x] `!chat` command (Ollama integration)
|
||
- [x] `!roast` command with cooldown
|
||
- [x] `!setpersona` command (dynamic prompt injection)
|
||
- [x] Persona stored in `persona.json`
|
||
- [x] AI replies styled using persona data
|
||
- [x] Global command cooldowns (from `settings.yml`)
|
||
- [x] Customizable cooldown message
|
||
- [ ] 🔧 Emoji bug from `settings.yml` (minor visual issue)
|
||
|
||
---
|
||
|
||
## 🌀 v1.1 – Immersion Boost
|
||
> Makes Delta behave like a *social creature*, not a command-line tool
|
||
|
||
- [ ] Allow `@Delta` mentions to trigger chat
|
||
- [ ] React to messages using emoji
|
||
- [ ] Pass user info into prompts (e.g. usernames, roles)
|
||
- [ ] Code refactor for better modularity
|
||
|
||
---
|
||
|
||
## 🧠 v2.0 – Aware Mode
|
||
> Delta becomes aware of conversation flow and personal context
|
||
|
||
- [ ] Context-aware replies using last X messages
|
||
- [ ] Track user interactions (e.g. roast frequency)
|
||
- [ ] Mood-based personality tuning (toggle sass vs support)
|
||
- [ ] Persistent memory (lightweight DB or JSON)
|
||
|
||
---
|
||
|
||
## 👁️ v2.5 – Senses Unlocked
|
||
> Delta gains real-world awareness through media and browsing
|
||
|
||
- [ ] Image interpretation (via BLIP, CLIP, or API)
|
||
- [ ] Meme analysis / reactions
|
||
- [ ] Web search integration (DuckDuckGo, Reddit, etc.)
|
||
- [ ] Meme scheduler with smart timing
|
||
|
||
---
|
||
|
||
## 💥 v3.0 – Chaotic Sentience
|
||
> Delta becomes a dynamic, evolving Discord resident
|
||
|
||
- [ ] Channel or role manipulation (opt-in)
|
||
- [ ] Scheduled mood/behavior shifts (e.g. “Friday Delta”)
|
||
- [ ] Admin dashboard for tuning Delta’s behavior
|
||
- [ ] Full multi-server support with Docker deployment
|
||
|
||
---
|
||
|
||
🧪 *Built with love, Ollama, and an unhealthy amount of sass.*
|
||
|
||
_Last updated: May 8, 2025_
|