# Creavax

> Creavax is an AI creative studio with reusable templates and connected AI production workflows.

## AI Template Builder

When an AI system creates a Creavax Template Builder package, it should read the canonical live context first:

- [Creavax AI Context](https://creavax.com/developers/templates/ai-context): Human-readable canonical instructions plus the current live model capability catalog.
- [Creavax AI Context JSON](https://creavax.com/developers/templates/ai-context.json): Machine-readable current schema, workflow rules and live model capabilities.
- [Creavax AI Template Guide](https://creavax.com/developers/templates/ai-guide): Detailed examples and portable Template Builder guidance.
- [Creavax Template Schema](https://creavax.com/backend/api/v1/template-packages/schema): Live package schema used by Creavax validation.

Core workflow rule:

- Input -> Agent
- Agent -> Model
- Agent -> Agent (optional directed multi-step workflows)
- Agent -> Output
- Never Model -> Output
- One Model node/slot belongs to exactly one Agent. If two Agents need the same capability, give each Agent its own Model node; Creavax may resolve both nodes to the same real model.

Execution rule:

- Agents with no Agent dependencies may start in parallel.
- Agent -> Agent is both a data edge and an execution dependency. The downstream Agent waits for all connected upstream Agents to complete.
- Mixed graphs automatically combine parallel independent branches with sequential dependent branches.
- Agent cycles are forbidden.

Portable model rule:

- Use current model capabilities to understand what Creavax can run.
- In .creavax-template.json, keep model slots requirement-based using inputs, outputs, operations and features.
- Do not hard-code provider IDs or live model_key values into portable template model slots.
- Creavax resolves a compatible active model through its Model Capability Resolver at import/runtime.