sinapse-ai 5.0.8 → 6.0.1

package/docs/00-shared-activation-pipeline.md

@@ -481,7 +481,7 @@ Each agent has specific config requirements defined in `.sinapse-ai/data/agent-c
 
 | Agent | Config Sections | Files Loaded | Performance Target |
 |-------|----------------|--------------|-------------------|
-| `sinapse-master` | dataLocation, registry | sinapse-kb.md (lazy) | <30ms |
+| `sinapse-orqx` | dataLocation, registry | sinapse-kb.md (lazy) | <30ms |
 | `dev` | devLoadAlwaysFiles, devStoryLocation, dataLocation | coding-standards.md, tech-stack.md, source-tree.md, technical-preferences.md | <50ms |
 | `qa` | qaLocation, dataLocation, storyBacklog | technical-preferences.md, test-levels-framework.md, test-priorities-matrix.md | <50ms |
 | `devops` | dataLocation, cicdLocation | technical-preferences.md | <50ms |
@@ -622,7 +622,7 @@ Activation → loadUserProfile() → validateUserProfile() → resolveConfig(L5
 | 7 | `.sinapse-ai/core/config/migrate-config.js` | Config | Categorizes `user_profile` as USER_FIELD during migration | Same categorization |
 | 8 | `.sinapse-ai/core/config/schemas/user-config.schema.json` | Schema | `enum: ["bob", "advanced"]` validation | Same validation |
 | 9 | `.sinapse-ai/core/config/templates/user-config.yaml` | Template | Default template value: `bob` | N/A (template default is bob) |
-| 10 | `.sinapse-ai/development/agents/pm.md` | Agent | PM becomes sole orchestrator; bob mode session detection; orchestrates other agents internally | PM operates as normal PM with standard workflow |
+| 10 | `.sinapse-ai/development/agents/project-lead.md` | Agent | PM becomes sole orchestrator; bob mode session detection; orchestrates other agents internally | PM operates as normal PM with standard workflow |
 | 11 | `packages/installer/src/wizard/questions.js` | Install | Presents bob/advanced choice during setup | Same prompt |
 | 12 | `packages/installer/src/wizard/index.js` | Install | Writes `user_profile: bob`; idempotent on re-install | Writes `user_profile: advanced` |
 | 13 | `packages/installer/src/wizard/i18n.js` | Install | Translated "Assisted Mode" text (en/pt/es) | Translated "Advanced Mode" text |
@@ -634,24 +634,24 @@ Activation → loadUserProfile() → validateUserProfile() → resolveConfig(L5
 
 ### 13.3 Impact Matrix: Agent Command Visibility
 
-In `bob` mode, non-PM agents return **empty command lists** (redirect to @pm shown instead). PM agent shows all commands normally.
+In `bob` mode, non-PM agents return **empty command lists** (redirect to @project-lead shown instead). PM agent shows all commands normally.
 
 | Agent | `key` Commands Count | Bob Mode Result | Advanced Mode (`new` session) |
 |-------|---------------------|-----------------|-------------------------------|
 | `@pm` | 4 (`help`, `status`, `run`, `exit`) | All commands shown (PM is primary interface) | Full visibility commands |
-| `@dev` | 4 (`help`, `apply-qa-fixes`, `run-tests`, `exit`) | Empty (redirect to @pm) | Full visibility commands |
-| `@qa` | 0 (no visibility metadata) | Empty (redirect to @pm) | Fallback: first 12 commands |
-| `@architect` | 3 (`help`, `create-doc`, `exit`) | Empty (redirect to @pm) | Full visibility commands |
-| `@po` | 4 (`help`, `validate`, `gotcha`, `gotchas`) | Empty (redirect to @pm) | Full visibility commands |
-| `@sm` | 2 (`help`, `draft`) | Empty (redirect to @pm) | Full visibility commands |
-| `@analyst` | 2 (`help`, `exit`) | Empty (redirect to @pm) | Full visibility commands |
-| `@data-engineer` | 0 (no visibility metadata) | Empty (redirect to @pm) | Fallback: first 12 commands |
-| `@devops` | 0 (no visibility metadata) | Empty (redirect to @pm) | Fallback: first 12 commands |
-| `@ux-design-expert` | 0 (no visibility metadata) | Empty (redirect to @pm) | Fallback: first 12 commands |
-| `@squad-creator` | 7 (most have `key`) | Empty (redirect to @pm) | Full visibility commands |
-| `@sinapse-master` | 0 (uses string visibility) | Empty (redirect to @pm) | Fallback: first 12 commands |
-
-**Note:** Agents with 0 `key` commands (`qa`, `data-engineer`, `devops`, `ux-design-expert`, `sinapse-master`) lack `visibility` array metadata on their commands. In `advanced` mode `workflow` sessions, they fall back to showing first 12 commands. This is a known gap tracked for future improvement.
+| `@dev` | 4 (`help`, `apply-qa-fixes`, `run-tests`, `exit`) | Empty (redirect to @project-lead) | Full visibility commands |
+| `@qa` | 0 (no visibility metadata) | Empty (redirect to @project-lead) | Fallback: first 12 commands |
+| `@architect` | 3 (`help`, `create-doc`, `exit`) | Empty (redirect to @project-lead) | Full visibility commands |
+| `@po` | 4 (`help`, `validate`, `gotcha`, `gotchas`) | Empty (redirect to @project-lead) | Full visibility commands |
+| `@sm` | 2 (`help`, `draft`) | Empty (redirect to @project-lead) | Full visibility commands |
+| `@analyst` | 2 (`help`, `exit`) | Empty (redirect to @project-lead) | Full visibility commands |
+| `@data-engineer` | 0 (no visibility metadata) | Empty (redirect to @project-lead) | Fallback: first 12 commands |
+| `@devops` | 0 (no visibility metadata) | Empty (redirect to @project-lead) | Fallback: first 12 commands |
+| `@ux-design-expert` | 0 (no visibility metadata) | Empty (redirect to @project-lead) | Fallback: first 12 commands |
+| `@squad-creator` | 7 (most have `key`) | Empty (redirect to @project-lead) | Full visibility commands |
+| `@sinapse-orqx` | 0 (uses string visibility) | Empty (redirect to @project-lead) | Fallback: first 12 commands |
+
+**Note:** Agents with 0 `key` commands (`qa`, `data-engineer`, `devops`, `ux-design-expert`, `sinapse-orqx`) lack `visibility` array metadata on their commands. In `advanced` mode `workflow` sessions, they fall back to showing first 12 commands. This is a known gap tracked for future improvement.
 
 ### 13.4 Validation Pipeline Integration
 

package/docs/FEATURE_PROCESS.md

@@ -73,7 +73,7 @@ Release (credited in CHANGELOG.md)
 
 ### Who Can Add to Backlog?
 
-The Product Owner (@po) is the sole authority for adding items to the internal backlog.
+The Product Owner (@product-lead) is the sole authority for adding items to the internal backlog.
 This ensures proper prioritization and alignment with project goals.
 
 ### Contributor Credit

package/docs/ORQX-PLAN.md

@@ -0,0 +1,264 @@
+# SINAPSE Framework — Plano de Orquestracao: Refinamento Total
+
+**Data:** 2026-03-24
+**Autor:** Imperator (Sinapse Master)
+**Status:** Em Execucao
+**Versao:** 1.0
+
+---
+
+## Visao Estrategica
+
+Transformar o SINAPSE de um framework derivado em um **produto autoral, produtizado e pronto para distribuicao em massa**. Zero referencias externas, instalacao zero-error, documentacao didatica, e experiencia padronizada para TODOS os usuarios — de iniciantes a devs avancados.
+
+**Publico-alvo:**
+- Empreendedores que querem construir, empacotar e vender produtos com IA
+- Empresas que querem otimizar workflows e aumentar produtividade
+- Desenvolvedores que querem um framework completo de AI agents
+
+**Resultado esperado:** Qualquer pessoa roda `npx sinapse-ai install`, responde 3 perguntas, e tem um ambiente completo funcionando.
+
+---
+
+## Estado Atual (Pre-Refinamento)
+
+| Dimensao | Score | Notas |
+|----------|-------|-------|
+| AIOX Contamination | LIMPO | Fase 1 executada em 2026-03-24 |
+| Installation Flow | BOM | Wizard v4, 8 fases, multi-IDE |
+| Agent Greetings | PARCIAL | Core 100%, Orqx 65%, Squads 95% |
+| Documentation | EXCELENTE | Multi-lang, CI/CD, governance |
+| Cross-LLM Support | BOM | 6 IDEs suportadas |
+
+---
+
+## FASE 1: Purga AIOX [COMPLETA]
+
+**Status:** DONE (2026-03-24)
+
+Arquivos limpos:
+- [x] `.github/CODEOWNERS` — @caioimori -> @caioimori
+- [x] `CONTRIBUTING.md` — @caioimori -> @caioimori
+- [x] `CONTINUITY-PLAN.md` — Thiago Finch refs removidas
+- [x] `package-lock.json` (root) — entries aiox-install + aiox-pro-cli removidas
+- [x] `.sinapse-ai/scripts/diagnostics/health-dashboard/package-lock.json` — @aiox -> @sinapse
+- [x] Verificacao final: `grep -ri "aiox|pedrovaleriolopez|internal-reference"` = ZERO matches
+
+---
+
+## FASE 2: Padronizacao de Greetings + Filtragem de Comandos
+
+**Status:** EM ANDAMENTO (parcial)
+**Agentes:** @developer (implementacao) + @quality-gate (validacao)
+
+### Decisao Estrategica: Somente Orqx Sao Visiveis
+- **19 comandos visiveis:** 18 orqx + sinapse-orqx (renomeado de sinapse-orqx)
+- **~160 specialist agents:** Backend-only, chamados internamente pelos orqx
+- **Usuarios nunca chamam especialistas diretamente**
+
+### Rename: sinapse-orqx → sinapse-orqx
+- [x] Arquivo de comando renomeado (.claude/commands/SINAPSE/agents/sinapse-orqx.md)
+- [ ] Agent definition renomeado (~/.sinapse/sinapse/agents/)
+- [ ] Squad manifest atualizado
+- [ ] Referencias no codebase atualizadas
+
+### Objetivo
+Somente os 19 orqx devem ter greeting/activation instructions E aparecer como comandos.
+
+### Template Padrao (Referencia: Core Agents)
+```
+{icon} {Name} the {Archetype} ready to {verb}! [{Permission Badge}]
+
+**Role:** {role description}
+
+## Quick Commands
+- *help — Mostrar comandos disponiveis
+- *status — Ver estado atual
+- {specific commands...}
+
+— {Name}, {action phrase} {emoji}
+```
+
+### Trabalho Necessario
+1. Auditar os ~7 orqx agents que desviam do padrao (35%)
+2. Auditar os ~6 specialist agents sem greeting definido (5%)
+3. Corrigir cada agent definition file
+4. Validar que unified-activation-pipeline.js resolve corretamente
+5. Testar 1 agent por squad (17 testes minimos)
+
+### Acceptance Criteria
+- [ ] 100% dos orqx agents seguem template padrao
+- [ ] 100% dos specialist agents tem greeting_levels definido
+- [ ] Teste de ativacao passa para 1 agent de cada squad
+- [ ] greeting-builder.js gera output correto para todos os niveis
+
+---
+
+## FASE 3: Instalacao Zero-Error
+
+**Status:** PENDENTE
+**Agentes:** @architect (review) + @developer (fixes) + @quality-gate (testing)
+
+### Objetivo
+`npx sinapse-ai install` funciona 100% em qualquer maquina, qualquer SO, com qualquer LLM target.
+
+### Mudancas Estrategicas
+1. **Linguas:** Remover ES (Espanhol) e ZH (Chines) do wizard. Manter apenas PT + EN.
+2. **Modos de Instalacao:**
+   - "Rapido" (default) — Instala tudo automaticamente, ZERO decisoes tecnicas
+   - "Personalizado" — Escolhe tech stack, IDEs, configuracoes avancadas
+3. **Comando `sinapse`:** Ativar Claude Code com personalizacao SINAPSE completa
+4. **IDEs Primarias:** Claude Code + Codex (prioridade maxima). Demais como bonus.
+
+### Checklist de Validacao
+- [ ] Greenfield install funciona em Windows 11 limpo
+- [ ] Greenfield install funciona em macOS limpo
+- [ ] Greenfield install funciona em Ubuntu limpo
+- [ ] Brownfield upgrade funciona sem perda de dados
+- [ ] Wizard pergunta apenas lingua + modo (Rapido/Personalizado) no modo Rapido
+- [ ] Modo Personalizado oferece: IDE, tech preset, environment
+- [ ] `sinapse` no terminal abre Claude Code com framework carregado
+- [ ] `sinapse install` roda wizard
+- [ ] `sinapse doctor` roda diagnostico
+- [ ] Post-install validator reporta 0 erros
+- [ ] Hooks do Claude Code (.claude/hooks/*) instalados corretamente
+- [ ] IDE sync funciona para Claude Code e Codex
+
+### Analise: Modo Avancado (Bob vs Advanced)
+
+**Decisao:** MANTER ambos, renomear:
+- "Rapido" = antigo "bob" (recomendado, default, esconde complexidade)
+- "Personalizado" = antigo "advanced" (opt-in, mostra detalhes)
+
+**Justificativa:** O mass market NUNCA ve o modo personalizado — e opt-in. Remover cortaria power users que pagam mais e evangelizam o produto. Default = Rapido, que resolve 95% dos casos.
+
+---
+
+## FASE 4: Documentacao Didatica
+
+**Status:** PENDENTE
+**Agentes:** @analyst (review) + @developer (updates) + @ux-design-expert (UX writing)
+
+### Objetivo
+Qualquer pessoa que acessar o repositorio no GitHub entende imediatamente:
+1. O que e o SINAPSE
+2. Como instalar
+3. Como usar
+4. Onde encontrar ajuda
+
+### Trabalho Necessario
+1. **README.md** — Revisar para clareza e didatica:
+   - [ ] Quick start em 3 passos (install, activate, use)
+   - [ ] Demo GIF/screenshot do CLI em acao
+   - [ ] Badge de versao NPM atualizado
+   - [ ] Remover qualquer referencia a ES/ZH que nao existe mais
+2. **docs/installation/** — Guia por IDE:
+   - [ ] Claude Code (primario, detalhado)
+   - [ ] Codex (primario, detalhado)
+   - [ ] Gemini, Cursor, Copilot (secundarios, basico)
+3. **docs/getting-started.md** — Validar que esta atualizado com v5
+4. **docs/glossary.md** — Termos atuais (orqx, squad, agent, etc.)
+5. **docs/roadmap.md** — Atualizado com visao 2026
+6. **CONTRIBUTING.md** — Simplificar fluxo para novos contribuidores
+7. **Remover docs/zh/ e docs/es/** — Nao mais suportados
+
+### Acceptance Criteria
+- [ ] README tem quick start em 3 passos
+- [ ] Cada IDE tem guia proprio em docs/installation/
+- [ ] Zero paginas desatualizadas referenciando v3 ou v4
+- [ ] Glossario completo com 100% dos termos do framework
+- [ ] Nenhuma referencia a linguas removidas (ES, ZH)
+
+---
+
+## FASE 5: Code Audit Profundo
+
+**Status:** PENDENTE
+**Agentes:** @quality-gate (scan) + @developer (fixes) + @devops (release)
+
+### Objetivo
+Pente fino em cada arquivo do framework. Zero assinaturas escondidas, zero easter eggs, zero watermarks.
+
+### Scan Targets
+- [ ] Todos os .js/.ts/.cjs/.mjs — strings hardcoded, console.log, watermarks
+- [ ] Todos os .yaml/.yml — references externas em configs
+- [ ] Todos os .json — author/contributor fields
+- [ ] Todos os .md — URLs externas, nomes de pessoas
+- [ ] Todos os .sh/.bat — scripts com refs externas
+- [ ] `.github/workflows/` — actions com refs externas
+- [ ] `scripts/` — automacoes com refs externas
+- [ ] `packages/` — package.json internos (author, contributors, repository)
+- [ ] Git tags — verificar se alguma tag referencia AIOX
+- [ ] Git commit messages — verificar se tem refs problematicas (informativo, nao rewrite)
+
+### Pos-Audit
+- [ ] Regenerar package-lock.json limpo (`npm install`)
+- [ ] Rodar npm run lint
+- [ ] Rodar npm run typecheck
+- [ ] Rodar npm test
+- [ ] Validar install-manifest.yaml atualizado
+- [ ] @devops: commit final + tag de release
+
+### Acceptance Criteria
+- [ ] `grep -ri "aiox\|internal-reference\|pedrovaleriolopez\|alan.nicolas"` = ZERO matches
+- [ ] Nenhum package.json interno com author/contributor externo
+- [ ] Nenhuma URL apontando para repo externo nao-autorizado
+- [ ] Todos os quality gates passam (lint, typecheck, test, build)
+- [ ] Release tag criada
+
+---
+
+## TIMELINE DE EXECUCAO
+
+```
+Semana 1 (Atual):
+  Fase 1 [DONE] ████████████████████████████████████ 100%
+  Fase 2 [TODO] ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░   0%
+
+Semana 2:
+  Fase 2         ████████████████████░░░░░░░░░░░░░░░  55%
+  Fase 3 [start] ██████████░░░░░░░░░░░░░░░░░░░░░░░░░  25%
+
+Semana 3:
+  Fase 2         ████████████████████████████████████ 100%
+  Fase 3         ██████████████████████████░░░░░░░░░░  75%
+  Fase 4 [start] ██████████░░░░░░░░░░░░░░░░░░░░░░░░░  25%
+
+Semana 4:
+  Fase 3         ████████████████████████████████████ 100%
+  Fase 4         ████████████████████████████████████ 100%
+  Fase 5 [start] ████████████████████████████████████ 100%
+
+  >>> RELEASE: SINAPSE v6.0.0 — Refined Edition
+```
+
+---
+
+## DECISOES ESTRATEGICAS REGISTRADAS
+
+| # | Decisao | Justificativa |
+|---|---------|---------------|
+| 1 | @caioimori como unico maintainer no CODEOWNERS | Autoria completa |
+| 2 | BMad Method attribution mantida SOMENTE em LICENSE | Obrigacao MIT, invisivel ao usuario |
+| 3 | Linguas: PT + EN only | Foco, menos manutencao |
+| 4 | Modos: Rapido (default) + Personalizado | Mass market + power users |
+| 5 | Claude Code + Codex como IDEs primarias | Maior base de usuarios |
+| 6 | Zero refs externas em qualquer lugar visivel | Produto 100% autoral |
+| 7 | `sinapse` no terminal = Claude + SINAPSE framework | UX unificada |
+
+---
+
+## AGENTES ENVOLVIDOS
+
+| Fase | @architect | @developer | @quality-gate | @devops | @ux | @analyst |
+|------|-----------|------|-----|---------|-----|---------|
+| 1    |           | X    | X   |         |     |         |
+| 2    |           | X    | X   |         | X   |         |
+| 3    | X         | X    | X   |         |     |         |
+| 4    |           | X    |     |         | X   | X       |
+| 5    |           | X    | X   | X       |     |         |
+
+---
+
+*Documento vivo — atualizado conforme progresso das fases.*
+*Imperator — SINAPSE Framework Orchestration*

package/docs/core-architecture.md

@@ -69,11 +69,11 @@ The `sinapse-ai` directory contains all the definitions and resources that give
 
 ### 3.1. Agents (`sinapse-ai/agents/`)
 
-- **Purpose**: These are the foundational building blocks of the system. Each markdown file (e.g., `sinapse-master.md`, `pm.md`, `dev.md`) defines the persona, capabilities, and dependencies of a single AI agent.
+- **Purpose**: These are the foundational building blocks of the system. Each markdown file (e.g., `sinapse-orqx.md`, `pm.md`, `dev.md`) defines the persona, capabilities, and dependencies of a single AI agent.
 - **Structure**: An agent file contains a YAML header that specifies its role, persona, dependencies, and startup instructions. These dependencies are lists of tasks, templates, checklists, and data files that the agent is allowed to use.
 - **Startup Instructions**: Agents can include startup sequences that load project-specific documentation from the `docs/` folder, such as coding standards, API specifications, or project structure documents. This provides immediate project context upon activation.
 - **Document Integration**: Agents can reference and load documents from the project's `docs/` folder as part of tasks, workflows, or startup sequences. Users can also drag documents directly into chat interfaces to provide additional context.
-- **Example**: The `sinapse-master` agent lists its dependencies, which tells the build tool which files to include in a web bundle and informs the agent of its own capabilities.
+- **Example**: The `sinapse-orqx` agent lists its dependencies, which tells the build tool which files to include in a web bundle and informs the agent of its own capabilities.
 
 ### 3.2. Agent Teams (`sinapse-ai/agent-teams/`)
 

package/docs/en/sinapse-agent-flows/README.md

@@ -27,7 +27,7 @@ This folder contains detailed documentation for all SINAPSE agents, including:
 
 | Agent | Persona | Archetype | Document |
 |-------|---------|-----------|----------|
-| **@sinapse-master** | Orion | Orchestrator | [sinapse-master-system.md](./sinapse-master-system.md) |
+| **@sinapse-orqx** | Orion | Orchestrator | [sinapse-orqx-system.md](./sinapse-orqx-system.md) |
 | **@analyst** | Atlas | Researcher | [analyst-system.md](./analyst-system.md) |
 | **@architect** | Aria | Visionary | [architect-system.md](./architect-system.md) |
 | **@data-engineer** | Dara | Data Sage | [data-engineer-system.md](./data-engineer-system.md) |
@@ -98,7 +98,7 @@ Each agent document follows this standard structure:
 ```mermaid
 flowchart TB
     subgraph ORCHESTRATION["Orchestration"]
