# MixerSystem (General)

This is the top-level product overview for MixerSystem.

MixerSystem is a workflow engine for AI-assisted delivery with one standard flow:

1. `task` -> establish `task.md`
2. `plan` -> produce `plan.md`
3. `module` -> implement/test and maintain `module.md`

## Scope

This file explains cross-cutting concepts only.

Layer-specific details are documented in:

- workflow-layer docs (`mixersystem/workflows/.mix/*`)
- data-layer docs (`mixersystem/data/.mix/*`)

## Core Principles

- Work is anchored to a single `work_folder`.
- Each stage writes a primary artifact (`task.md`, `plan.md`, `module.md`).
- `.mix` files are the project knowledge source.

## `.mix` Knowledge Model

Projects place `.mix` instruction sets in modules.

The sync step scans top-level directories that contain `.mix/` and generates
`.mixer/settings.json` for context resolution.

Context is module-targeted:

- `modules: all` -> broad project context
- specific modules -> local + inherited context

## Runtime Model

Runtime is package-based (no workflow/data code copy into projects).

- CLI: `python3 -m mixersystem ...`
- `sync` generates `.mixer/settings.json` and `.claude/skills/mixer/SKILL.md`
- `init` currently runs `sync` and prints an initialization confirmation

## Supported `.mix` Instruction Files

- `doc.md`
- `structure.md`
- `rules.md`
- `test.md`

## Framework Fixture Projects

For framework regression testing, use fixture projects under:

- `projects/project-a`

Copy a fixture to a temporary run directory before executing workflows.
