rckrdmrd/trading-platform
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
381ec6ee7a
trading-platform/orchestration/analisis/coherencia/GAPS-TRACKING.yml
Adrian Flores Cortes 090fe5d278 feat: Add Trading Agents types for frontend 
Create comprehensive TypeScript type definitions for Trading Agents (Atlas, Orion, Nova) in the frontend.

- Align with backend trading-agents.client.ts interfaces
- Export AgentType, AgentStatus, BotStatus types
- Define TradingBot, AgentMetrics, AgentPosition, AgentTrade interfaces
- Include utility functions for status mapping and display names
- Full JSDoc documentation for all types
- Export from main types/index.ts

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-27 15:40:04 -06:00

432 lines
13 KiB
YAML
Raw Blame History

# ==============================================================================
# Gaps Tracking - Trading Platform
# Generated: 2026-01-27
# ==============================================================================
version: "1.0.0"
project: "trading-platform"
total_gaps: 18
completed_gaps: 0
in_progress_gaps: 0
# ==============================================================================
# P1 - Gaps Críticos (Acción Inmediata)
# ==============================================================================
p1_gaps:
- id: GAP-001
title: "Market Data OHLCV Service"
priority: "P1"
status: "pending"
schema: "market_data"
tables:
- market_data.ohlcv_5m
- market_data.ohlcv_15m
description: |
Las tablas OHLCV no tienen servicios backend. Los charts del frontend
necesitan consultar estos datos via API REST.
impact: "alto"
effort: "medio"
estimated_hours: 16
assigned_to: null
created_at: "2026-01-27"
due_date: null
deliverables:
- file: "apps/backend/src/modules/market-data/services/marketData.service.ts"
type: "service"
methods:
- getOHLCV(symbol, timeframe, limit?)
- getLatestCandles(symbol, timeframe)
- getHistoricalData(symbol, from, to)
- getCandlesByRange(symbol, timeframe, start, end)
- file: "apps/backend/src/modules/market-data/types/market-data.types.ts"
type: "interfaces"
interfaces:
- OHLCV
- Timeframe
- CandleQueryOptions
- file: "apps/backend/src/modules/market-data/controllers/market-data.controller.ts"
type: "controller"
endpoints:
- "GET /api/market-data/ohlcv/:symbol/:timeframe"
- "GET /api/market-data/historical/:symbol"
- file: "apps/backend/src/modules/market-data/market-data.module.ts"
type: "module"
tests:
- file: "apps/backend/src/modules/market-data/services/marketData.service.spec.ts"
- file: "apps/backend/src/modules/market-data/controllers/market-data.controller.spec.ts"
dependencies:
- market_data schema debe estar poblado con datos
- Integración con data-service Python (opcional)
acceptance_criteria:
- "[ ] Servicio puede consultar ohlcv_5m y ohlcv_15m"
- "[ ] Endpoint REST responde en <500ms para 100 candles"
- "[ ] Tipos TypeScript correctamente definidos"
- "[ ] Tests unitarios cubren >80%"
- "[ ] Documentación Swagger completa"
- "[ ] Frontend puede consumir endpoints"
- id: GAP-002
title: "Notification Service y Push Tokens"
priority: "P1"
status: "pending"
schema: "auth"
tables:
- auth.notifications
- auth.user_push_tokens
description: |
Sistema de notificaciones existe en DDL pero sin servicios backend.
Usuarios no pueden consultar ni gestionar notificaciones.
impact: "alto"
effort: "medio"
estimated_hours: 20
assigned_to: null
created_at: "2026-01-27"
due_date: null
deliverables:
- file: "apps/backend/src/modules/notifications/services/notification.service.ts"
type: "service"
methods:
- getUserNotifications(userId, filters?)
- markAsRead(notificationId)
- markAllAsRead(userId)
- deleteNotification(notificationId)
- sendNotification(userId, notification)
- file: "apps/backend/src/modules/notifications/services/push.service.ts"
type: "service"
methods:
- registerPushToken(userId, token, platform)
- unregisterPushToken(tokenId)
- sendPushNotification(userId, payload)
- sendBulkPushNotifications(userIds, payload)
- file: "apps/backend/src/modules/notifications/types/notification.types.ts"
type: "interfaces"
interfaces:
- Notification
- NotificationType
- PushToken
- PushPayload
- file: "apps/backend/src/modules/notifications/controllers/notification.controller.ts"
type: "controller"
endpoints:
- "GET /api/notifications"
- "POST /api/notifications/:id/read"
- "DELETE /api/notifications/:id"
- "POST /api/notifications/push-token"
- file: "apps/backend/src/modules/notifications/notifications.module.ts"
type: "module"
tests:
- file: "apps/backend/src/modules/notifications/services/notification.service.spec.ts"
- file: "apps/backend/src/modules/notifications/services/push.service.spec.ts"
dependencies:
- Firebase Cloud Messaging o OneSignal para push
- WebSocket para notificaciones en tiempo real (opcional)
acceptance_criteria:
- "[ ] Usuarios pueden ver sus notificaciones"
- "[ ] Usuarios pueden marcar como leídas"
- "[ ] Push tokens se registran correctamente"
- "[ ] Push notifications se envían vía FCM/OneSignal"
- "[ ] Tests cubren casos principales"
- "[ ] Frontend notifica en tiempo real"
# ==============================================================================
# P2 - Gaps Importantes (Corto Plazo)
# ==============================================================================
p2_gaps:
- id: GAP-003
title: "Audit Service - Consultas de Logs"
priority: "P2"
status: "pending"
schema: "audit"
tables:
- audit.audit_logs
- audit.security_events
- audit.trading_audit
- audit.api_request_logs
description: |
Sistema de auditoría registra logs via triggers/middleware pero no
hay servicios para consultarlos. Admin dashboard necesita estos datos.
impact: "medio"
effort: "grande"
estimated_hours: 32
assigned_to: null
created_at: "2026-01-27"
due_date: null
deliverables:
- file: "apps/backend/src/modules/audit/services/audit.service.ts"
type: "service"
methods:
- getAuditLogs(filters)
- getSecurityEvents(filters)
- getTradingAudit(botId, filters)
- getAPIRequestLogs(filters)
- exportAuditReport(from, to)
- file: "apps/backend/src/modules/audit/types/audit.types.ts"
type: "interfaces"
- file: "apps/backend/src/modules/audit/controllers/audit.controller.ts"
type: "controller"
endpoints:
- "GET /api/audit/logs"
- "GET /api/audit/security-events"
- "GET /api/audit/trading/:botId"
- "GET /api/audit/export"
acceptance_criteria:
- "[ ] Admin puede consultar audit logs"
- "[ ] Filtros por fecha, usuario, tipo de evento"
- "[ ] Paginación para grandes volúmenes"
- "[ ] Export a CSV/JSON"
- "[ ] Endpoints protegidos (admin only)"
- id: GAP-004
title: "Currency Exchange Service"
priority: "P2"
status: "pending"
schema: "financial"
tables:
- financial.currency_exchange_rates
description: |
Sistema multi-moneda (USD, MXN, EUR) necesita servicio de conversión
con sincronización automática de tasas de cambio.
impact: "medio"
effort: "medio"
estimated_hours: 16
assigned_to: null
created_at: "2026-01-27"
due_date: null
deliverables:
- file: "apps/backend/src/modules/financial/services/currencyExchange.service.ts"
type: "service"
methods:
- getExchangeRate(from, to, date?)
- convertAmount(amount, from, to)
- syncRatesFromAPI()
- getHistoricalRates(from, to, startDate, endDate)
- file: "apps/backend/src/modules/financial/types/currency.types.ts"
type: "interfaces"
dependencies:
- API externa: CoinGecko, ExchangeRate-API, o similar
- Cron job para sincronización diaria
acceptance_criteria:
- "[ ] Conversión USD <-> MXN <-> EUR"
- "[ ] Sync automático de tasas diarias"
- "[ ] Fallback a tasas anteriores si API falla"
- "[ ] Cache de tasas recientes"
- id: GAP-005
title: "Risk Assessment Service"
priority: "P2"
status: "pending"
schema: "investment"
tables:
- investment.risk_questionnaire
description: |
Usuarios completan cuestionario de riesgo pero no hay servicio
para gestionar respuestas ni calcular perfil.
impact: "medio"
effort: "medio"
estimated_hours: 12
assigned_to: null
created_at: "2026-01-27"
due_date: null
deliverables:
- file: "apps/backend/src/modules/investment/services/riskAssessment.service.ts"
type: "service"
methods:
- submitQuestionnaire(userId, answers)
- calculateRiskProfile(answers)
- getUserRiskProfile(userId)
- retakeQuestionnaire(userId)
acceptance_criteria:
- "[ ] Usuarios pueden completar cuestionario"
- "[ ] Perfil de riesgo se calcula automáticamente"
- "[ ] Resultados se almacenan en risk_questionnaire table"
- "[ ] Validación de respuestas"
- id: GAP-006
title: "Course Reviews"
priority: "P2"
status: "pending"
schema: "education"
tables:
- education.course_reviews
description: |
Tabla de reviews existe pero no hay endpoints para crear/consultar.
impact: "bajo"
effort: "pequeño"
estimated_hours: 6
assigned_to: null
created_at: "2026-01-27"
due_date: null
deliverables:
- file: "apps/backend/src/modules/education/services/course.service.ts"
type: "service"
methods:
- createReview(userId, courseId, rating, review)
- getCourseReviews(courseId, pagination)
- updateReview(reviewId, data)
- deleteReview(reviewId)
acceptance_criteria:
- "[ ] Usuarios pueden crear reviews"
- "[ ] Reviews se muestran en curso"
- "[ ] Rating promedio se calcula"
- "[ ] Validación: 1 review por usuario por curso"
- id: GAP-007
title: "Login Attempts Tracking"
priority: "P2"
status: "pending"
schema: "auth"
tables:
- auth.login_attempts
description: |
Tabla registra intentos de login pero no hay consultas para
análisis de seguridad.
impact: "bajo"
effort: "pequeño"
estimated_hours: 4
assigned_to: null
created_at: "2026-01-27"
due_date: null
deliverables:
- file: "apps/backend/src/modules/auth/services/token.service.ts"
type: "service"
methods:
- getLoginAttempts(email?, ip?, limit)
- getFailedAttempts(userId)
- analyzeLoginPatterns(userId)
acceptance_criteria:
- "[ ] Admin puede consultar login attempts"
- "[ ] Filtros por email, IP, fecha"
- "[ ] Detección de patrones sospechosos"
# ==============================================================================
# P3 - Gaps Menores (Largo Plazo)
# ==============================================================================
p3_gaps:
- id: GAP-008
title: "Distribution Runs Admin"
priority: "P3"
status: "pending"
schema: "investment"
tables:
- investment.distribution_runs
description: "Admin endpoint para gestionar distribution runs"
impact: "bajo"
effort: "pequeño"
estimated_hours: 4
- id: GAP-009
title: "System Events Queries"
priority: "P3"
status: "pending"
schema: "audit"
tables:
- audit.system_events
- audit.data_access_logs
description: "Consultas de system events en audit.service.ts"
impact: "bajo"
effort: "pequeño"
estimated_hours: 4
- id: GAP-010
title: "Compliance Service (KYC/AML)"
priority: "P3"
status: "pending"
schema: "audit"
tables:
- audit.compliance_logs
description: "Futuro compliance.service.ts para KYC/AML"
impact: "bajo"
effort: "grande"
estimated_hours: 40
- id: GAP-011
title: "Rate Limiting Config Admin"
priority: "P3"
status: "pending"
schema: "auth"
tables:
- auth.rate_limiting_config
description: "Admin endpoint para configurar rate limits"
impact: "bajo"
effort: "pequeño"
estimated_hours: 4
# ==============================================================================
# Estadísticas
# ==============================================================================
statistics:
by_priority:
P1: 2
P2: 5
P3: 4
by_status:
pending: 11
in_progress: 0
completed: 0
by_effort:
pequeño: 5
medio: 5
grande: 1
total_estimated_hours: 162
# ==============================================================================
# Notas de Tracking
# ==============================================================================
tracking_notes: |
Este archivo debe actualizarse cuando:
- Se inicia trabajo en un gap (status: in_progress)
- Se completa un gap (status: completed)
- Se reasigna prioridad de un gap
- Se asigna desarrollador a un gap
- Se estima nueva fecha de entrega
Para marcar un gap como completado:
1. Cambiar status a "completed"
2. Agregar completed_at con fecha
3. Agregar pull_request con URL del PR
4. Validar que todos los acceptance_criteria estén cumplidos
Formato para gaps completados:
- id: GAP-XXX
status: "completed"
completed_at: "2026-XX-XX"
completed_by: "Developer Name"
pull_request: "https://github.com/org/repo/pull/XXX"
review_status: "approved"
last_updated: "2026-01-27"
next_review: "2026-02-15"
Reference in New Issue View Git Blame Copy Permalink