-        MASTER["@sinapse-master\n(Orion)"]
+        MASTER["@sinapse-orqx\n(Orion)"]
     end
 
     subgraph DISCOVERY["Discovery & Planning"]

package/docs/en/sinapse-agent-flows/dev-system.md

@@ -1,4 +1,4 @@
-# @dev (Dex) - System Documentation
+# @developer (Dex) - System Documentation
 
 > **EN** | [PT](../../sinapse-agent-flows/dev-system.md) | [ES](../../es/sinapse-agent-flows/dev-system.md)
 
@@ -23,4 +23,4 @@ For complete documentation including flowcharts, command mappings, integrations,
 
 ---
 
-*SINAPSE Agent Flows - @dev System v1.0*
+*SINAPSE Agent Flows - @developer System v1.0*

package/docs/en/sinapse-agent-flows/pm-system.md

@@ -1,4 +1,4 @@
-# @pm (Morgan) - System Documentation
+# @project-lead (Morgan) - System Documentation
 
 > **EN** | [PT](../../sinapse-agent-flows/pm-system.md) | [ES](../../es/sinapse-agent-flows/pm-system.md)
 
@@ -23,4 +23,4 @@ For complete documentation including flowcharts, command mappings, integrations,
 
 ---
 
-*SINAPSE Agent Flows - @pm System v1.0*
+*SINAPSE Agent Flows - @project-lead System v1.0*

