Add local project snapshots and plans

Capture the current local data snapshot and planning artifacts alongside
this development batch so the workspace state matches the code changes.
This preserves the reference materials and generated files that were
kept in the working tree.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-03-22 13:49:03 +08:00
parent 7d80a6e2ec
commit 90ea732584
47 changed files with 3553 additions and 119 deletions

27
task_plan.md Normal file
View File

@@ -0,0 +1,27 @@
# 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.