sinapse-ai 9.2.0 → 9.3.0

package/.sinapse-ai/product/templates/sinapse-ai-config.yaml

@@ -1,106 +0,0 @@
-# SINAPSE AI Provider Configuration
-#
-# Configure AI providers (Claude Code, Gemini CLI) for SINAPSE operations.
-# This file controls which provider is used for different task types.
-#
-# @see Epic GEMINI-INT - Story 2: AI Provider Factory Pattern
-
-# Provider Configuration
-ai_providers:
-  # Primary provider - used by default
-  primary: claude        # Options: claude, gemini
-
-  # Fallback provider - used when primary fails
-  fallback: gemini       # Options: claude, gemini, null (no fallback)
-
-  # Task-based routing
-  # Route specific task types to preferred providers
-  routing:
-    # Simple tasks - use cheaper/faster provider
-    simple_tasks: gemini       # Code formatting, simple refactors
-
-    # Complex tasks - use more capable provider
-    complex_tasks: claude      # Architecture, security reviews
-
-    # Documentation - high volume, speed matters
-    documentation: gemini
-
-    # Code generation - balance of speed and quality
-    code_generation: gemini
-
-    # Code review - quality matters
-    code_review: claude
-
-    # Testing - straightforward tasks
-    testing: gemini
-
-    # Security - critical thinking required
-    security: claude
-
-# Claude Code Configuration
-claude:
-  # Model to use
-  model: claude-3-5-sonnet    # Options: claude-3-5-sonnet, claude-3-opus, etc.
-
-  # Execution timeout (ms)
-  timeout: 300000             # 5 minutes
-
-  # Maximum retry attempts
-  maxRetries: 3
-
-  # Skip permission prompts (use with caution)
-  dangerouslySkipPermissions: false
-
-# Gemini CLI Configuration
-gemini:
-  # Model to use
-  model: gemini-2.0-flash     # Options: gemini-2.0-flash, gemini-2.0-pro
-
-  # Execution timeout (ms)
-  timeout: 300000             # 5 minutes
-
-  # Maximum retry attempts
-  maxRetries: 3
-
-  # Enable preview features (required for Gemini 3)
-  previewFeatures: true
-
-  # Use JSON output format by default
-  jsonOutput: false
-
-# Model Switching (Story 16)
-# Automatic selection between Flash and Pro based on task complexity
-model_switching:
-  enabled: false              # Enable when Story 16 is complete
-  default_model: gemini-2.0-flash
-  complexity_threshold:
-    simple: 0.3               # < 0.3 = Flash
-    medium: 0.7               # 0.3-0.7 = Flash
-    complex: 1.0              # > 0.7 = Pro
-  quality_fallback:
-    enabled: true
-    min_score: 0.6            # If quality < 0.6, retry with Pro
-
-# Parallel Execution (Story 17)
-# Run Claude + Gemini simultaneously for better quality
-parallel_execution:
-  enabled: false              # Enable when Story 17 is complete
-  default_mode: fallback      # Options: race, consensus, best-of, merge, fallback
-
-  # Task-specific modes
-  task_modes:
-    architecture: consensus   # Both must agree on architecture
-    security: consensus       # Critical - need agreement
-    code_generation: best-of  # Pick best code
-    documentation: race       # Speed matters
-    refactoring: merge        # Combine insights
-
-  # Cost control
-  cost_control:
-    max_parallel_cost: 1.00   # Max cost for parallel run (USD)
-    fallback_on_budget: true  # Disable parallel if over budget
-
-  # Quality thresholds
-  quality_thresholds:
-    consensus_similarity: 0.85
-    merge_min_quality: 0.7

package/docs/changelog.md