package/docs/en/sinapse-agent-flows/qa-system.md

@@ -1,4 +1,4 @@
-# @qa (Quinn) - System Documentation
+# @quality-gate (Quinn) - System Documentation
 
 > **EN** | [PT](../../sinapse-agent-flows/qa-system.md) | [ES](../../es/sinapse-agent-flows/qa-system.md)
 
@@ -23,4 +23,4 @@ For complete documentation including flowcharts, command mappings, integrations,
 
 ---
 
-*SINAPSE Agent Flows - @qa System v1.0*
+*SINAPSE Agent Flows - @quality-gate System v1.0*

package/docs/en/sinapse-agent-flows/{sinapse-master-system.md → sinapse-orqx-system.md}

@@ -1,12 +1,12 @@
-# @sinapse-master (Orion) - System Documentation
+# @sinapse-orqx (Orion) - System Documentation
 
-> **EN** | [PT](../../sinapse-agent-flows/sinapse-master-system.md) | [ES](../../es/sinapse-agent-flows/sinapse-master-system.md)
+> **EN** | [PT](../../sinapse-agent-flows/sinapse-orqx-system.md) | [ES](../../es/sinapse-agent-flows/sinapse-orqx-system.md)
 
 ---
 
 ## Summary
 
-**@sinapse-master** (Orion) is the **Orchestrator** of the SINAPSE agent system. This agent is responsible for:
+**@sinapse-orqx** (Orion) is the **Orchestrator** of the SINAPSE agent system. This agent is responsible for:
 
 - Coordinating all other agents in the system
 - Managing the overall workflow and task delegation
