Workspace V1 agents

Go to file

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
00-plan-maestro	Initial commit: Workspace v1 with 3-layer architecture	2025-12-23 00:35:19 -06:00
01-fase-control-plane	Initial commit: Workspace v1 with 3-layer architecture	2025-12-23 00:35:19 -06:00
02-fase-core-orchestration	Initial commit: Workspace v1 with 3-layer architecture	2025-12-23 00:35:19 -06:00
03-fase-shared-infra	Initial commit: Workspace v1 with 3-layer architecture	2025-12-23 00:35:19 -06:00
04-fase-proyectos	Initial commit: Workspace v1 with 3-layer architecture	2025-12-23 00:35:19 -06:00
05-fase-shared-libs	Initial commit: Workspace v1 with 3-layer architecture	2025-12-23 00:35:19 -06:00
06-fase-knowledge-base	Initial commit: Workspace v1 with 3-layer architecture	2025-12-23 00:35:19 -06:00
07-fase-validacion-final	Initial commit: Workspace v1 with 3-layer architecture	2025-12-23 00:35:19 -06:00
control-plane	Initial commit: Workspace v1 with 3-layer architecture	2025-12-23 00:35:19 -06:00
projects	Initial commit: Workspace v1 with 3-layer architecture	2025-12-23 00:35:19 -06:00
shared	Initial commit: Workspace v1 with 3-layer architecture	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

README.md

Workspace v1 - Multi-Project Development Environment

Version: 2.0.0 Fecha: 2025-12-18

Descripcion

Workspace unificado para desarrollo de multiples proyectos con arquitectura de 3 capas, sistema de orquestacion SIMCO/NEXUS, y governance centralizado.

Arquitectura

workspace-v1/
|
+-- control-plane/           # Governance y orquestacion
|     +-- registries/        # Puertos, dominios, BDs
|     +-- orchestration/     # SIMCO, agentes, directivas
|     +-- devtools/          # Scripts, docker, configs
|
+-- projects/                # Repositorios de productos
|     +-- gamilit/           # Gamificacion educativa
|     +-- erp-suite/         # ERP multi-vertical
|     +-- trading-platform/  # Trading
|     +-- betting-analytics/ # Betting analytics
|
+-- shared/                  # Recursos compartidos
      +-- libs/              # Librerias
      +-- infra/             # Infraestructura
      +-- knowledge-base/    # Documentacion

Proyectos

Proyecto	Descripcion	Status
Gamilit	Plataforma de gamificacion educativa	Development
ERP Suite	ERP multi-vertical (construccion, mecanicas)	Development
Trading Platform	Plataforma de trading	Planned
Betting Analytics	Analisis de apuestas deportivas	Planned

Quick Start

1. Inicializar Workspace

# Crear redes Docker
cd control-plane
./devtools/docker/networks/create-networks.sh

# Iniciar Traefik
cd devtools/docker/traefik
docker-compose -f docker-compose.traefik.yml up -d

2. Levantar un Proyecto

# Ejemplo: Gamilit
cd projects/gamilit/docker
docker-compose up -d

3. Validar Configuracion

cd control-plane
./devtools/scripts/validation/validate-all.sh

URLs de Desarrollo

Infraestructura

Servicio	URL
Traefik Dashboard	http://traefik.localhost:8080

Gamilit

Servicio	URL
API	http://api.gamilit.localhost
Web	http://gamilit.localhost

ERP Suite

Servicio	URL
Core API	http://api.erp.localhost
Core Web	http://erp.localhost
Construccion API	http://api.construccion.erp.localhost
Mecanicas API	http://api.mecanicas.erp.localhost

Trading

Servicio	URL
API	http://api.trading.localhost
Web	http://trading.localhost

Betting

Servicio	URL
API	http://api.betting.localhost
Web	http://betting.localhost

Sistema SIMCO/NEXUS

Directivas Principales

SIMCO-INICIALIZACION: Protocolo de carga de contexto
SIMCO-CREAR: Creacion de componentes
SIMCO-VALIDAR: Validacion pre-commit
SIMCO-SERVICE-DESCRIPTOR: Uso de descriptores

Agentes

Agente	Rol
NEXUS-BACKEND	APIs y logica
NEXUS-FRONTEND	Interfaces UI
NEXUS-DATABASE	Schemas y datos
NEXUS-DEVOPS	Infraestructura
NEXUS-TECH-LEADER	Arquitectura

Principios Clave

Registry First: Todo puerto/dominio/BD debe estar registrado
Descriptor First: Crear service.descriptor.yml antes del codigo
Validacion Continua: Validar antes de commit
Aislamiento: Cada proyecto en su red Docker
Traefik Only: Solo puertos 80/443 publicos

Documentacion

Mantenido por: Tech-Leader Ultima actualizacion: 2025-12-18