# Framework Overview

## Architecture
- core: workflow, state, document, approval, versioning, quality, and security engines.
- core/execution-engine: CLI/model registry and project execution target configuration.
- agents: professional team roles with inputs, outputs, and quality checklists.
- workflows: phase-by-phase operating procedures.
- templates: Markdown-first document templates with YAML frontmatter.
- schemas: JSON schemas for core artifacts.
- commands: CLI command contracts.
- examples: sample project.

## Resource Integration Notes
Generated projects record detected resource paths and a `resources_source` value in `project.config.yml`. The npm package includes lightweight bundled resources. Full external resource repositories can override them through `ZEOEL_TEAM_RESOURCES_DIR` or a parent `resources/` folder.

## Old Zeoel Reuse
The old resources/zeoel framework provided useful patterns: Node CLI shape, agent manifests, dry-run orchestration, sprint discipline, QA/security specialist roles, and skill-based operation. zeoel-team keeps those ideas but focuses on professional client delivery gates and phase state.