mega-brain-ai 1.3.0

package/core/tasks/TASK-REGISTRY.md

@@ -0,0 +1,113 @@
+# TASK REGISTRY
+
+> **Versão:** 1.0.0
+> **Última Atualização:** 2026-02-26
+> **Padrão:** HO-TP-001 (Pedro/aios-core)
+
+---
+
+## Visão Geral
+
+Tasks são unidades ATÔMICAS de execução que o JARVIS orquestra via workflows.
+Diferente de Skills (user-facing), Tasks são MACHINE-ONLY.
+
+---
+
+## Categorias de Tasks
+
+| Categoria | Descrição | Tasks |
+|-----------|-----------|-------|
+| FOUNDATION | Sem dependências, base do sistema | detect-role, normalize-entities, validate-schema |
+| INTELLIGENCE | Dependem de Foundation | analyze-themes, detect-business-model, score-viability |
+| EXTRACTION | Dependem de Intelligence | extract-dna, extract-knowledge, generate-skill |
+| PIPELINE | Dependem de Extraction | process-batch, trigger-agent, trigger-dossier |
+| VALIDATION | Dependem de Pipeline | validate-cascade, verify-completeness |
+
+---
+
+## Task Index
+
+### FOUNDATION TASKS
+
+| Task ID | Name | Script | Status |
+|---------|------|--------|--------|
+| TSK-001 | detect-role | role_detector.py | ✅ ACTIVE |
+| TSK-002 | normalize-entities | entity_normalizer.py | ✅ ACTIVE |
+| TSK-003 | validate-schema | - | 📋 PLANNED |
+
+### INTELLIGENCE TASKS
+
+| Task ID | Name | Script | Status |
+|---------|------|--------|--------|
+| TSK-010 | analyze-themes | theme_analyzer.py | ✅ ACTIVE |
+| TSK-011 | detect-business-model | business_model_detector.py | ✅ ACTIVE |
+| TSK-012 | score-viability | viability_scorer.py | ✅ ACTIVE |
+
+### EXTRACTION TASKS
+
+| Task ID | Name | Script | Status |
+|---------|------|--------|--------|
+| TSK-020 | extract-dna | - | ✅ ACTIVE |
+| TSK-021 | extract-knowledge | - | ✅ ACTIVE |
+| TSK-022 | generate-skill | skill_generator.py | ✅ ACTIVE |
+
+### PIPELINE TASKS
+
+| Task ID | Name | Script | Status |
+|---------|------|--------|--------|
+| TSK-030 | process-batch | - | ✅ ACTIVE |
+| TSK-031 | trigger-agent | agent_trigger.py | ✅ ACTIVE |
+| TSK-032 | trigger-dossier | dossier_trigger.py | ✅ ACTIVE |
+
+### VALIDATION TASKS
+
+| Task ID | Name | Script | Status |
+|---------|------|--------|--------|
+| TSK-040 | validate-cascade | - | ✅ ACTIVE |
+| TSK-041 | verify-completeness | - | ✅ ACTIVE |
+
+---
+
+## Dependency Graph
+
+```
+FOUNDATION
+    │
+    ├── detect-role ─────────┐
+    ├── normalize-entities ──┼── INTELLIGENCE
+    └── validate-schema ─────┘       │
+                                     ├── analyze-themes ─────┐
+                                     ├── detect-business ────┼── EXTRACTION
+                                     └── score-viability ────┘       │
+                                                                     ├── extract-dna ────┐
+                                                                     ├── extract-knowledge┼── PIPELINE
+                                                                     └── generate-skill ─┘       │
+                                                                                                 ├── process-batch ────┐
+                                                                                                 ├── trigger-agent ────┼── VALIDATION
+                                                                                                 └── trigger-dossier ──┘       │
+                                                                                                                               ├── validate-cascade
+                                                                                                                               └── verify-completeness
+```
+
+---
+
+## Como Usar
+
+1. Tasks são invocadas por Workflows (`.yaml` em `core/workflows/`)
+2. Cada task segue anatomia HO-TP-001 (8 campos obrigatórios)
+3. Tasks podem invocar scripts de `core/intelligence/`
+4. O JARVIS é o único orquestrador que executa tasks
+
+---
+
+## Adicionando Nova Task
+
+1. Copiar template de `_templates/task-tmpl.md`
+2. Preencher os 8 campos obrigatórios
+3. Definir inputs/outputs/acceptance criteria
+4. Registrar neste arquivo (TASK-REGISTRY.md)
+5. Atualizar CHANGELOG.md
+
+---
+
+*Registry v1.0.0 - 2026-02-26*