@@ -1,184 +0,0 @@
-# Changelog
-
-> 🌐 **EN** | [PT](./pt/CHANGELOG.md) | [ES](./es/CHANGELOG.md)
-
----
-
-All notable changes to SINAPSE will be documented in this file.
-
-The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
-and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
-
----
-
-## [2.2.0] - 2026-01-29
-
-### Added
-
-- **🤖 SINAPSE Autonomous Development Engine (ADE)**: Complete autonomous development system with 7 Epics:
-  - **Epic 1 - Worktree Manager**: Git worktree isolation for parallel story development
-  - **Epic 2 - Migration V2→V3**: autoClaude V3 format with capability flags
-  - **Epic 3 - Spec Pipeline**: Transform requirements into executable specifications
-  - **Epic 4 - Execution Engine**: 13-step subtask execution with mandatory self-critique
-  - **Epic 5 - Recovery System**: Automatic failure recovery with attempt tracking and rollback
-  - **Epic 6 - QA Evolution**: 10-phase structured review process
-  - **Epic 7 - Memory Layer**: Persistent memory for patterns, insights, and gotchas
-
-- **New Agent Commands**:
-  - `@devops`: `*create-worktree`, `*list-worktrees`, `*merge-worktree`, `*cleanup-worktrees`, `*inventory-assets`, `*analyze-paths`, `*migrate-agent`, `*migrate-batch`
-  - `@pm`: `*gather-requirements`, `*write-spec`
-  - `@architect`: `*assess-complexity`, `*create-plan`, `*create-context`, `*map-codebase`
-  - `@analyst`: `*research-deps`, `*extract-patterns`
-  - `@qa`: `*critique-spec`, `*review-build`, `*request-fix`, `*verify-fix`
-  - `@dev`: `*execute-subtask`, `*track-attempt`, `*rollback`, `*capture-insights`, `*list-gotchas`, `*apply-qa-fix`
-
-- **New Scripts**:
-  - `worktree-manager.js`, `story-worktree-hooks.js`, `project-status-loader.js`
-  - `asset-inventory.js`, `path-analyzer.js`, `migrate-agent.js`
-  - `subtask-verifier.js`, `plan-tracker.js`
-  - `recovery-tracker.js`, `approach-manager.js`, `rollback-manager.js`, `stuck-detector.js`
-  - `qa-loop-orchestrator.js`, `qa-report-generator.js`
-  - `codebase-mapper.js`, `pattern-extractor.js`, `gotchas-documenter.js`
-
-- **New Workflows**:
-  - `auto-worktree.yaml` - Automatic worktree creation for stories
-  - `spec-pipeline.yaml` - 5-phase specification pipeline
-  - `qa-loop.yaml` - QA review and fix loop
-
-- **New Tasks** (15+ new tasks for ADE):
-  - Spec Pipeline: `spec-gather-requirements.md`, `spec-assess-complexity.md`, `spec-research-dependencies.md`, `spec-write-spec.md`, `spec-critique.md`
-  - Execution: `plan-create-implementation.md`, `plan-create-context.md`, `plan-execute-subtask.md`
-  - QA: `qa-review-build.md`, `qa-fix-issues.md`, `qa-structured-review.md`
-  - Memory: `capture-session-insights.md`
-  - Worktree: `worktree-create.md`, `worktree-list.md`, `worktree-merge.md`
-
-- **JSON Schemas**:
-  - `agent-v3-schema.json` - V3 agent definition validation
-  - `task-v3-schema.json` - V3 task definition validation
-
-- **Templates**:
-  - `spec-tmpl.md` - Specification document template
-  - `qa-report-tmpl.yaml` - QA report template
-
-- **Checklists**:
-  - `self-critique-checklist.md` - Mandatory self-critique for developers
-
-- **Documentation**:
-  - [ADE Complete Guide](guides/ade-guide.md) - Full tutorial
-  - [Epic 1-7 Handoffs](architecture/) - Technical handoffs (ADE-EPIC-1 through ADE-EPIC-7)
-  - [Agent Changes](architecture/ADE-AGENT-CHANGES.md) - All agent modifications with capability matrix
-
-### Changed
-
-- **Agent Format**: All 12 agents migrated to autoClaude V3 format with capability flags
-- **Agent Sync**: All agents now synced between `.sinapse-ai/development/agents/` and `.claude/commands/SINAPSE/agents/`
-
-### Fixed
-
-- Agent command registration for all ADE Epics
-- Schema validation for V3 format
-
----
-
-## [2.1.0] - 2025-01-24
-
-### Added
-
-- **Interactive Installation Wizard**: Step-by-step guided setup with component selection
-- **Multi-IDE Support**: Added support for 4 IDEs (Claude Code, Cursor, Gemini CLI, GitHub Copilot)
-- **Squads System**: Modular add-ons including HybridOps for ClickUp integration
-- **Cross-Platform Testing**: Full test coverage for Windows, macOS, and Linux
-- **Error Handling & Rollback**: Automatic rollback on installation failure with recovery suggestions
-- **Agent Improvements**:
-  - Decision logging in yolo mode for `dev` agent
-  - Backlog management commands for `qa` agent
-  - CodeRabbit integration for automated code review
-  - Contextual greetings with project status
-- **Documentation Suite**:
-  - Troubleshooting Guide with 23 documented issues
-  - FAQ with 22 Q&As
-  - Migration Guide v2.0 to v4.0.4
-
-### Changed
-
-- **Directory Structure**: Renamed `.legacy-core/` to `.sinapse-ai/`
-- **Configuration Format**: Enhanced `core-config.yaml` with new sections for git, projectStatus, and sharding options
-- **Agent Format**: Updated agent YAML schema with persona_profile, commands visibility, and whenToUse fields
-- **IDE Configuration**: Claude Code agents moved to `.claude/commands/SINAPSE/agents/`
-- **File Locations**:
-  - `docs/architecture/coding-standards.md` → `docs/framework/coding-standards.md`
-  - `docs/architecture/tech-stack.md` → `docs/framework/tech-stack.md`
-  - `.sinapse-ai/utils/` → `.sinapse-ai/scripts/`
-
-### Fixed
-
-- Installation failures on Windows with long paths
-- PowerShell execution policy blocking scripts
-- npm permission issues on Linux/macOS
-- IDE configuration not applying after installation
-
-### Deprecated
-
-- Manual installation process (use `npx sinapse-ai install` instead)
-- `.legacy-core/` directory name (automatically migrated)
-
-### Security
-
-- Added validation for installation directory to prevent system directory modifications
-- Improved handling of environment variables and API keys
-
----
-
-## [2.0.0] - 2024-12-01
-
-### Added
-
-- Initial public release of SINAPSE
-- 11 specialized AI agents (dev, qa, architect, pm, po, sm, analyst, ux-expert, data-engineer, devops, db-sage)
-- Task workflow system with 60+ pre-built tasks
-- Template system with 20+ document templates
-- Story-driven development methodology
-- Basic Claude Code integration
-
-### Known Issues
-
-- Manual installation required (2-4 hours)
-- Limited cross-platform support
-- No interactive wizard
-
----
-
-## [1.0.0] - 2024-10-15
-
-### Added
-
-- Initial internal release
-- Core agent framework
-- Basic task execution
-
----
-
-## Migration Notes
-
-### Upgrading from 2.0.x to 2.1.x
-
-**Quick upgrade:**
-
-```bash
-npx sinapse-ai install --force-upgrade
-```
-
-**Key changes:**
-
-1. Directory renamed: `.legacy-core/` → `.sinapse-ai/`
-2. Update `core-config.yaml` with new fields
-3. Re-run IDE configuration
-
----
-
-## Links
-
-- [Troubleshooting](./installation/troubleshooting.md)
-- [FAQ](./installation/faq.md)
-- [GitHub Repository](https://github.com/SinapseAI/sinapse-ai)
-- [Issue Tracker](https://github.com/SinapseAI/sinapse-ai/issues)

package/docs/community.md

@@ -1,227 +0,0 @@
-# SINAPSE Community
-
-> 🇧🇷 [Versão em Português](COMMUNITY-PT.md)
-
-Welcome to the SINAPSE community!
-
-We're building the future of AI-orchestrated development together.
-
-## Our Values
-
-- **Collaboration over competition** - We grow together
-- **Inclusion** - Everyone is welcome regardless of experience level
-- **Transparency** - Open discussions, open decisions
-- **Quality** - We care about doing things right
-
-## Getting Started
-
-### First Steps
-
-1. Star the repository
-2. Read the [README](README.md)
-3. Set up your [development environment](CONTRIBUTING.md#getting-started)
-4. Introduce yourself in [Discussions](https://github.com/SinapseAI/sinapse-ai/discussions)
-
-### Find Your First Contribution
-
-- Look for issues labeled [`good-first-issue`](https://github.com/SinapseAI/sinapse-ai/labels/good-first-issue)
-- Check [`help-wanted`](https://github.com/SinapseAI/sinapse-ai/labels/help-wanted) for more complex tasks
-- Browse [open Discussions](https://github.com/SinapseAI/sinapse-ai/discussions) to help others
-
-## Communication Channels
-
-### GitHub Discussions (Primary)
-
-Our main communication hub for all SINAPSE repositories:
-
-- **Announcements** - Project updates from maintainers
-- **General** - General discussions about SINAPSE
-- **Ideas** - Propose new features and improvements
-- **Q&A** - Get help with technical questions
-- **Show and Tell** - Share your projects using SINAPSE
-- **Troubleshooting** - Get help with problems
-- **Squads** - Discussions about SINAPSE Squads (modular agent teams)
-- **MCP Ecosystem** - Discussions about MCP tools and integrations
-
-[Join the Discussion](https://github.com/SinapseAI/sinapse-ai/discussions)
-
-### Issue Tracker
-
-For bug reports and feature requests:
-
-- [sinapse-ai Issues](https://github.com/SinapseAI/sinapse-ai/issues) - Core framework
-- [sinapse-squads Issues](https://github.com/SinapseAI/sinapse-squads/issues) - SINAPSE Squads
-- [mcp-ecosystem Issues](https://github.com/SinapseAI/mcp-ecosystem/issues) - MCP tools
-
-## How to Contribute
-
-### Code Contributions
-
-1. Fork the repository
-2. Create a feature branch (`git checkout -b feature/amazing-feature`)
-3. Make your changes
-4. Run tests (`npm test`)
-5. Submit a Pull Request
-
-See [CONTRIBUTING.md](CONTRIBUTING.md) for detailed guidelines.
-
-### Non-Code Contributions
-
-We value all types of contributions:
-
-- **Documentation** - Fix typos, improve explanations
-- **Translation** - Help translate docs
-- **Bug Reports** - Report issues you find
-- **Ideas** - Share your thoughts on improvements
-- **Design** - UI/UX suggestions
-- **Advocacy** - Blog posts, talks, tutorials
-
-### Squads
-
-Create and share your own Squads (modular AI agent teams)!
-
-Squads are specialized teams of AI agents that work together on specific domains:
-- **ETL Squad** - Data collection and transformation
-- **Creator Squad** - Content generation
-
-See [docs/Squads.md](docs/Squads.md) for details on creating your own Squad.
-
-## Community Roles
-
-### Contributors
-
-Anyone who has contributed to SINAPSE in any way.
-- Listed in our [Contributors page](https://github.com/SinapseAI/sinapse-ai/graphs/contributors)
-- Mentioned in release notes for significant contributions
-
-### Maintainers
-
-Core team members who review PRs and guide the project:
-
-- [@SinapseAI](https://github.com/SinapseAI) - Project Lead
-
-### Becoming a Maintainer
-
-Active contributors may be invited to become maintainers. We look for:
-- Consistent quality contributions
-- Helpful community interactions
-- Understanding of project goals
-
-## Recognition
-
-### Contributors Wall
-
-All contributors are recognized in our [Contributors page](https://github.com/SinapseAI/sinapse-ai/graphs/contributors).
-
-### Release Credits
-
-Significant contributions are credited in release notes.
-
-## Governance
-
-### Decision Making
-
-- **Minor decisions**: Maintainers can decide
-- **Major decisions**: Discussed in GitHub Discussions
-- **Breaking changes**: Require RFC process
-
-### RFC Process
-
-For significant changes:
-
-1. Open a Discussion with `[RFC]` prefix
-2. Community provides feedback
-3. Maintainers make final decision
-4. Decision is documented
-
-### Code of Conduct
-
-We follow the [Contributor Covenant](CODE_OF_CONDUCT.md). Please read and respect it.
-
-Report violations to: conduct@SinapseAI.com
-
-## Getting Help
-
-### Stuck on something?
-
-1. Check the [Documentation](docs/)
-2. Search [existing Discussions](https://github.com/SinapseAI/sinapse-ai/discussions)
-3. Ask in Q&A Discussions
-4. Open a Troubleshooting discussion
-
-### Found a bug?
-
-1. Search [existing issues](https://github.com/SinapseAI/sinapse-ai/issues)
-2. If new, [open a bug report](https://github.com/SinapseAI/sinapse-ai/issues/new?template=bug_report.md)
-
-### Have an idea?
-
-1. Check if it exists in [Ideas](https://github.com/SinapseAI/sinapse-ai/discussions/categories/ideas)
-2. If new, [share your idea](https://github.com/SinapseAI/sinapse-ai/discussions/new?category=ideas)
-3. Read our [Feature Request Process](docs/feature-process.md) for detailed guidelines
-
-## Project Roadmap
-
-Want to know where SINAPSE is headed? Check out our public roadmap:
-
-- [ROADMAP.md](ROADMAP.md) - High-level vision and planned features
-- [GitHub Project](https://github.com/orgs/SinapseAI/projects/1) - Detailed tracking board
-
-The roadmap is updated monthly and reflects community input. You can influence our direction by:
-
-1. **Voting** on ideas in [Discussions](https://github.com/SinapseAI/sinapse-ai/discussions/categories/ideas)
-2. **Proposing** new features via the [RFC process](/.github/RFC_TEMPLATE.md)
-3. **Contributing** directly to planned features
-
-> Roadmap items are plans, not commitments. Priorities may shift based on community needs and technical constraints.
-
-### Feature Request Process
-
-We have a structured process for proposing new features:
-
-1. **Quick Ideas** - Open a Discussion in the "Ideas" category
-2. **RFC Process** - For significant features, write an RFC using our [template](/.github/RFC_TEMPLATE.md)
-3. **Community Voting** - Use :+1: reactions to show support
-4. **Implementation** - Approved ideas move to our backlog
-
-See [Feature Request Process](docs/feature-process.md) for complete details.
-
-## Resources
-
-### Learning SINAPSE
-
-- [Getting Started Guide](docs/getting-started.md)
-- [Architecture Overview](docs/architecture.md)
-- [User Guide](.sinapse-ai/user-guide.md)
-
-### External Resources
-
-- [SINAPSE GitHub Organization](https://github.com/SinapseAI)
-- [Changelog](CHANGELOG.md)
-
-## Internationalization
-
-We welcome contributions in all languages!
-
-- Documentation is primarily in English
-- Community discussions can be in any language
-- Portuguese (PT-BR) translations are appreciated
-
-## Project Status
-
-- Current Version: See [releases](https://github.com/SinapseAI/sinapse-ai/releases)
-- Changelog: [CHANGELOG.md](CHANGELOG.md)
-
----
-
-## Questions?
-
-Can't find what you're looking for?
-Open a Discussion or reach out to the community!
-
-**Thank you for being part of the SINAPSE community!**
-
----
-
-*This document is maintained by the SINAPSE community.*
-*Last updated: 2025-12-09*

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

@@ -1,190 +0,0 @@
-# SINAPSE Agent Flows - Detailed Agent Documentation
-
-> **EN** | [PT](../../sinapse-agent-flows/README.md) | [ES](../../es/sinapse-agent-flows/README.md) | [ZH](../../zh/sinapse-agent-flows/README.md)
-
----
-
-**Version:** 1.0.0
-**Last Updated:** 2026-02-05
-**Status:** Official Documentation
-
----
-
-## Overview
-
-This folder contains detailed documentation for all SINAPSE agents, including:
-
-- **Complete system** for each agent
-- **Mermaid flowcharts** of operations
-- **Command mapping** to tasks
-- **Integrations** between agents
-- **Workflows** involving each agent
-- **Best practices** and troubleshooting
-
----
-
-## Documented Agents
-
-| Agent | Persona | Archetype | Document |
-|-------|---------|-----------|----------|
-| **@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) |
-| **@dev** | Dex | Builder | [dev-system.md](./dev-system.md) |
-| **@devops** | Gage | Guardian | [devops-system.md](./devops-system.md) |
-| **@pm** | Morgan | Strategist | [pm-system.md](./pm-system.md) |
-| **@qa** | Quinn | Guardian | [qa-system.md](./qa-system.md) |
-| **@sm** | River | Facilitator | [sm-system.md](./sm-system.md) |
-| **@squad-creator** | Nova | Creator | [squad-creator-system.md](./squad-creator-system.md) |
-| **@ux-design-expert** | Uma | Designer | [ux-design-expert-system.md](./ux-design-expert-system.md) |
-
----
-
-## Document Structure
-
-Each agent document follows this standard structure:
-
-```
-1. Overview
-   - Main responsibilities
-   - Core principles
-
-2. Complete File List
-   - Core tasks
-   - Agent definition
-   - Templates
-   - Checklists
-   - Related files
-
-3. System Flowchart
-   - Complete Mermaid diagram
-   - Operations flow
-
-4. Command Mapping
-   - Commands -> Tasks
-   - Parameters and options
-
-5. Related Workflows
-   - Workflows using the agent
-   - Agent's role in each workflow
-
-6. Agent Integrations
-   - Who provides inputs
-   - Who receives outputs
-   - Collaborations
-
-7. Configuration
-   - Configuration files
-   - Available tools
-   - Restrictions
-
-8. Best Practices
-   - When to use
-   - What to avoid
-
-9. Troubleshooting
-   - Common issues
-   - Solutions
-
-10. Changelog
-    - Version history
-```
-
----
-
-## Agent Relationship Diagram
-
-```mermaid
-flowchart TB
-    subgraph ORCHESTRATION["Orchestration"]
-        MASTER["@sinapse-orqx\n(Orion)"]
-    end
-
-    subgraph DISCOVERY["Discovery & Planning"]
-        ANALYST["@analyst\n(Atlas)"]
-        PM["@pm\n(Morgan)"]
-    end
-
-    subgraph DESIGN["Design & Architecture"]
-        ARCHITECT["@architect\n(Aria)"]
-        UX["@ux-design-expert\n(Uma)"]
-        DATA["@data-engineer\n(Dara)"]
-    end
-
-    subgraph MANAGEMENT["Management"]
-        PO["@po\n(Pax)"]
-        SM["@sm\n(River)"]
-    end
-
-    subgraph EXECUTION["Execution"]
-        DEV["@dev\n(Dex)"]
-        QA["@qa\n(Quinn)"]
-        DEVOPS["@devops\n(Gage)"]
-    end
-
-    MASTER --> ANALYST
-    MASTER --> PM
-    ANALYST --> PM
-    PM --> UX
-    PM --> ARCHITECT
-    UX --> ARCHITECT
-    ARCHITECT --> DATA
-    ARCHITECT --> PO
-    PO --> SM
-    SM --> DEV
-    DEV --> QA
-    QA --> DEVOPS
-
-    style MASTER fill:#e3f2fd
-    style EXECUTION fill:#c8e6c9
-```
-
----
-
-## How to Use This Documentation
-
-### To Understand an Agent
-
-1. Access the desired agent's document
-2. Read the **Overview** to understand the role
-3. Check the **Commands** to know what it can do
-4. See the **Workflows** to understand the context
-
-### To Debug Issues
-
-1. Go directly to the **Troubleshooting** section
-2. Check the **Flowcharts** to understand the flow
-3. Verify **Integrations** for dependencies
-
-### To Extend the System
-
-1. Analyze the **File List** to know what to modify
-2. Follow **Best Practices** to maintain consistency
-3. Update the **Changelog** after changes
-
----
-
-## Relationship with Other Documentation
-
-| Documentation | Location | Purpose |
-|---------------|----------|---------|
-| Meta-Agent Commands | [docs/meta-agent-commands.md](../../meta-agent-commands.md) | Quick reference |
-| Workflows Guide | [docs/guides/workflows-guide.md](../../guides/workflows-guide.md) | Workflows guide |
-| SINAPSE Workflows | [docs/sinapse-workflows/](../../sinapse-workflows/) | Detailed workflows |
-| Architecture | [docs/architecture/](../../architecture/) | Technical architecture |
-
----
-
-## Contributing
-
-To add or update agent documentation:
-
-1. Follow the standard structure described above
-2. Include updated Mermaid diagrams
-3. Keep the changelog up to date
-4. Create translations in PT and ES
-
----
-
-*SINAPSE Agent Flows Documentation v1.0 - Detailed documentation of the agent system*