@@ -19,8 +19,8 @@
 
 For complete documentation including flowcharts, command mappings, integrations, and troubleshooting, please refer to the Portuguese version:
 
-**[View Full Documentation (PT)](../../sinapse-agent-flows/sinapse-master-system.md)**
+**[View Full Documentation (PT)](../../sinapse-agent-flows/sinapse-orqx-system.md)**
 
 ---
 
-*SINAPSE Agent Flows - @sinapse-master System v1.0*
+*SINAPSE Agent Flows - @sinapse-orqx System v1.0*

package/docs/en/sinapse-agent-flows/sm-system.md

@@ -1,4 +1,4 @@
-# @sm (River) - System Documentation
+# @sprint-lead (River) - System Documentation
 
 > **EN** | [PT](../../sinapse-agent-flows/sm-system.md) | [ES](../../es/sinapse-agent-flows/sm-system.md)
 
@@ -23,4 +23,4 @@ For complete documentation including flowcharts, command mappings, integrations,
 
 ---
 
-*SINAPSE Agent Flows - @sm System v1.0*
+*SINAPSE Agent Flows - @sprint-lead System v1.0*

package/docs/framework/entity-layer-classification.md

@@ -21,7 +21,7 @@ Rules are evaluated in order. **First match wins.**
 | 2 | L1 | `bin/**` | sinapse.js, sinapse-init.js |
 | 3 | L1 | `.sinapse-ai/constitution.md` | (exact match) |
 | 4 | L3 | `.sinapse-ai/data/**` | entity-registry.yaml |