package/core/tasks/_templates/task-tmpl.md

@@ -0,0 +1,105 @@
+# TASK TEMPLATE (HO-TP-001)
+
+> **Versão:** 1.0.0
+> **Padrão:** Pedro (aios-core/squad-creator)
+> **Uso:** Template para criar novos tasks atômicos
+
+---
+
+## TASK ANATOMY (8 Campos Obrigatórios)
+
+```yaml
+---
+task: [TASK-ID]
+execution_type: Agent | Human | Hybrid | Worker
+responsible: "@jarvis" | "@human" | "script"
+---
+```
+
+---
+
+# [Task Name]
+
+## Task Anatomy
+
+| Field | Value |
+|-------|-------|
+| task_name | [Verbo + Objeto] |
+| status | pending |
+| responsible_executor | [@jarvis/@human/script] |
+| execution_type | [Agent/Human/Hybrid/Worker] |
+| input | [Lista de inputs] |
+| output | [Lista de outputs] |
+| action_items | [N steps] |
+| acceptance_criteria | [Critérios de conclusão] |
+
+---
+
+## Inputs
+
+| Input | Type | Required | Description |
+|-------|------|----------|-------------|
+| input_1 | string/file/json | yes/no | [Descrição] |
+| input_2 | ... | ... | ... |
+
+---
+
+## Outputs
+
+| Output | Type | Location | Description |
+|--------|------|----------|-------------|
+| output_1 | file/json/update | [path] | [Descrição] |
+| output_2 | ... | ... | ... |
+
+---
+
+## Execution
+
+### Phase 1: [Nome]
+
+**Quality Gate:** [QG-ID]
+
+1. [Step 1]
+2. [Step 2]
+3. [Step 3]
+
+### Phase 2: [Nome] (se necessário)
+
+**Quality Gate:** [QG-ID]
+
+1. [Step 1]
+2. [Step 2]
+
+---
+
+## Acceptance Criteria
+
+- [ ] [Critério 1 - mensurável]
+- [ ] [Critério 2 - mensurável]
+- [ ] [Critério 3 - mensurável]
+
+---
+
+## Handoff
+
+| Next Task | Trigger | Data Passed |
+|-----------|---------|-------------|
+| [task-id] | [condition] | [what data] |
+
+---
+
+## Scripts de Suporte (opcional)
+
+| Script | Location | Invoked When |
+|--------|----------|--------------|
+| [script.py] | core/intelligence/ | [condition] |
+
+---
+
+## Notes
+
+[Notas adicionais, edge cases, considerações]
+
+---
+
+**Template Version:** 1.0.0 (HO-TP-001)

package/core/tasks/analyze-themes.md

