docs: update README and roadmap for v1.2.0

README.md:
- Add household staff table with current status
- Update requirements to list external services
- Add Redis, Qdrant to configuration section
- Update project structure with new modules
- Update version to 1.2.0

IMPLEMENTATION_ROADMAP.md:
- Update current state to v1.2.0
- Mark Phase 2 (Steward) as complete
- Mark Phase 3 (Butler coordination) as complete
- Update Phase 4 with Librarian and Biographer complete
- Mark Phase 6 (Services) as complete
- Update Phase 8 (Memory) with completed items
- Update next steps

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

IMPLEMENTATION_ROADMAP.md

@@ -4,35 +4,37 @@
 
 This document outlines the phased implementation plan to transform the current OpenAI-compatible API into the full Tatlock household butler system.
 
-## Current State (v0.1.1+ - Phase 1 Mostly Complete)
+## Current State (v1.2.0 - Phase F Complete)
 
 **What we have**:
 - ✅ **The Orchestrator** - FastAPI infrastructure layer
   - OpenAI-compatible API endpoints (Responses API + Chat Completions)
   - Streaming coordination and conversation management
   - Response format with reasoning support
-  - Test infrastructure (131 tests, 81.78% coverage)
-- ✅ **Tatlock Agent** - Real PydanticAI integration
-  - Connected to Ollama (mistral-nemo:latest)
-  - British butler personality with research mindset
-  - Streaming responses with reasoning
-  - Tool calling framework functional
-- ✅ **Permanent Tools**
-  - Calculator (safe mathematical expressions)
-  - Date/Time toolkit (current time, relative dates, time differences)
-  - Web search (SearXNG integration)
+  - Test infrastructure (~400 tests)
+- ✅ **Two-Tier Architecture**
+  - The Steward analyzes requests and recommends capabilities
+  - Tatlock coordinates execution with scoped tools
+  - Real-time streaming of analysis and reasoning
+- ✅ **Household Staff**
+  - **Tatlock** (Butler): Primary interface with witty personality
+  - **The Steward**: Request analysis and capability recommendation
+  - **The Librarian**: Research via library-desk HybridRAG + wiki
+  - **The Biographer**: User memory, profiles, preferences, semantic recall
+- ✅ **Core Tools**
+  - Calculator, Date/Time toolkit, Web search (SearXNG)
+- ✅ **Memory System**
+  - Direct access layer (memory_service) for fast lookups
+  - Vector storage (Qdrant) for semantic recall
+  - Session cache (Redis) with 24h TTL
+  - Multi-tenancy via ContextVar
 - ✅ Mock agent (lorem-tester for testing)
-- ✅ Agent interface abstraction
 
 **What we need**:
-- **The Household** - Full multi-agent coordination:
-  - The Steward (first-tier request analysis)
-  - Tatlock coordination layer (expert agent delegation)
-  - Expert household staff agents (Librarian, Developer, Handyman, etc.)
-- Multi-tenant database architecture
-- Containerized service ecosystem
+- More household staff (Developer, Secretary, Handyman, Housekeeper)
 - MCP (Model Context Protocol) integration
 - Dynamic model switching for specialized tasks
+- Full multi-tenant database (PostgreSQL)
 
 ---
 
@@ -359,15 +361,18 @@ User Request → Orchestrator → Steward Analysis → Recommendations → Tatlo
 
 ### Success Criteria
 
-- [ ] **Steward analyzes incoming requests** using PydanticAI agent
-- [ ] **Produces structured recommendations** (tools, agents, reasoning)
-- [ ] **Recommendations formatted as prepended note** to Tatlock
-- [ ] **Tool registry is queryable and extensible** via clean API
-- [ ] **Steward output visible in reasoning stream** for transparency
-- [ ] **Only recommended tools available** to Tatlock (scoped context)
-- [ ] **Base model stays loaded** between Steward and Tatlock calls
-- [ ] **Recommendations are accurate** (not over/under-inclusive)
-- [ ] **Integration tests pass** for full Steward → Tatlock flow
+- [x] **Steward analyzes incoming requests** using PydanticAI agent
+- [x] **Produces structured recommendations** (tools, agents, reasoning)
+- [x] **Recommendations formatted as prepended note** to Tatlock
+- [x] **Tool registry is queryable and extensible** via clean API
+- [x] **Steward output visible in reasoning stream** for transparency
+- [x] **Only recommended tools available** to Tatlock (scoped context)
+- [x] **Base model stays loaded** between Steward and Tatlock calls
+- [x] **Recommendations are accurate** (not over/under-inclusive)
+- [x] **Integration tests pass** for full Steward → Tatlock flow
+
+### Status
+**✅ COMPLETE** (v0.2.5)
 
 ### Performance Targets
 
