sinapse-ai 5.0.8 → 6.0.1

package/docs/es/architecture/ADE-EPIC3-HANDOFF.md

@@ -1,327 +0,0 @@
-# ADE Epic 3 Handoff - Spec Pipeline
-
-> **De:** Quinn (@qa) - QA Agent
-> **Para:** Aria (@architect) - Solution Architect
-> **Fecha:** 2026-01-28
-> **Estado:** Epic 1+2 COMPLETO → Epic 3 DESBLOQUEADO
-
----
-
-## Resumen Ejecutivo
-
-Epic 1 (Worktree) y Epic 2 (Migration V3) estan **100% completos** y aprobados por el QA Gate. El Epic 3 (Spec Pipeline) esta **desbloqueado** para inicio inmediato.
-
-**Epic 3 es 100% Prompt Engineering** - @architect lidera las 6 stories.
-
----
-
-## Prerequisitos Validados ✅
-
-| Dependencia       | Estado            | Evidencia                                     |
-| ----------------- | ----------------- | --------------------------------------------- |
-| WorktreeManager   | ✅ Funcional      | `manager.list()` ejecuta sin errores          |
-| V3 Schemas        | ✅ Completo       | `agent-v3-schema.json`, `task-v3-schema.json` |
-| Todos Agents V3   | ✅ 12/12 migrados | `autoClaude:` section en todos                |
-| Migration Scripts | ✅ Listos         | `asset-inventory.js`, `path-analyzer.js`      |
-
----
-
-## Epic 3: Vision General del Spec Pipeline
-
-**Tipo:** 10% Codigo, **90% Prompt Engineering**
-
-El Spec Pipeline transforma requisitos vagos en especificaciones ejecutables a traves de 5 fases secuenciales:
-
-```
-User Request → Gather → Assess → Research → Write → Critique → Spec Ready
-```
-
----
-
-## Desglose de Stories
-
-| Story | Entregable                      | Tipo           | Agent      |
-| ----- | ------------------------------- | -------------- | ---------- |
-| 3.1   | `spec-gather-requirements.md`   | Task .md       | @architect |
-| 3.2   | `spec-assess-complexity.md`     | Task .md       | @architect |
-| 3.3   | `spec-research-dependencies.md` | Task .md + MCP | @architect |
-| 3.4   | `spec-write-spec.md`            | Task .md       | @architect |
-| 3.5   | `spec-critique.md`              | Task .md       | @architect |
-| 3.6   | `spec-pipeline.yaml`            | Workflow .yaml | @architect |
-
-**@dev necesario:** Ninguno
-**@architect lidera:** TODAS las stories
-
----
-
-## Story 3.1: Gather Requirements
-
-**Objetivo:** Recolectar y estructurar requisitos del usuario
-
-**Task:** `spec-gather-requirements.md`
-
-**Inputs:**
-
-- User request (texto o voz)
-- Contexto del proyecto (desde status.json)
-- Specs existentes (si se esta iterando)
-
-**Outputs:**
-
-- Documento de requisitos estructurado
-- Preguntas de clarificacion (si hay ambiguedad)
-- Definicion inicial del scope
-
-**Pattern:**
-
-```yaml
-autoClaude:
-  pipelinePhase: spec-gather
-  elicit: true
-  deterministic: false # Se necesita creatividad del LLM
-```
-
----
-
-## Story 3.2: Assess Complexity
-
-**Objetivo:** Evaluar complejidad y estimar esfuerzo
-
-**Task:** `spec-assess-complexity.md`
-
-**Inputs:**
-
-- Requisitos recolectados (de 3.1)
-- Analisis del codebase
-- Restricciones tecnicas
-
-**Outputs:**
-
-- Puntuacion de complejidad (simple/standard/complex)
-- Estimacion de esfuerzo
-- Factores de riesgo
-- Desglose sugerido (si es complex)
-
-**Pattern:**
-
-```yaml
-autoClaude:
-  pipelinePhase: spec-assess
-  complexity: standard
-  verification:
-    type: none # La evaluacion es consultiva
-```
-
----
-
-## Story 3.3: Research Dependencies
-
-**Objetivo:** Investigar bibliotecas, APIs y patrones necesarios
-
-**Task:** `spec-research-dependencies.md`
-
-**Herramientas Requeridas:**
-
-- EXA (busqueda web)
-- Context7 (documentacion de bibliotecas)
-- Busqueda en codebase
-
-**Inputs:**
-
-- Requisitos + Evaluacion
-- Preferencias del tech stack (desde technical-preferences.md)
-
-**Outputs:**
-
-- Bibliotecas recomendadas con justificacion
-- Enlaces a documentacion de APIs
-- Ejemplos de codigo
-- Notas de compatibilidad
-
-**Pattern:**
-
-```yaml
-autoClaude:
-  pipelinePhase: spec-research
-  tools:
-    - exa
-    - context7
-```
-
----
-
-## Story 3.4: Write Specification
-
-**Objetivo:** Producir especificacion ejecutable
-
-**Task:** `spec-write-spec.md`
-
-**Inputs:**
-
-- Todos los outputs anteriores (requisitos, evaluacion, investigacion)
-- Template de spec
-
-**Outputs:**
-
-- Documento de especificacion completo
-- Checklist de implementacion
-- Escenarios de prueba (Given-When-Then)
-- Criterios de aceptacion
-
-**Template:** Usar `spec-tmpl.yaml` existente o crear nuevo
-
-**Pattern:**
-
-```yaml
-autoClaude:
-  pipelinePhase: spec-write
-  deterministic: true # Mismos inputs = misma spec
-  composable: true
-```
-
----
-
-## Story 3.5: Critique Specification
-
-**Objetivo:** Validar y mejorar la spec antes de la ejecucion
-
-**Task:** `spec-critique.md`
-
-**Inputs:**
-
-- Especificacion escrita (de 3.4)
-- Checklist de calidad
-
-**Outputs:**
-
-- Reporte de critica
-- Sugerencias de mejora
-- Decision PASS/NEEDS_REVISION
-- Spec revisada (si se corrigio automaticamente)
-
-**Agent:** Capacidades de @qa (canCritique: true)
-
-**Pattern:**
-
-```yaml
-autoClaude:
-  pipelinePhase: spec-critique
-  selfCritique:
-    required: true
-    checklistRef: spec-quality-checklist.md
-```
-
----
-
-## Story 3.6: Pipeline Orchestration
-
-**Objetivo:** Orquestar las 5 fases en un workflow unico
-
-**Workflow:** `spec-pipeline.yaml`
-
-**Estructura:**
-
-```yaml
-workflow:
-  id: spec-pipeline
-  sequence:
-    - step: gather
-      task: spec-gather-requirements.md
-      agent: pm
-    - step: assess
-      task: spec-assess-complexity.md
-      agent: architect
-    - step: research
-      task: spec-research-dependencies.md
-      agent: analyst
-    - step: write
-      task: spec-write-spec.md
-      agent: pm
-    - step: critique
-      task: spec-critique.md
-      agent: qa
-      gate: true # Debe pasar para continuar
-```
-
----
-
-## Patrones Tecnicos
-
-### Task V3 Template
-
-```yaml
-autoClaude:
-  version: '3.0'
-  pipelinePhase: spec-{phase}
-  deterministic: boolean
-  elicit: boolean
-  composable: true
-
-  verification:
-    type: none|command|manual
-
-  contextRequirements:
-    projectContext: true
-    filesContext: false
-    implementationPlan: false
-    spec: false
-```
-
-### Pipeline Phase Enum
-
-```
-spec-gather    # @pm - recolectar requisitos
-spec-assess    # @architect - evaluar complejidad
-spec-research  # @analyst - investigar dependencias
-spec-write     # @pm - escribir especificacion
-spec-critique  # @qa - validar calidad
-```
-
----
-
-## Criterios de Exito
-
-- [ ] Las 5 spec tasks creadas con seccion autoClaude V3
-- [ ] Pipeline workflow orquesta todas las fases
-- [ ] Cada task tiene inputs/outputs claros
-- [ ] Critique task incluye quality gate
-- [ ] Prueba end-to-end: solicitud vaga → spec completa
-
----
-
-## Orden de Ejecucion Recomendado
-
-1. **3.1 + 3.2 + 3.3** - Crear las 3 tasks de analisis (pueden ser paralelas)
-2. **3.4** - Write spec task (depende de entender el flujo)
-3. **3.5** - Critique task (necesita spec para criticar)
-4. **3.6** - Pipeline workflow (integra todo)
-
----
-
-## Documentos Relacionados
-
-- PRD: `docs/prd/sinapse-autonomous-development-engine.md`
-- Auto-Claude Analysis: `docs/architecture/AUTO-CLAUDE-ANALYSIS-COMPLETE.md`
-- Epic Stories: `docs/stories/sinapse-ai-ade/epic-3-spec-pipeline.md`
-
----
-
-## QA Gate para Epic 3
-
-Despues de completar Epic 3, ejecutar:
-
-```
-@qa *gate epic-3-spec-pipeline
-```
-
-**Validacion:**
-
-- Todas las 5 tasks validan contra task-v3-schema.json
-- Pipeline workflow ejecuta sin errores
-- Prueba E2E: "Add login feature" → spec completa
-
----
-
-_Handoff preparado por Quinn (@qa) - Guardian de la Calidad_
-_Commit: 3fea6ca - feat(ade): complete Epic 1+2_
-_Fecha: 2026-01-28_