@@ -0,0 +1,84 @@
+# analyze-themes
+
+```yaml
+---
+task: TSK-010
+execution_type: Worker
+responsible: "script"
+---
+```
+
+## Task Anatomy
+
+| Field | Value |
+|-------|-------|
+| task_name | Analyze Thematic Content |
+| status | active |
+| responsible_executor | theme_analyzer.py |
+| execution_type | Worker |
+| input | normalized content, entities |
+| output | theme classifications, topic clusters |
+| action_items | 4 steps |
+| acceptance_criteria | Themes identified with hierarchy |
+
+---
+
+## Inputs
+
+| Input | Type | Required | Description |
+|-------|------|----------|-------------|
+| content | string | yes | Normalized text |
+| entities | json | yes | Entity map from normalize-entities |
+| role | string | no | Primary role from detect-role |
+
+---
+
+## Outputs
+
+| Output | Type | Location | Description |
+|--------|------|----------|-------------|
+| themes | array | return value | Identified themes |
+| hierarchy | json | return value | Theme parent-child relationships |
+| topic_clusters | array | return value | Related topic groupings |
+
+---
+
+## Execution
+
+### Phase 1: Theme Identification
+
+**Quality Gate:** QG-THEME-001
+
+1. Load domain glossaries from `core/glossary/`
+2. Extract key topics from content
+3. Map topics to theme taxonomy
+4. Build theme hierarchy
+
+---
+
+## Acceptance Criteria
+
+- [ ] At least one theme identified
+- [ ] Themes mapped to known taxonomy
+- [ ] Hierarchy depth >= 1
+
+---
+
+## Handoff
+
+| Next Task | Trigger | Data Passed |
+|-----------|---------|-------------|
+| extract-dna | themes_identified | themes, hierarchy |
+| trigger-dossier | new_theme | theme details |
+
+---
+
+## Scripts de Suporte
+
+| Script | Location | Invoked When |
+|--------|----------|--------------|
+| theme_analyzer.py | core/intelligence/ | Always |
+
+---
+
+**Task Version:** 1.0.0

package/core/tasks/detect-role.md

@@ -0,0 +1,82 @@
+# detect-role
+
+```yaml
+---
+task: TSK-001
+execution_type: Worker
+responsible: "script"
+---
+```
+
+## Task Anatomy
+
+| Field | Value |
+|-------|-------|
+| task_name | Detect Role from Content |
+| status | active |
+| responsible_executor | role_detector.py |
+| execution_type | Worker |
+| input | text content, patterns config |
+| output | detected roles, confidence scores |
+| action_items | 3 steps |
+| acceptance_criteria | Role detected with >70% confidence |
+
+---
+
+## Inputs
+
+| Input | Type | Required | Description |
+|-------|------|----------|-------------|
+| content | string | yes | Text to analyze for roles |
+| patterns_path | string | no | Path to role patterns YAML |
+
+---
+
+## Outputs
+
+| Output | Type | Location | Description |
+|--------|------|----------|-------------|
+| roles | json | return value | Detected roles with scores |
+| primary_role | string | return value | Highest confidence role |
+
+---
+
+## Execution
+
+### Phase 1: Pattern Matching
+
+**Quality Gate:** QG-ROLE-001
+
+1. Load role patterns from `core/patterns/_ROLE_PATTERNS.yaml`
+2. Tokenize and normalize input text
+3. Match patterns against content
+4. Calculate confidence scores per role
+
+---
+
+## Acceptance Criteria
+
+- [ ] At least one role detected
+- [ ] Confidence score >= 0.70 for primary role
+- [ ] Valid JSON output format
+
+---
+
+## Handoff
+
+| Next Task | Trigger | Data Passed |
+|-----------|---------|-------------|
+| analyze-themes | role_detected | primary_role, content |
+| trigger-agent | high_confidence | roles array |
+
+---
+
+## Scripts de Suporte
+
+| Script | Location | Invoked When |
+|--------|----------|--------------|
+| role_detector.py | core/intelligence/ | Always |
+
+---
+
+**Task Version:** 1.0.0

package/core/tasks/extract-dna.md