-| 5 | L3 | `**/MEMORY.md` | agents/dev/MEMORY.md |
+| 5 | L3 | `**/MEMORY.md` | agents/developer/MEMORY.md |
 | 6 | L3 | `.claude/**` | CLAUDE.md, settings.json |
 | 7 | L3 | `core-config.yaml`, `project-config.yaml` | (exact match) |
 | 8 | L3 | `*-config.yaml` (root only) | custom-config.yaml |
@@ -30,7 +30,7 @@ Rules are evaluated in order. **First match wins.**
 | 11 | L2 | `.sinapse-ai/product/**` | templates/, checklists/ |
 | 12 | L4 | Everything else | docs/, tests/, packages/ |
 
-**Important:** Rule 5 (MEMORY.md) must come before Rule 9 (development/) so that `agents/dev/MEMORY.md` classifies as L3 instead of L2.
+**Important:** Rule 5 (MEMORY.md) must come before Rule 9 (development/) so that `agents/developer/MEMORY.md` classifies as L3 instead of L2.
 
 ## SCAN_CONFIG to Layer Mapping
 

package/docs/framework/source-tree.md

@@ -123,14 +123,14 @@ sinapse-ai/                             # Root project
 │   └── utils/                         # Core utilities
 │
 ├── data/                              # Shared Data