package/docs/es/architecture/ARCHITECTURE-INDEX.md

@@ -1,188 +0,0 @@
-# SINAPSE Architecture Documentation Index
-
-> 🌐 [EN](../../architecture/ARCHITECTURE-INDEX.md) | [PT](../../pt/architecture/ARCHITECTURE-INDEX.md) | **ES**
-
----
-
-**Version:** 2.1.1
-**Last Updated:** 2026-01-26
-**Status:** Official Reference
-
----
-
-## 📋 Document Navigation
-
-This index provides navigation to all architecture documentation for SINAPSE v4.
-
-> **Note:** Official framework documentation (coding-standards, tech-stack, source-tree) has been consolidated in `docs/framework/`. See [Framework README](../framework/README.md) for details.
-
----
-
-## 📁 Directory Structure
-
-```
-docs/architecture/
-├── ARCHITECTURE-INDEX.md     # This file
-├── high-level-architecture.md # System overview
-├── module-system.md          # 4-module architecture
-├── mcp-system-diagrams.md    # MCP architecture diagrams
-├── memory-layer.md           # Memory system architecture
-├── adr/                      # Architectural Decision Records
-└── [framework/]              # See docs/framework/ for standards
-```
-
----
-
-## 🎯 Quick Links by Topic
-
-### Core Architecture
-
-| Document | Description | Status |
-|----------|-------------|--------|
-| [High-Level Architecture](./high-level-architecture.md) | Overview of SINAPSE v4 architecture | ✅ Current |
-| [Module System](./module-system.md) | 4-module modular architecture | ✅ Current |
-| [Memory Layer](./memory-layer.md) | Memory system architecture | ✅ Current |
-
-### MCP & Integrations
-
-| Document | Description | Status |
-|----------|-------------|--------|
-| [MCP System Diagrams](./mcp-system-diagrams.md) | MCP architecture diagrams | ✅ Current |
-
-> **Note:** MCP management is handled via Docker MCP Toolkit (Story 5.11). Use `@devops` agent with `*setup-mcp-docker` for configuration.
-
-### Agent System
-
-| Document | Description | Status |
-|----------|-------------|--------|
-| [Agent Responsibility Matrix](./agent-responsibility-matrix.md) | Agent roles and responsibilities | ✅ Current |
-| [Agent Config Audit](./agent-config-audit.md) | Configuration audit | ✅ Current |
-
-### Tools & Utilities
-
-| Document | Description | Status |
-|----------|-------------|--------|
-| [Utility Integration Guide](./utility-integration-guide.md) | Utility integration | ✅ Current |
-| [CI/CD](./ci-cd.md) | CI/CD pipeline documentation | ✅ Current |
-
-### Health Check System (HCS)
-
-| Document | Description | Status |
-|----------|-------------|--------|
-| [HCS Check Specifications](./hcs-check-specifications.md) | Health check specs | ✅ Current |
-| [HCS Execution Modes](./hcs-execution-modes.md) | Execution modes | ✅ Current |
-| [HCS Self-Healing Spec](./hcs-self-healing-spec.md) | Self-healing specification | ✅ Current |
-
-### Squad System
-
-| Document | Description | Status |
-|----------|-------------|--------|
-| [Squad Improvement Analysis](./squad-improvement-analysis.md) | Improvement analysis | ✅ Current |
-| [Squad Improvement Approach](./squad-improvement-recommended-approach.md) | Recommended approach | ✅ Current |
-
-### Architectural Decision Records (ADR)
-
-| Document | Description | Status |
-|----------|-------------|--------|
-| [ADR COLLAB-1](./adr/ADR-COLLAB-1-current-state-audit.md) | Current state audit | ✅ Current |
-| [ADR COLLAB-2](./adr/ADR-COLLAB-2-proposed-configuration.md) | Proposed configuration | ✅ Current |
-| [ADR HCS](./adr/adr-hcs-health-check-system.md) | Health Check System | ✅ Current |
-| [ADR Isolated VM](./adr/adr-isolated-vm-decision.md) | Isolated VM decision | ✅ Current |
-
-### Reference Documents (Official in docs/framework/)
-
-| Document | Description | Status |
-|----------|-------------|--------|
-| [Tech Stack](../framework/tech-stack.md) | Technology decisions | ✅ Current |
-| [Coding Standards](../framework/coding-standards.md) | Code standards | ✅ Current |
-| [Source Tree](../framework/source-tree.md) | Project structure | ✅ Current |
-
-> **Note:** These are linked to `docs/framework/` which is the official location.
-
-### Research & Analysis
-
-| Document | Description | Status |
-|----------|-------------|--------|
-| [Contribution Workflow Research](./contribution-workflow-research.md) | Contribution analysis | ✅ Current |
-| [Introduction](./introduction.md) | Original intro (v2.0) | 📦 Legacy |
-
----
-
-## 🏗️ Architecture Overview Diagram
-
-```
-┌─────────────────────────────────────────────────────────────────────────┐
-│                     SINAPSE v4 ARCHITECTURE                              │
-│                                                                         │
-│   ┌─────────────────────────────────────────────────────────────────┐   │
-│   │                    MULTI-REPO STRUCTURE                          │   │
-│   │                                                                  │   │
-│   │   SinapseAI/sinapse-ai ◄───── Central Hub                       │   │
-│   │          │                    - Framework core                   │   │
-│   │          │                    - 11 base agents                   │   │
-│   │          │                    - Discussions hub                  │   │
-│   │          │                                                       │   │
-│   │   ┌──────┴───────┐                                               │   │
-│   │   │              │                                               │   │
-│   │   ▼              ▼                                               │   │
-│   │ sinapse-squads   mcp-ecosystem                                      │   │
-│   │ (MIT)         (Apache 2.0)                                       │   │
-│   └─────────────────────────────────────────────────────────────────┘   │
-│                                                                         │
-│   ┌─────────────────────────────────────────────────────────────────┐   │
-│   │                    MODULAR ARCHITECTURE                          │   │
-│   │                                                                  │   │
-│   │   .sinapse-ai/                                                    │   │
-│   │   ├── core/           ← Framework foundations                    │   │
-│   │   ├── development/    ← Agents, tasks, workflows                 │   │
-│   │   ├── product/        ← Templates, checklists                    │   │
-│   │   └── infrastructure/ ← Scripts, tools, integrations             │   │
-│   └─────────────────────────────────────────────────────────────────┘   │
-│                                                                         │
-│   ┌─────────────────────────────────────────────────────────────────┐   │
-│   │                    QUALITY GATES 3 LAYERS                        │   │
-│   │                                                                  │   │
-│   │   Layer 1: Pre-commit ──► Layer 2: PR ──► Layer 3: Human        │   │
-│   │   (Husky/lint-staged)    (CodeRabbit)    (Strategic Review)     │   │
-│   │        30%                  +50%              +20%               │   │
-│   │                        (80% automated)                           │   │
-│   └─────────────────────────────────────────────────────────────────┘   │
-│                                                                         │
-└─────────────────────────────────────────────────────────────────────────┘
-```
-
----
-
-## 📚 Reading Order for New Contributors
-
-### Quick Start (30 min)
-1. [High-Level Architecture](./high-level-architecture.md)
-2. [Module System](./module-system.md)
-3. [Framework README](../framework/README.md)
-
-### Deep Dive (2-3 hours)
-1. All Quick Start documents
-2. [Agent Responsibility Matrix](./agent-responsibility-matrix.md)
-3. [MCP System Diagrams](./mcp-system-diagrams.md)
-4. [Tech Stack](../framework/tech-stack.md)
-
-### Complete Mastery (1-2 days)
-1. All documents in this index
-2. ADR documents for architectural decisions
-3. HCS documentation for health check system
-
----
-
-## 📝 Document Status Legend
-
-| Status | Meaning |
-|--------|---------|
-| ✅ Current | Up-to-date with v4.2 |
-| ⚠️ Update needed | Needs terminology or content update |
-| 📦 Legacy | Historical reference |
-| 🆕 New | Recently created |
-
----
-
-**Last Updated:** 2026-01-26
-**Maintainer:** @architect (Aria)