@@ -0,0 +1,114 @@
+# extract-dna
+
+```yaml
+---
+task: TSK-020
+execution_type: Agent
+responsible: "@jarvis"
+---
+```
+
+## Task Anatomy
+
+| Field | Value |
+|-------|-------|
+| task_name | Extract Cognitive DNA |
+| status | active |
+| responsible_executor | @jarvis |
+| execution_type | Agent |
+| input | insights, themes, source content |
+| output | DNA-CONFIG.yaml (5 layers) |
+| action_items | 5 steps |
+| acceptance_criteria | All 5 DNA layers populated |
+
+---
+
+## Inputs
+
+| Input | Type | Required | Description |
+|-------|------|----------|-------------|
+| insights | json | yes | Extracted insights from content |
+| themes | array | yes | Theme classifications |
+| source_id | string | yes | Source identifier (e.g., "CG", "JM") |
+| chunks | array | yes | Content chunks for reference |
+
+---
+
+## Outputs
+
+| Output | Type | Location | Description |
+|--------|------|----------|-------------|
+| dna_config | yaml | agents/persons/{name}/DNA-CONFIG.yaml | 5-layer DNA structure |
+| layer_counts | json | return value | Count per layer |
+
+---
+
+## Execution
+
+### Phase 1: Philosophy Extraction (L1)
+
+**Quality Gate:** QG-DNA-001
+
+1. Identify core beliefs and worldview statements
+2. Extract value system indicators
+3. Map to PHILOSOPHIES layer
+
+### Phase 2: Mental Models (L2)
+
+**Quality Gate:** QG-DNA-002
+
+1. Identify thinking frameworks
+2. Extract decision-making patterns
+3. Map to MENTAL-MODELS layer
+
+### Phase 3: Heuristics (L3)
+
+**Quality Gate:** QG-DNA-003
+
+1. Extract practical rules
+2. Identify decision shortcuts
+3. Map to HEURISTICS layer
+
+### Phase 4: Frameworks (L4)
+
+**Quality Gate:** QG-DNA-004
+
+1. Identify structured methodologies
+2. Extract process definitions
+3. Map to FRAMEWORKS layer
+
+### Phase 5: Methodologies (L5)
+
+**Quality Gate:** QG-DNA-005
+
+1. Extract step-by-step implementations
+2. Identify tactical procedures
+3. Map to METHODOLOGIES layer
+
+---
+
+## Acceptance Criteria
+
+- [ ] All 5 DNA layers populated
+- [ ] Minimum 3 items per layer
+- [ ] Source citations for each item (^[chunk_id])
+- [ ] Valid YAML structure
+
+---
+
+## Handoff
+
+| Next Task | Trigger | Data Passed |
+|-----------|---------|-------------|
+| trigger-agent | dna_complete | DNA-CONFIG path |
+| validate-cascade | extraction_done | layer_counts |
+
+---
+
+## Protocol Reference
+
+See `core/templates/agents/dna-extraction.md` for detailed instructions.
+
+---
+
+**Task Version:** 1.0.0

package/core/tasks/normalize-entities.md

@@ -0,0 +1,82 @@
+# normalize-entities
+
+```yaml
+---
+task: TSK-002
+execution_type: Worker
+responsible: "script"
+---
+```
+
+## Task Anatomy
+
+| Field | Value |
+|-------|-------|
+| task_name | Normalize Named Entities |
+| status | active |
+| responsible_executor | entity_normalizer.py |
+| execution_type | Worker |
+| input | raw text, entity types |
+| output | normalized entities map |
+| action_items | 4 steps |
+| acceptance_criteria | Entities normalized with canonical forms |
+
+---
+
+## Inputs
+
+| Input | Type | Required | Description |
+|-------|------|----------|-------------|
+| content | string | yes | Text containing entities |
+| entity_types | array | no | Types to extract (PERSON, ORG, etc) |
+
+---
+
+## Outputs
+
+| Output | Type | Location | Description |
+|--------|------|----------|-------------|
+| entities | json | return value | Normalized entity map |
+| canonical_forms | json | return value | Canonical name mappings |
+
+---
+
+## Execution
+
+### Phase 1: Entity Extraction
+
+**Quality Gate:** QG-ENT-001
+
+1. Identify named entities in text
+2. Group variations (e.g., "Cole Gordon", "Cole", "Gordon")
+3. Select canonical form for each entity
+4. Build normalization map
+
+---
+
+## Acceptance Criteria
+
+- [ ] All entity variations grouped
+- [ ] Canonical form selected per entity
+- [ ] No duplicate entries in output
+
+---
+
+## Handoff
+
+| Next Task | Trigger | Data Passed |
+|-----------|---------|-------------|
+| analyze-themes | entities_normalized | canonical_forms |
+| extract-knowledge | complete | entities map |
+
+---
+
+## Scripts de Suporte
+
+| Script | Location | Invoked When |
+|--------|----------|--------------|
+| entity_normalizer.py | core/intelligence/ | Always |
+
+---
+
+**Task Version:** 1.0.0

