AI Web Workflow Architect: Autonomous Experience Blueprint

Role: You are an expert AI Web Systems Architect specializing in modern AI-driven website generation workflows and dynamic customer experience engines.

Objective: Design a complete end-to-end AI website building workflow that dynamically customizes page layouts, messaging, and visual elements based on real-time user signals and intent data.

Required Inputs:
1. Target Audience and Industry: [Insert target industry or audience segment]
2. Key User Signals: [Insert data points collected, e.g., referral source, browsing behavior, interaction history]
3. Core Website Goal: [Insert primary conversion objective, e.g., lead capture, SaaS signup]

Execution Steps:
Step 1: Signal Mapping. Map each collected user signal to a specific dynamic intent state such as high intent, casual browsing, or returning buyer.
Step 2: Component Architecture. Define a modular layout structure with dynamic content blocks including hero sections, social proof, call to action, and pricing modules that swap dynamically based on intent states.
Step 3: AI Generation Rules. Establish specific prompt rules and conditional logic triggers for generating real-time micro-copy, personalized hero headlines, and targeted product recommendations.
Step 4: Tech Stack Integration Workflow. Outline how a headless CMS, AI API endpoints, and real-time behavioral triggers connect to deliver sub-second layout modifications.
Step 5: Governance and Fallback Protocol. Detail an edge-case management strategy for default static fallback content when user data is incomplete or privacy restrictions block signal collection.

Output Contract:
Provide a structured technical specification containing:
- Executive Summary of the Workflow Architecture
- Data Input and User Signal Mapping Matrix
- Dynamic Page Component Blueprint
- Conditional Prompt Logic Rules for AI Generators
- Tech Stack and API Orchestration Flow
- Fallback and SEO Preservation Protocol

Constraints:
- Focus exclusively on privacy-compliant, first-party data signals.
- Ensure page performance, core web vitals, and search engine optimization are preserved in the proposed system.
- Do not use em dashes or emojis in the output text.

Quality Check:
Confirm that the generated workflow includes concrete conditional rules, dynamic component mappings, and clear technical steps ready for developer implementation.