workspace-v1/04-fase-proyectos/trading-platform
Adrian Flores Cortes 967ab360bb Initial commit: Workspace v1 with 3-layer architecture
Structure:
- control-plane/: Registries, SIMCO directives, CI/CD templates
- projects/: Gamilit, ERP-Suite, Trading-Platform, Betting-Analytics
- shared/: Libs catalog, knowledge-base

Key features:
- Centralized port, domain, database, and service registries
- 23 SIMCO directives + 6 fundamental principles
- NEXUS agent profiles with delegation rules
- Validation scripts for workspace integrity
- Dockerfiles for all services
- Path aliases for quick reference

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

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-23 00:35:19 -06:00
..
README.md Initial commit: Workspace v1 with 3-layer architecture 2025-12-23 00:35:19 -06:00

FASE 4.3: MIGRACION TRADING PLATFORM

Proyecto: Trading Platform Estado: Pendiente Prioridad: P2 Complejidad: Alta (Microservicios) Dependencias: Fase 4.1, 4.2 completadas


OBJETIVO

Migrar Trading Platform considerando:

  1. Arquitectura de microservicios
  2. Servicios ML/Python
  3. Servicios LLM
  4. Multiples backends

INFORMACION DEL PROYECTO

Campo Valor
Nombre Trading Platform
Tipo Plataforma de analisis/trading
Stack Backend Express + FastAPI (Python)
Stack Frontend React
Servicios API, ML Engine, LLM Agent, Web

Puertos (de registry)

Servicio Puerto
api 3020
web 3021
ml_engine 3022
llm_agent 3023

ESTRUCTURA OBJETIVO

trading-platform/
|
+-- apps/
|     +-- backend/           # Express API
|     +-- frontend/          # React
|     +-- ml-engine/         # Python/FastAPI
|     +-- llm-agent/         # Python/FastAPI
|     +-- database/
|
+-- docker/
|     +-- docker-compose.yml
|
+-- orchestration/
+-- docs/

CONSIDERACIONES ESPECIALES

  1. Multiples runtimes: Node + Python
  2. Servicios ML: Requieren GPU o recursos especiales
  3. Inter-service communication: API llama a ML y LLM
  4. Datos sensibles: Estrategias de trading

TAREAS PRINCIPALES

  1. Crear estructura
  2. Service descriptors para cada servicio (4 total)
  3. Migrar codigo por servicio
  4. Docker compose unificado
  5. Validacion

Agente Responsable: Tech-Leader + Backend-Agent + ML-Agent