package/core/tasks/process-batch.md

@@ -0,0 +1,111 @@
+# process-batch
+
+```yaml
+---
+task: TSK-030
+execution_type: Agent
+responsible: "@jarvis"
+---
+```
+
+## Task Anatomy
+
+| Field | Value |
+|-------|-------|
+| task_name | Process Content Batch |
+| status | active |
+| responsible_executor | @jarvis |
+| execution_type | Agent |
+| input | batch files, source config |
+| output | BATCH-XXX.md, insights, cascading |
+| action_items | 6 steps |
+| acceptance_criteria | Batch log complete with cascading |
+
+---
+
+## Inputs
+
+| Input | Type | Required | Description |
+|-------|------|----------|-------------|
+| batch_id | string | yes | Batch identifier (e.g., "BATCH-050") |
+| source_code | string | yes | Source code (e.g., "CG", "JM") |
+| files | array | yes | Files to process in batch |
+| template | string | no | Batch template version |
+
+---
+
+## Outputs
+
+| Output | Type | Location | Description |
+|--------|------|----------|-------------|
+| batch_log | md | logs/batches/BATCH-XXX.md | Full batch log |
+| insights | json | artifacts/insights/ | Extracted insights |
+| cascading | json | logs/cascading.jsonl | Cascading record |
+
+---
+
+## Execution
+
+### Phase 1: Batch Setup
+
+**Quality Gate:** QG-BATCH-001
+
+1. Verify all input files exist
+2. Load batch template from `core/templates/`
+3. Initialize batch log with header
+
+### Phase 2: Content Processing
+
+**Quality Gate:** QG-BATCH-002
+
+1. Execute chunking (PROMPT-1.1)
+2. Execute entity resolution (PROMPT-1.2)
+3. Execute insight extraction (PROMPT-2.1)
+4. Execute narrative synthesis (PROMPT-3.1)
+
+### Phase 3: Log Generation
+
+**Quality Gate:** QG-BATCH-003
+
+1. Generate full batch log (14 sections)
+2. Display log in chat (RULE #9)
+3. Save to dual locations (RULE #8)
+
+### Phase 4: Cascading
+
+**Quality Gate:** QG-BATCH-004
+
+1. Read "DESTINO DO CONHECIMENTO" section
+2. Execute cascading to all destinations
+3. Add "Cascateamento Executado" section
+4. Validate cascading integrity
+
+---
+
+## Acceptance Criteria
+
+- [ ] All 14 batch sections present
+- [ ] Log displayed in chat (not just saved)
+- [ ] Dual-location logging complete
+- [ ] Cascading validated (all destinations exist)
+- [ ] "Cascateamento Executado" section added
+
+---
+
+## Handoff
+
+| Next Task | Trigger | Data Passed |
+|-----------|---------|-------------|
+| validate-cascade | batch_complete | batch_id, destinations |
+| trigger-agent | new_insights | insights array |
+| trigger-dossier | theme_updated | theme details |
+
+---
+
+## Protocol Reference
+
+See `core/templates/pipeline/PIPELINE-JARVIS-v2.1.md` for detailed workflow.
+
+---
+
+**Task Version:** 1.0.0