rckrdmrd/trading-platform
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
fd6c39d220
trading-platform/orchestration/tareas/_archive/2026-01/TASK-2026-01-26-OQI-007-LLM-ASSISTANT-PANELS/01-CONTEXTO.md
Adrian Flores Cortes df43dd90cb [F0-F2] feat: Coherence analysis baseline + entity types + frontend stores 
FASE 0 - Preparación y Purga:
- Archived 21 completed tasks to _archive/2026-01/
- Marked 4 docs as DEPRECATED
- Created 3 baseline coherence reports

FASE 1 - DDL-Backend Coherence:
- audit.types.ts: +4 types (SystemEvent, TradingAudit, ApiRequestLog, DataAccessLog)
- investment.types.ts: +4 types (RiskQuestionnaire, WithdrawalRequest, DailyPerformance, DistributionHistory)
- entity.types.ts: +5 types (Symbol, TradingBot, TradingSignal, TradingMetrics, PaperBalance)

FASE 2 - Backend-Frontend Coherence:
- investmentStore.ts: New Zustand store with 20+ actions
- mlStore.ts: New Zustand store with signal caching
- alerts.service.ts: New service with 15 functions

FASE 3 - Documentation:
- OQI-009: Updated to 100% coverage, added ET-MKT-004-productos.md
- OQI-010: Created full structure (STATUS.md, ROADMAP-MT4.md, ET-MT4-001-gateway.md)

Coherence Baseline Established:
- DDL-Backend: 31% (target 95%)
- Backend-Frontend: 72% (target 85%)
- Global: 39.6% (target 90%)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-28 22:08:04 -06:00

1.3 KiB
Raw Blame History

01 - CONTEXTO

Identificacion

  • Tarea: TASK-2026-01-26-OQI-007-LLM-ASSISTANT-PANELS
  • Epic: OQI-007 (LLM Strategy Agent)
  • Fecha: 2026-01-26
  • Agente: Claude Opus 4.5

Situacion Actual

El modulo assistant del frontend tiene 18 componentes existentes pero carece de:

  • Manejo de errores robusto (error boundaries)
  • Indicadores de estado de conexion
  • Visualizacion de consumo de tokens
  • Biblioteca de templates de prompts

Justificacion

Problema

El LLM Strategy Agent requiere componentes de soporte para:

  1. Resiliencia: Capturar errores sin crashear toda la app
  2. UX: Mostrar estado de conexion en tiempo real
  3. Costos: Visualizar consumo de tokens y costos
  4. Productividad: Templates de prompts reutilizables

Beneficio Esperado

  • Mejor experiencia de usuario
  • Reduccion de tickets de soporte
  • Control de costos de API
  • Mayor productividad en analisis

Alcance

En Scope

  • ErrorBoundary.tsx - React error boundary
  • ConnectionStatus.tsx - WebSocket/API indicator
  • TokenUsageDisplay.tsx - Token consumption display
  • PromptLibrary.tsx - Prompt template browser

Fuera de Scope

  • Integracion con backend
  • Persistencia de datos
  • Tests unitarios

Referencias

  • FRONTEND_INVENTORY.yml: assistant module
  • MASTER_INVENTORY.yml: OQI-007 section
  • docs/02-definicion-modulos/OQI-007-llm-strategy-agent/