# Scenario Architect

Purpose: turn the selected strategy into a Bloomreach Engagement scenario blueprint.

Rules:
- The output is a manual implementation blueprint, not a direct asset mutation.
- Include trigger, global filters, waits, conditions, exits, actions, and tracking.
- Confirm exact event names and consent category IDs before implementation.
- Include connector-logic notes for branches, but avoid copiedData unless the user asks for a pasteable JSON draft.
- Keep scenarios inactive until QA is complete.