ilia
4b9ffb5ddf
- Enhanced `ARCHITECTURE.md` with details on LLM models for work (Llama 3.1 70B Q4) and family agents (Phi-3 Mini 3.8B Q4). - Introduced new documents: - `ASR_EVALUATION.md` for ASR engine evaluation and selection. - `HARDWARE.md` outlining hardware requirements and purchase plans. - `IMPLEMENTATION_GUIDE.md` for Milestone 2 implementation steps. - `LLM_CAPACITY.md` assessing VRAM and context window limits. - `LLM_MODEL_SURVEY.md` surveying open-weight LLM models. - `LLM_USAGE_AND_COSTS.md` detailing LLM usage and operational costs. - `MCP_ARCHITECTURE.md` describing the Model Context Protocol architecture. - `MCP_IMPLEMENTATION_SUMMARY.md` summarizing MCP implementation status. These updates provide comprehensive guidance for the next phases of development and ensure clarity in project documentation.
Kanban Tickets
This directory contains all project tickets organized by their kanban status.
Directory Structure
- backlog/: Future work items that are planned but not yet ready to start
- todo/: Items that are ready to be worked on
- in-progress/: Items currently being actively developed
- review/: Items that are complete but awaiting review, testing, or approval
- done/: Completed items (archived for reference)
Ticket Naming Convention
Tickets should be named using the format:
[TICKET-ID]_[short-description].md
Example: TICKET-001_setup-project-structure.md
Workflow
- Create: New tickets start in
backlog/ortodo/depending on readiness - Start Work: Move ticket from
todo/toin-progress/when starting - Complete: Move ticket from
in-progress/toreview/when implementation is done - Approve: Move ticket from
review/todone/when approved/merged
Using with Vibe Kanban
- Create tickets in this directory structure
- Import or reference these tickets in your Vibe Kanban board
- Keep ticket files in sync with kanban board status
- Use ticket IDs to reference in commits and PRs
Template
Use TICKET_TEMPLATE.md when creating new tickets to ensure consistency.