feat: control-pipeline Service aus Compliance-Repo migriert
Control-Pipeline (Pass 0a/0b, BatchDedup, Generator) als eigenstaendiger Service in Core, damit Compliance-Repo unabhaengig refakturiert werden kann. Schreibt weiterhin ins compliance-Schema der shared PostgreSQL. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
22
control-pipeline/requirements.txt
Normal file
22
control-pipeline/requirements.txt
Normal file
@@ -0,0 +1,22 @@
|
||||
# Web Framework
|
||||
fastapi>=0.123.0
|
||||
uvicorn[standard]>=0.27.0
|
||||
|
||||
# Database
|
||||
SQLAlchemy>=2.0.36
|
||||
psycopg2-binary>=2.9.10
|
||||
|
||||
# HTTP Client
|
||||
httpx>=0.28.0
|
||||
|
||||
# Validation
|
||||
pydantic>=2.5.0
|
||||
|
||||
# AI - Anthropic Claude
|
||||
anthropic>=0.75.0
|
||||
|
||||
# Vector DB (dedup)
|
||||
qdrant-client>=1.7.0
|
||||
|
||||
# Auth
|
||||
python-jose[cryptography]>=3.3.0
|
||||
Reference in New Issue
Block a user