Refactor/agentic architecture#25
Merged
Merged
Conversation
…in database folder for coherence Data files should not be tracked per .gitignore policy. Files remain locally but are no longer in git.
Move old frontend, parser, scraper, and retriever services to legacy/ folder as part of architectural refactor. New agent-based retriever and pusher services replace the legacy implementation. - Migrate legacy services to legacy/services/ - Move legacy docker-compose and Makefile to legacy/ - Preserve database schemas in legacy/database/ - New services use agent-based architecture
Preserve old implementation for reference: - services/frontend/ → legacy/services/frontend/ - services/parser/ → legacy/services/parser/ - services/scraper/ → legacy/services/scraper/ - services/retriever/ (old) → legacy/services/retriever/ - docker-compose.yml → legacy/docker-compose.yml - docker-compose.override.yml → legacy/docker-compose.override.yml - Makefile → legacy/Makefile - database/ → legacy/database/
Add Neo4j client module to retriever service: - services/retriever/agent/clients/neo4j_client.py - Update config.py with Neo4j settings
Implement core agent architecture: - Orchestrator: routes queries and manages conversation flow - DBQueryAgent: generates and executes Neo4j Cypher queries - SafetyGuard: validates queries and enforces safety constraints
Complete retriever service implementation: - FastAPI endpoints for chat and query - Service configuration and Dockerfile - Dependencies (pyproject.toml, uv.lock)
New service for multimodal event submission: - Basic API structure with health endpoint - Configuration and Dockerfile - Observability integration
Update infrastructure to support new services: - docker-compose.yml: retriever and pusher services - docker-compose.override.yml: development configuration - Makefile: new service commands - Dev-container: update dev-container
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🏗️ Refactor: Agent-Based Neo4j Architecture
Major architectural refactor migrating from PostgreSQL RAG to agent-based Neo4j architecture.
Changes
legacy/folderBreaking Changes
NEO4J_URI,NEO4J_USERNAME,NEO4J_PASSWORDBenefits