-│   ├── sinapse-kb.md                     # SINAPSE knowledge base (@sinapse-master, lazy-loaded)
+│   ├── sinapse-kb.md                     # SINAPSE knowledge base (@sinapse-orqx, lazy-loaded)
 │   ├── agent-config-requirements.yaml # Per-agent config loading rules (@architect, updated on agent changes)
 │   ├── technical-preferences.md       # User/team technical preferences (@architect, updated on preference changes)
-│   └── workflow-patterns.yaml         # Workflow detection patterns (@sm, updated on workflow changes)
+│   └── workflow-patterns.yaml         # Workflow detection patterns (@sprint-lead, updated on workflow changes)
 │
 ├── development/                       # Development Assets
 │   ├── agents/                        # Agent definitions (11 core agents)
-│   │   ├── sinapse-master.md             # Master orchestrator
+│   │   ├── sinapse-orqx.md             # Master orchestrator
 │   │   ├── dev.md                     # Developer agent
 │   │   ├── qa.md                      # QA engineer agent
 │   │   ├── architect.md               # System architect agent
@@ -182,10 +182,10 @@ sinapse-ai/                             # Root project
 │   │   └── change-checklist.md        # Change management
 │   ├── data/                          # PM-specific data files
 │   │   ├── brainstorming-techniques.md    # Brainstorming methods (@analyst, reference doc, rarely updated)
