This document indexes all memory bank files for easy reference.
- Project vision and purpose
- Target users and scope
- MVP vs Phase 2+ features
- Success criteria and milestones
- Read this first for project overview
- Architecture overview
- Service layer design
- API contract specifications
- Data flow diagrams
- Cache strategy
- Database schema
- Key architectural decisions
- Technology choices and rationale
- Trade-offs and alternatives considered
- Justification for major decisions
- Tech stack detailed breakdown
- Language and framework versions
- Library versions and dependencies
- Performance characteristics
- Scalability considerations
- Phase-by-phase completion tracker
- Task status (completed, in-progress, TODO)
- Outstanding items with priority
- Recent updates and dates
- Update this regularly
development-status.md [NEW]
- Comprehensive status report
- Component implementation status
- Test results summary
- Architecture diagrams
- Quality metrics
- Read for current full status
- Complete feature list
- MVP vs future features
- Feature descriptions and use cases
- Implementation status
- Acceptance criteria
- API endpoint specifications
- Request/response schemas
- Error codes and messages
- Rate limiting and quotas
- Authentication (future)
- Optimization algorithms used
- Maximum Sharpe ratio approach
- Efficient frontier generation
- Ledoit-Wolf covariance
- Performance benchmarks
- Test pyramid structure
- Unit test coverage targets
- Integration test scope
- E2E test scenarios
- Performance testing approach
- CI/CD pipeline requirements
- Deployment architecture
- Environment configurations
- Database setup and migration
- Scaling strategy
- Monitoring and logging
- Disaster recovery
- Yahoo Finance integration
- Data quality requirements
- Historical data specifications
- Real-time vs batch updates
- Data refresh strategy
- Current focus and priorities
- Active work items
- Immediate blockers
- Assumptions and constraints
- Context for current phase
- Update before starting new phase
- Frontend structure created
- Component descriptions
- Page specifications
- API integration details
- Styling and responsive design
- Reference for frontend architecture
- Get running in 2 minutes
- Quick command reference
- Troubleshooting guide
- Key features overview
- Start here for hands-on work
- Phase 8 summary and status
- What was accomplished
- File structure created
- Features implemented
- Next steps (Phase 9)
- Read for Phase 8 context
- Phase-by-phase checklist (Phases 1-15)
- Sub-tasks for each phase
- Sample test cases
- Current status dashboard
- Future phases overview
- Use to track progress
- Start with projectBrief.md - Understand the vision
- Read systemPatterns.md - Learn the architecture
- Check progress.md - See what's done
- Open QUICKSTART.md - Start running code
- Check features.md - Find your feature
- Review systemPatterns.md - Understand where it fits
- Look at api-spec.md - See API contract
- Check tests in relevant test files
- Consult QUICKSTART.md - Quick troubleshooting section
- Check techContext.md - Technology details
- Review deployment.md - Environment issues
- Look at testing-strategy.md - Test-related issues
- Read deployment.md - Full deployment guide
- Check data-sources.md - Data setup requirements
- Review testing-strategy.md - Pre-deployment testing
- Review decisions.md - Why each choice was made
- Check systemPatterns.md - How it's implemented
- Look at techContext.md - Technology context
Update progress.md:
- After completing a task
- When starting a new phase
- When encountering blockers
- When changing priorities
- At least once per day during development
Update activeContext.md:
- Before each work session
- When switching contexts/tasks
- When assumptions change
- Before switching team members in
Update IMPLEMENTATION_CHECKLIST.md:
- When completing a major phase
- When adding/removing tasks
- When re-prioritizing work
Create PHASE_N_COMPLETION.md:
- When completing each major phase
- Summarize what was accomplished
- List files created/modified
- Link to relevant documentation
- Describe next steps
- Separation of Concerns: Each document focuses on one aspect
- Cross-referencing: Links between related documents
- Versioning: Dates on changes to track evolution
- Actionability: Documents guide decisions and actions
- Completeness: Enough detail to implement without the author
Just started working here?
- QUICKSTART.md ← Start here
Need project overview?
- projectBrief.md ← Read this
Need current status?
- development-status.md ← Check this
Need architecture details?
- systemPatterns.md ← Review this
Need to track progress?
- IMPLEMENTATION_CHECKLIST.md ← Use this
Need to understand decisions?
- decisions.md ← Read this
Need API details?
- api-spec.md ← Reference this
Need deployment help?
- deployment.md ← Follow this
| Type | Count | Files |
|---|---|---|
| Core Documentation | 7 | projectBrief, systemPatterns, decisions, techContext, features, api-spec, ml-models |
| Progress Tracking | 2 | progress.md, activeContext.md |
| Operations | 4 | testing-strategy, deployment, data-sources, frontend-scaffolding |
| Quick Reference | 3 | QUICKSTART, PHASE8_COMPLETION, IMPLEMENTATION_CHECKLIST |
| TOTAL | 16 | Documents |
- Date: 2025-12-13
- Phase: 8 (Frontend Scaffolding Complete)
- Status: ✅ Ready for Phase 9 (Local Integration Testing)
For questions about documents, see activeContext.md