@@ -435,12 +440,15 @@ The Steward is the foundation of the household architecture. Without it, we'd ne
    - Wait time transparency
 
 ### Success Criteria
-- [ ] Tatlock receives enriched requests (user + Steward notes)
-- [ ] Only recommended tools are available
-- [ ] Tatlock coordinates multiple tool calls
-- [ ] All actions streamed to reasoning output
-- [ ] Responses have consistent personality
-- [ ] Synthesizes multi-source results coherently
+- [x] Tatlock receives enriched requests (user + Steward notes)
+- [x] Only recommended tools are available
+- [x] Tatlock coordinates multiple tool calls
+- [x] All actions streamed to reasoning output
+- [x] Responses have consistent personality
+- [x] Synthesizes multi-source results coherently
+
+### Status
+**✅ COMPLETE** (v1.1.0)
 
 ### Estimated Effort
 **4-5 weeks** - Complex coordination logic
@@ -453,39 +461,44 @@ The Steward is the foundation of the household architecture. Without it, we'd ne
 
 ### Priority Expert Agents
 
-1. **The Librarian** (Research & Knowledge Management) ⭐ **Priority**
-   - Research assistance and synthesis
-   - Automatic research dossier generation
-   - Knowledge base queries and organization
-   - Reference management
-   - Wiki integration (future: dedicated wiki container)
-   - Mind map maintenance (future)
-   - *Rationale: Helps guide development priorities through better research*
+1. **The Librarian** (Research & Knowledge Management) ✅ **COMPLETE** (v1.1.0)
+   - Research assistance via library-desk HybridRAG
+   - Wiki page management (search, create, update)
+   - Semantic vector search
+   - Knowledge graph queries
+   - Dossier browsing
 
-2. **The Developer** (Software Development)
+2. **The Biographer** (User Memory) ✅ **COMPLETE** (v1.2.0)
+   - User profile management (name, location, timezone)
+   - Preference storage (units, theme)
+   - Semantic memory recall ("What car do I drive?")
+   - Fact storage from conversations
+   - Session context caching
+
+3. **The Developer** (Software Development) 🔜 **Planned**
    - Code generation assistance
    - Debugging support
    - Documentation generation
    - Architecture guidance
    - *Rationale: Directly supports building the system itself*
 
-3. **The Handyman** (System Maintenance)
+4. **The Handyman** (System Maintenance) 🔜 **Planned**
    - System status queries
    - Log analysis
    - Basic troubleshooting
    - Infrastructure monitoring
 
-4. **The Secretary** (Scheduling & Organization)
-   - Calendar integration (placeholder)
-   - Task management (placeholder)
+5. **The Secretary** (Scheduling & Organization) 🔜 **Planned**
+   - Calendar integration
+   - Task management
    - Reminder system
    - Schedule conflict detection
 
-5. **The Housekeeper** (Home Automation)
+6. **The Housekeeper** (Home Automation) 🔜 **Planned**
+   - Home Assistant integration
    - Device control interface
    - Status queries
    - Automation triggers
-   - Environmental monitoring
 
 ### Each Agent Includes
 - Specialized prompt and personality
@@ -494,12 +507,15 @@ The Steward is the foundation of the household architecture. Without it, we'd ne
 - Integration with Butler orchestration
 
 ### Success Criteria
-- [ ] Each agent implemented as separate module
-- [ ] Agents callable via tool framework
-- [ ] Agents use specialized prompts
-- [ ] Results integrate cleanly with Butler
+- [x] Each agent implemented as separate module
+- [x] Agents callable via tool framework
+- [x] Agents use specialized prompts
+- [x] Results integrate cleanly with Butler
 - [ ] Can invoke specialized models (e.g., Codestral for Developer)
 
+### Status
+**🔶 PARTIAL** - Librarian and Biographer complete, others planned
+
 ### Estimated Effort
 **6-8 weeks** - Parallel development possible
 
@@ -556,31 +572,37 @@ The core orchestration (Steward → Butler → Experts) can work entirely with i
 
 ### Services to Integrate
 
-1. **Redis (Memory & Caching)**
-   - Docker compose setup
-   - Conversation cache
-   - Short-term memory
-   - Session management
+1. **Redis (Memory & Caching)** ✅ **COMPLETE** (v1.2.0)
+   - Benchmark storage (db=1)
+   - Memory cache for sessions (db=2)
+   - 24h TTL for session context
+   - Recent entities tracking
 