-│   │   ├── elicitation-methods.md         # Elicitation techniques (@po, reference doc, rarely updated)
-│   │   ├── mode-selection-best-practices.md # Mode selection guide (@sm, updated on workflow changes)
-│   │   ├── test-levels-framework.md       # Test level definitions (@qa, updated when test strategy changes)
-│   │   └── test-priorities-matrix.md      # Test priority rules (@qa, updated when priorities shift)
+│   │   ├── elicitation-methods.md         # Elicitation techniques (@product-lead, reference doc, rarely updated)
+│   │   ├── mode-selection-best-practices.md # Mode selection guide (@sprint-lead, updated on workflow changes)
+│   │   ├── test-levels-framework.md       # Test level definitions (@quality-gate, updated when test strategy changes)
+│   │   └── test-priorities-matrix.md      # Test priority rules (@quality-gate, updated when priorities shift)
 │   └── templates/                     # Document templates
 │       ├── engine/                    # Template engine
 │       ├── ide-rules/                 # IDE rule templates
@@ -267,28 +267,28 @@ All data files used by agents during activation must have documented ownership,
 
 | File | Owner | Fill Rule | Update Trigger | Used By |
 |------|-------|-----------|----------------|---------|
-| `coding-standards.md` | @dev | Updated when coding standards change | `*update-standards` task or manual edit | @dev, @pm, @ux-design-expert, @sm |
-| `tech-stack.md` | @architect | Updated on tech stack decisions | `*create-doc architecture` or manual edit | @dev, @pm, @ux-design-expert, @analyst |
-| `source-tree.md` | @architect | Updated when structure changes | `*update-source-tree` task | @dev, @analyst |
+| `coding-standards.md` | @developer | Updated when coding standards change | `*update-standards` task or manual edit | @developer, @project-lead, @ux-design-expert, @sprint-lead |
+| `tech-stack.md` | @architect | Updated on tech stack decisions | `*create-doc architecture` or manual edit | @developer, @project-lead, @ux-design-expert, @analyst |
+| `source-tree.md` | @architect | Updated when structure changes | `*update-source-tree` task | @developer, @analyst |
 
 ### Shared Data Files (.sinapse-ai/data/)
 
 | File | Owner | Fill Rule | Update Trigger | Used By |
 |------|-------|-----------|----------------|---------|
