DESKTOP-72TV0V4\caoxiaozhu
6f594631e9
Align the brain prompts, graph view, and startup defaults with the latest phase 1 flow so local runs and navigation stay consistent.
28 lines
1.2 KiB
Markdown
28 lines
1.2 KiB
Markdown
# Task Plan: Jarvis Knowledge Brain Phase 1 Blueprint
|
|
|
|
## Goal
|
|
Create a practical phase-1 implementation blueprint for the event-driven knowledge brain, covering backend models, services, scheduler jobs, retrieval integration, APIs, and frontend brain module structure.
|
|
|
|
## Phases
|
|
- [x] Phase 1: Plan and setup
|
|
- [x] Phase 2: Research/gather information
|
|
- [x] Phase 3: Draft blueprint
|
|
- [x] Phase 4: Review and deliver
|
|
|
|
## Key Questions
|
|
1. Which new persistence models are required for an event-driven knowledge brain?
|
|
2. How should existing conversation, document, todo, task, and forum data flow into the brain?
|
|
3. What should phase 1 include versus defer to later phases?
|
|
4. How should the frontend brain module be structured before full graph intelligence exists?
|
|
|
|
## Decisions Made
|
|
- Use an event-driven brain architecture instead of extending the current graph-only flow.
|
|
- Keep the current graph as a projection/view layer, not the brain source of truth.
|
|
- Phase 1 should prioritize unified ingestion, candidate generation, long-term memory storage, and retrieval integration.
|
|
|
|
## Errors Encountered
|
|
- None yet.
|
|
|
|
## Status
|
|
**Completed** - Separate implementation plan drafted in `knowledge_ingestion_plan.md` and supporting notes updated.
|