-3. **Qdrant (Vector Storage)**
-   - Docker compose setup
-   - Long-term memory embeddings
-   - Semantic search
-   - Conversation history vectors
+2. **Qdrant (Vector Storage)** ✅ **COMPLETE** (v1.2.0)
+   - Per-user memory collections
+   - 768-dim nomic-embed-text vectors
+   - Semantic search for recall
+   - Type-based filtering
 
-4. **SearxNG (Web Search)**
-   - Docker compose setup
+3. **SearxNG (Web Search)** ✅ **COMPLETE** (v0.2.0)
    - Search tool integration
    - Result processing
    - Privacy-preserving queries
 
+4. **library-desk (Research API)** ✅ **COMPLETE** (v1.1.0)
+   - HybridRAG search
+   - Wiki management
+   - Knowledge graph queries
+
 ### Success Criteria
-- [ ] All services defined in docker-compose.yml
-- [ ] Services communicate correctly
-- [ ] Tatlock can invoke web search
-- [ ] Redis used for session data
-- [ ] Qdrant stores conversation embeddings
-- [ ] Ollama serves the base model
+- [x] Services communicate correctly
+- [x] Tatlock can invoke web search
+- [x] Redis used for session data
+- [x] Qdrant stores user memories
+- [x] Ollama serves the base model
+
+### Status
+**✅ COMPLETE** - All core services integrated
 
 ### Estimated Effort
 **3-4 weeks** - Infrastructure setup
@@ -629,33 +651,48 @@ The core orchestration (Steward → Butler → Experts) can work entirely with i
 
 ### Deliverables
 
-1. **Long-Term Memory**
-   - Conversation embedding pipeline
-   - Semantic search over history
-   - Memory consolidation
-   - Relevance ranking
+1. **Long-Term Memory** ✅ **COMPLETE** (v1.2.0 - Phase F)
+   - Memory service for direct key-based access
+   - Qdrant vector storage for semantic recall
+   - Embedding via nomic-embed-text
+   - The Biographer agent for memory management
 
-2. **Context Management**
+2. **Session Memory** ✅ **COMPLETE** (v1.2.0)
+   - Redis session cache with 24h TTL
+   - Recent entities tracking
+   - Conversation context preservation
+   - Multi-tenancy via ContextVar
+
+3. **Steward Integration** ✅ **COMPLETE** (v1.2.0)
+   - Memory pre-fetch during request analysis
+   - Profile/preferences included in context
+   - Keyword-based context determination
+
+4. **Context Management** 🔜 **Future**
    - Smart context window trimming
    - Conversation branching
    - Topic tracking
    - Memory retrieval integration
 
-3. **Personalization**
+5. **Personalization** 🔜 **Future**
    - User preference learning
    - Interaction pattern analysis
    - Adaptive responses
    - Custom agent personalities per user
 
 ### Success Criteria
+- [x] User facts stored in Qdrant with semantic search
+- [x] Profile and preferences accessible via memory_service
+- [x] Session context cached in Redis
+- [x] User preferences affect responses (via Steward pre-fetch)
 - [ ] Conversations automatically embedded to Qdrant
-- [ ] Relevant history retrieved for new requests
-- [ ] Context stays within model limits
-- [ ] User preferences affect responses
-- [ ] Memory improves over time
+- [ ] Memory improves over time (learning from interactions)
+
+### Status
+**🔶 PARTIAL** - Core memory system complete, advanced features planned
 
 ### Estimated Effort
-**4-5 weeks** - AI/ML heavy
+**4-5 weeks** - AI/ML heavy (remaining work)
 
 ---
 
@@ -871,13 +908,13 @@ Phase 9 (Extended Staff) → Phase 10 (UX) → Phase 11 (Production)
 
 ## Next Steps
 
-1. **Immediate**: Commit model name fix (Tatlock)
-2. **Week 1-2**: Begin Phase 1 (PostgreSQL + multi-tenancy design)
-3. **Week 3**: Parallel prototype of Steward agent
-4. **Ongoing**: Update this roadmap as we learn
+1. **Priority**: Implement The Developer agent for code assistance
+2. **Integration**: Add Home Assistant integration for The Housekeeper
+3. **Calendar**: Integrate scheduling service for The Secretary
+4. **Ongoing**: Add more household staff as needed
 
 ---
 
 **Document Status**: Active planning document
 **Created**: 2025-12-06
-**Last Updated**: 2025-12-06
+**Last Updated**: 2025-12-13