-| `sinapse-kb.md` | @sinapse-master | Updated on major framework changes | Manual edit | @sinapse-master (lazy) |
+| `sinapse-kb.md` | @sinapse-orqx | Updated on major framework changes | Manual edit | @sinapse-orqx (lazy) |
 | `agent-config-requirements.yaml` | @architect | Updated when agent config needs change | Story-driven | AgentConfigLoader |
-| `technical-preferences.md` | @architect | Updated on preference changes | Manual edit or `*add-tech-doc` | @dev, @qa, @devops, @architect, @data-engineer |
-| `workflow-patterns.yaml` | @sm | Updated on workflow changes | Manual edit | @sm, WorkflowNavigator |
+| `technical-preferences.md` | @architect | Updated on preference changes | Manual edit or `*add-tech-doc` | @developer, @quality-gate, @devops, @architect, @data-engineer |
+| `workflow-patterns.yaml` | @sprint-lead | Updated on workflow changes | Manual edit | @sprint-lead, WorkflowNavigator |
 
 ### Product Data Files (.sinapse-ai/product/data/)
 
 | File | Owner | Fill Rule | Update Trigger | Used By |
 |------|-------|-----------|----------------|---------|
 | `brainstorming-techniques.md` | @analyst | Reference doc, rarely updated | Manual edit | @analyst |
-| `elicitation-methods.md` | @po | Reference doc, rarely updated | Manual edit | @po |
-| `mode-selection-best-practices.md` | @sm | Updated on workflow changes | Manual edit | @sm |
-| `test-levels-framework.md` | @qa | Updated when test strategy changes | `*update-test-strategy` or manual edit | @qa |
-| `test-priorities-matrix.md` | @qa | Updated when priorities shift | `*update-test-strategy` or manual edit | @qa |
+| `elicitation-methods.md` | @product-lead | Reference doc, rarely updated | Manual edit | @product-lead |
+| `mode-selection-best-practices.md` | @sprint-lead | Updated on workflow changes | Manual edit | @sprint-lead |
+| `test-levels-framework.md` | @quality-gate | Updated when test strategy changes | `*update-test-strategy` or manual edit | @quality-gate |
+| `test-priorities-matrix.md` | @quality-gate | Updated when priorities shift | `*update-test-strategy` or manual edit | @quality-gate |
 
 ---
 

package/docs/getting-started.md

@@ -133,10 +133,10 @@ SINAPSE agents are activated through your IDE. Once activated, agents respond to
 *exit                    # Exit agent mode
 
 # Agent-specific examples
-@dev *help               # Developer agent commands
-@qa *review STORY-42     # QA agent reviews a story
-@pm *create-epic         # PM agent creates an epic
-@sm *draft               # Scrum Master drafts a story
+@developer *help               # Developer agent commands
+@quality-gate *review STORY-42     # QA agent reviews a story
+@project-lead *create-epic         # PM agent creates an epic
+@sprint-lead *draft               # Scrum Master drafts a story
 ```
 
 ### Available Agents
@@ -157,13 +157,13 @@ SINAPSE agents are activated through your IDE. Once activated, agents respond to
 ### Typical Workflow
 
 ```
-1. @pm creates a PRD          → *create-epic
-2. @sm drafts stories          → *draft
-3. @po validates stories       → *validate-story-draft
-4. @dev implements             → (works from story file)
-5. @qa reviews                 → *review STORY-ID
+1. @project-lead creates a PRD          → *create-epic
+2. @sprint-lead drafts stories          → *draft
+3. @product-lead validates stories       → *validate-story-draft
+4. @developer implements             → (works from story file)
+5. @quality-gate reviews                 → *review STORY-ID
 6. @devops pushes              → *push (only agent with push authority)
-7. @po closes story            → *close-story STORY-ID
+7. @product-lead closes story            → *close-story STORY-ID
 ```
 
 ## IDE Compatibility
@@ -214,10 +214,10 @@ When you first activate an SINAPSE agent in an existing project:
 
 | Your Situation | Recommended Workflow |
 |----------------|---------------------|
-| Add major feature to existing project | `@pm → *create-doc brownfield-prd` |
+| Add major feature to existing project | `@project-lead → *create-doc brownfield-prd` |
 | Audit legacy codebase | `brownfield-discovery.yaml` (full workflow) |
-| Quick enhancement | `@pm → *brownfield-create-epic` |
-| Single bug fix | `@pm → *brownfield-create-story` |
+| Quick enhancement | `@project-lead → *brownfield-create-epic` |
+| Single bug fix | `@project-lead → *brownfield-create-story` |
 
 ### Safety Guarantees