whiteport-design-studio 0.2.2 → 0.3.0

package/src/workflows/6-asset-generation/data/content-creation-workshop-guide.md

@@ -54,7 +54,7 @@ The Content Creation Workshop is a disciplined, multi-model framework for genera
 - Defines: WHAT must this content accomplish? HOW will we know it worked?
 - Answers: What's the measurable outcome? Which models should we emphasize?
 
-### 1. VTC = Strategic Foundation
+### 1. Trigger Map = Strategic Foundation
 - Provides: Business goal, solution, user, driving forces, customer awareness positioning
 - Answers: WHO are we serving? WHAT motivates them? WHERE are they in their journey?
 
@@ -81,7 +81,7 @@ The Content Creation Workshop is a disciplined, multi-model framework for genera
 The workshop follows **7 sequential considerations** (agents can adapt flow naturally):
 
 0. **Define Content Purpose** - What job must this content do?
-1. **Load VTC Context** - Establish strategic foundation
+1. **Load Trigger Map Context** - Establish strategic foundation
 2. **Apply Customer Awareness Strategy** - Determine appropriate language & information
 3. **Define Required Action** - Filter for relevance
 4. **Frame User Empowerment** - Set tone and transformation narrative
@@ -115,12 +115,12 @@ When you encounter content creation in a workflow:
      - Collaborative conversation through considerations
      - Adapt flow naturally (skip/combine as appropriate)
 
-3. **Check for VTC** - Does the current context have a defined VTC?
+3. **Check for Trigger Map** - Does the current context have a Trigger Map?
    - If YES → Proceed with strategic generation
-   - If NO → Suggest creating a VTC first (route to VTC Workshop)
+   - If NO → Suggest creating a Trigger Map first (route to Phase 2)
 
 4. **Execute Strategically:**
-   - Consider all strategic layers (VTC, Awareness, Action, Empowerment, Structure)
+   - Consider all strategic layers (Trigger Map, Awareness, Action, Empowerment, Structure)
    - Emphasize models based on content purpose (see Content Purpose Guide)
    - Don't force rigid steps - adapt naturally
 
@@ -141,7 +141,7 @@ You control the strategic context and mode:
 2. **Choose your mode:**
    - Need quick suggestions? → "Suggest content for this hero section"
    - Want to explore together? → "Let's work through the homepage hero"
-3. **Provide context** or let agent find it (VTC, page purpose, user state)
+3. **Provide context** or let agent find it (Trigger Map, page purpose, user state)
 4. **Review against purpose** - Does it do its job? (objective criteria)
 5. **Select or refine** - Choose variant or combine elements
 6. **Iterate if needed** - Purpose not achieved? Refine and regenerate
@@ -233,7 +233,7 @@ DESIGNER: "Make headline more fear-focused"
    - Model priority emphasis
 
 2. **Strategic Context Document** (shows your thinking)
-   - VTC reference
+   - Trigger Map reference
    - Awareness journey map
    - Action requirement
    - Empowerment frame
@@ -285,7 +285,7 @@ DESIGNER: "Make headline more fear-focused"
 **Micro-Steps:**
 - `steps/workflow.md` - Sequential execution guide
 - `steps/step-00-define-purpose.md`
-- `steps/step-01-load-vtc-context.md`
+- `steps/step-01-load-trigger-map-context.md`
 - `steps/step-02-awareness-strategy.md`
 - `steps/step-03-action-filter.md`
 - `steps/step-04-empowerment-frame.md`
@@ -306,8 +306,7 @@ DESIGNER: "Make headline more fear-focused"
 - [Kathy Sierra Badass Users](../../../docs/models/kathy-sierra-badass-users.md)
 
 **Whiteport Methods:**
-- [Value Trigger Chain](../../../docs/method/value-trigger-chain-guide.md)
-- [VTC Advanced Usage](../../../docs/learn/module-06-trigger-mapping/lesson-12-vtc-advanced-usage.md)
+- [Trigger Mapping Guide](../../../docs/method/trigger-mapping-guide.md)
 - [Content Purpose Guide](../../../docs/method/content-purpose-guide.md) - **Start here for content effectiveness**
 
 **Workflows:**

package/src/workflows/6-asset-generation/steps-c/step-00-define-purpose.md

@@ -1,7 +1,7 @@
 ---
 name: 'step-00-define-purpose'
 description: 'Define the measurable job and purpose for content before generation begins'
-nextStepFile: './step-01-load-vtc-context.md'
+nextStepFile: './step-01-load-trigger-map-context.md'
 ---
 
 # Step 0: Define Content Purpose
@@ -83,7 +83,7 @@ Define measurable or observable outcomes: "User recognizes themselves and contin
 
 Ask: **"Which strategic models matter most for THIS job?"**
 
-Present the Model Priority Matrix from the Content Purpose Guide. Different content types emphasize different models (Customer Awareness, Golden Circle, Badass Users, VTC, Action Mapping). Discuss and assign star ratings per model.
+Present the Model Priority Matrix from the Content Purpose Guide. Different content types emphasize different models (Customer Awareness, Golden Circle, Badass Users, Trigger Map, Action Mapping). Discuss and assign star ratings per model.
 
 ### 6. Document Purpose Definition
 
@@ -124,7 +124,7 @@ Display: **"Select an Option:** [C] Continue"
 
 ## CRITICAL STEP COMPLETION NOTE
 
-ONLY WHEN C is selected and the purpose definition is documented will you load {nextStepFile} to begin loading VTC context.
+ONLY WHEN C is selected and the purpose definition is documented will you load {nextStepFile} to begin loading Trigger Map context.
 
 ---
 

package/src/workflows/6-asset-generation/steps-c/step-01-load-trigger-map-context.md

@@ -0,0 +1,147 @@
+---
+name: 'step-01-load-trigger-map-context'
+description: 'Establish the strategic foundation by loading relevant Trigger Map context for content creation'
+nextStepFile: './step-02-awareness-strategy.md'
+---
+
+# Step 1: Load Trigger Map Context
+
+## STEP GOAL:
+
+Load the relevant Trigger Map context — WHO we are serving, WHAT motivates them, and WHERE they are in their awareness journey — so that all content decisions are anchored in strategy, not guesswork.
+
+## MANDATORY EXECUTION RULES (READ FIRST):
+
+### Universal Rules:
+
+- NEVER generate content without user input
+- CRITICAL: Read the complete step file before taking any action
+- CRITICAL: When loading next step with 'C', ensure entire file is read
+- YOU ARE A FACILITATOR, not a content generator
+- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
+
+### Role Reinforcement:
+
+- You are a strategic content analyst loading the Trigger Map foundation
+- If you already have been given a name, communication_style and identity, continue to use those while playing this new role
+- We engage in collaborative dialogue, not command-response
+- You bring strategic methodology, user brings their project knowledge
+- Maintain a thorough, investigative tone — the context must be correct before proceeding
+
+### Step-Specific Rules:
+
+- Focus ONLY on loading and validating the Trigger Map context
+- FORBIDDEN to generate content text or apply awareness strategy in this step
+- If no Trigger Map exists, flag the gap and work with whatever context is available
+- Ensure all fields are populated before proceeding
+
+## EXECUTION PROTOCOLS:
+
+- Follow the Sequence of Instructions exactly
+- Document Trigger Map context for traceability
+- Check for Trigger Map in project documentation before asking user
+- FORBIDDEN to proceed without confirmed strategic context
+
+## CONTEXT BOUNDARIES:
+
+- Available context: Purpose definition from Step 0, project configuration
+- Focus: Loading and validating the correct Trigger Map context for this content
+- Limits: Do not apply the context yet — just load and confirm it
+- Dependencies: Purpose definition from Step 0
+
+## Sequence of Instructions (Do not deviate, skip, or optimize)
+
+### 1. Load the Trigger Map
+
+Search project documentation:
+- Check `{output_folder}/B-Trigger-Map/00-trigger-map.md` (the hub document)
+- Check persona documents in `{output_folder}/B-Trigger-Map/`
+- If no Trigger Map folder exists, check Product Brief for business context
+
+### 2. Identify the Relevant Context
+
+Ask: **"Which business goal and persona does this content serve?"**
+
+- Present the business goals from the Trigger Map — which one applies?
+- Present the personas — which one is the target audience for this content?
+- Present driving forces for that persona — which are most relevant?
+
+### 3. Present and Confirm Context
+
+Display the selected context:
+
+```
+Business Goal: [selected goal from Trigger Map]
+Persona: [persona name and description]
+Driving Forces:
+  - Positive: [relevant positive drivers]
+  - Negative: [relevant negative drivers]
+Customer Awareness: [START level] → [END level]
+```
+
+Ask: **"Is this the right strategic context for this content? Any adjustments?"**
+
+### 4. Handle Missing Trigger Map
+
+If no Trigger Map exists:
+- Explain that the Trigger Map (Phase 2) provides the strategic foundation for content
+- Recommend completing Phase 2 first for best results
+- If the user wants to proceed anyway, use whatever context is available from the Product Brief
+- Note the gap and flag that content may need revision after the Trigger Map is completed
+
+### 5. Document Context
+
+Save the confirmed context:
+
+```yaml
+trigger_map_context:
+  business_goal: "[goal text]"
+  persona:
+    name: "[persona name]"
+    description: "[brief persona description]"
+  driving_forces:
+    positive: "[relevant positive drivers]"
+    negative: "[relevant negative drivers]"
+  customer_awareness:
+    start: "[awareness level where user begins]"
+    end: "[awareness level we want them to reach]"
+```
+
+### 6. Present MENU OPTIONS
+
+Display: **"Select an Option:** [C] Continue"
+
+#### Menu Handling Logic:
+
+- IF C: Save context, then load, read entire file, then execute {nextStepFile}
+- IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)
+
+#### EXECUTION RULES:
+
+- ALWAYS halt and wait for user input after presenting menu
+- ONLY proceed to next step when user selects 'C'
+- User can chat or ask questions — always respond and then end with display again of the menu options
+
+## CRITICAL STEP COMPLETION NOTE
+
+ONLY WHEN C is selected and the Trigger Map context is confirmed and documented will you load {nextStepFile} to begin applying the Customer Awareness Strategy.
+
+---
+
+## SYSTEM SUCCESS/FAILURE METRICS
+
+### SUCCESS:
+
+- Trigger Map context is identified and loaded
+- All fields are populated (goal, persona, driving forces, awareness)
+- User confirms this is the correct context for this content
+- Context is documented for traceability
+
+### FAILURE:
+
+- Proceeding without confirmed strategic context
+- Generating content text in this step
+- Applying awareness strategy before context is loaded
+- Not waiting for user input at menu
+
+**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/workflows/6-asset-generation/steps-c/step-02-awareness-strategy.md

@@ -8,7 +8,7 @@ nextStepFile: './step-03-action-filter.md'
 
 ## STEP GOAL:
 
-Translate the VTC's awareness positioning into a concrete content strategy — determining what language the user can understand, what information they need, what proof is required, and what emotional journey we are facilitating.
+Translate the Trigger Map's awareness positioning into a concrete content strategy — determining what language the user can understand, what information they need, what proof is required, and what emotional journey we are facilitating.
 
 ## MANDATORY EXECUTION RULES (READ FIRST):
 
@@ -44,20 +44,20 @@ Translate the VTC's awareness positioning into a concrete content strategy — d
 
 ## CONTEXT BOUNDARIES:
 
-- Available context: Purpose definition (Step 0), VTC context (Step 1)
+- Available context: Purpose definition (Step 0), Trigger Map context (Step 1)
 - Focus: Translating awareness levels into content strategy decisions
 - Limits: Do not write content — define the strategy for it
-- Dependencies: Confirmed VTC with awareness START and END levels
+- Dependencies: Confirmed Trigger Map with awareness START and END levels
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
 ### 1. Validate Starting Awareness Level
 
-Present the START level from VTC and describe what it means. Confirm with user: does this match where users are when they encounter this content?
+Present the START level from the Trigger Map and describe what it means. Confirm with user: does this match where users are when they encounter this content?
 
 ### 2. Clarify Target Awareness Level
 
-Present the END level from VTC and describe the shift. Confirm: is this the right awareness goal for this content?
+Present the END level from the Trigger Map and describe the shift. Confirm: is this the right awareness goal for this content?
 
 ### 3. Determine Awareness-Appropriate Language
 

package/src/workflows/6-asset-generation/steps-c/step-03-action-filter.md

@@ -44,10 +44,10 @@ Apply Action Mapping (Cathy Moore) to identify the specific action the user must
 
 ## CONTEXT BOUNDARIES:
 
-- Available context: Purpose (Step 0), VTC (Step 1), Awareness Strategy (Step 2)
+- Available context: Purpose (Step 0), Trigger Map (Step 1), Awareness Strategy (Step 2)
 - Focus: What action must the user take, and what information enables it
 - Limits: Do not write content — filter what information to include
-- Dependencies: VTC and Awareness Strategy from previous steps
+- Dependencies: Trigger Map and Awareness Strategy from previous steps
 
 ## Sequence of Instructions (Do not deviate, skip, or optimize)
 
@@ -63,13 +63,13 @@ Push for specific behaviors, not vague understanding:
 
 ### 2. Connect Action to Business Goal
 
-Trace the logic: User does [action] → which leads to [outcome] → which drives [business goal from VTC].
+Trace the logic: User does [action] → which leads to [outcome] → which drives [business goal from Trigger Map].
 
-Ask: **"Does this action clearly serve the VTC's business goal?"**
+Ask: **"Does this action clearly serve the Trigger Map's business goal?"**
 
 ### 3. Connect Action to Driving Forces
 
-From VTC driving forces: **"By taking this action, how does the user move toward their wish or away from their fear?"**
+From the Trigger Map driving forces: **"By taking this action, how does the user move toward their wish or away from their fear?"**
 
 ### 4. Determine Essential Information
 
@@ -96,7 +96,7 @@ action_filter:
     description: "[Specific action user must be able to take]"
     success_criteria: "[How we know they can do it]"
   business_impact:
-    connection: "[How this action drives the VTC business goal]"
+    connection: "[How this action drives the business goal]"
     logic: "[Action → Outcome → Goal]"
   user_motivation:
     positive_driver: "[How action satisfies their wish]"
@@ -141,7 +141,7 @@ ONLY WHEN C is selected and the action filter is documented will you load {nextS
 ### ✅ SUCCESS:
 
 - Specific action identified (not vague "understanding")
-- Action connects to VTC business goal
+- Action connects to Trigger Map business goal
 - Action satisfies user's driving forces
 - Essential information determined (what enables the action)
 - Unnecessary information identified (what does not enable action)

package/src/workflows/6-asset-generation/steps-c/step-04-empowerment-frame.md

@@ -44,7 +44,7 @@ Apply Kathy Sierra's Badass Users framework to frame content around user capabil
 
 ## CONTEXT BOUNDARIES:
 
-- Available context: Purpose (Step 0), VTC (Step 1), Awareness (Step 2), Action Filter (Step 3)
+- Available context: Purpose (Step 0), Trigger Map (Step 1), Awareness (Step 2), Action Filter (Step 3)
 - Focus: Framing content around user capability, not product features
 - Limits: Do not write content — define the empowerment frame for it
 - Dependencies: Action Filter from Step 3

package/src/workflows/6-asset-generation/steps-c/step-05-structural-order.md

@@ -44,7 +44,7 @@ Apply Simon Sinek's Golden Circle to sequence all content from previous steps in
 
 ## CONTEXT BOUNDARIES:
 
-- Available context: Purpose (Step 0), VTC (Step 1), Awareness (Step 2), Action Filter (Step 3), Empowerment Frame (Step 4)
+- Available context: Purpose (Step 0), Trigger Map (Step 1), Awareness (Step 2), Action Filter (Step 3), Empowerment Frame (Step 4)
 - Focus: Sequencing existing content elements into persuasive order
 - Limits: Do not write final content — organize the structure for it
 - Dependencies: All previous steps provide the content elements to sequence
@@ -55,7 +55,7 @@ Apply Simon Sinek's Golden Circle to sequence all content from previous steps in
 
 Ask: **"What's the emotional opening that connects to their driving forces?"**
 
-Opens with user's current emotional state, connects to driving forces from VTC, makes them care before explaining the solution.
+Opens with user's current emotional state, connects to driving forces from the Trigger Map, makes them care before explaining the solution.
 
 ### 2. Identify the HOW
 

package/src/workflows/6-asset-generation/steps-c/step-06-generate-content.md

@@ -44,7 +44,7 @@ Generate 2-3 strategically grounded content variations based on all strategic co
 
 ## CONTEXT BOUNDARIES:
 
-- Available context: All outputs from Steps 0-5 (Purpose, VTC, Awareness, Action, Empowerment, Structure)
+- Available context: All outputs from Steps 0-5 (Purpose, Trigger Map, Awareness, Action, Empowerment, Structure)
 - Focus: Synthesizing strategy into actual content text, then refining with user
 - Limits: Variations are strategic alternatives, not random drafts
 - Dependencies: Complete WHY-HOW-WHAT structure from Step 5
@@ -72,7 +72,7 @@ Ask: **"Which variation resonates most with you?"** Allow selection, combination
 
 Ask: **"Does this feel aligned with the strategic context?"**
 
-Check against: VTC business goal, driving forces, awareness level, required action, capability framing, WHY-HOW-WHAT structure.
+Check against: Trigger Map business goal, driving forces, awareness level, required action, capability framing, WHY-HOW-WHAT structure.
 
 ### 5. Refinement
 
@@ -89,7 +89,7 @@ Ask: **"Does this move the user from START to END awareness?"** Verify the journ
 ### 8. Document Final Content
 
 Save using content-output template with full strategic traceability:
-- VTC reference, awareness journey, action enabled, empowerment achieved
+- Trigger Map reference, awareness journey, action enabled, empowerment achieved
 - Implementation notes (technical, design, language tags, asset needs)
 
 ### 9. Present MENU OPTIONS

package/src/workflows/6-asset-generation/templates/content-output.template.md

@@ -11,10 +11,10 @@
 
 ## Strategic Foundation
 
-### Step 1: VTC Context
+### Step 1: Trigger Map Context
 
 ```yaml
-vtc_reference:
+trigger_map_reference:
   business_goal: "{goal text}"
   solution: "{solution name/description}"
   user:
@@ -81,7 +81,7 @@ action_filter:
     success_criteria: "{How we know they can do it}"
   
   business_impact:
-    connection: "{How this action drives the VTC business goal}"
+    connection: "{How this action drives the business goal}"
     logic: "{Action → Outcome → Goal}"
   
   user_motivation:
@@ -293,7 +293,7 @@ WHAT Section:
 
 **This content serves:**
 
-- **VTC Business Goal:** {How this drives the goal}
+- **Business Goal:** {How this drives the goal}
 - **User Driving Forces:** 
   - Positive: {How it satisfies wish}
   - Negative: {How it addresses fear}
@@ -345,5 +345,5 @@ WHAT Section:
 ---
 
 _Created using WDS Content Creation Workshop (5-Model Framework)_  
-_Models: VTC, Customer Awareness Cycle, Action Mapping, Badass Users, Golden Circle_
+_Models: Trigger Map, Customer Awareness Cycle, Action Mapping, Badass Users, Golden Circle_
 

package/src/workflows/6-asset-generation/workflow-content.md

@@ -11,17 +11,14 @@ description: Strategic text content generation using the 5-model framework
 
 ## INITIALIZATION
 
-### Agent Dialog Gate
-
-1. Check for pending activity dialogs
-2. If none, suggest creating one
-3. Load dialog context
+### Design Log
+Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
 
 
 ## The Five-Model Framework
 
 1. **Content Purpose** — The job to do
-2. **VTC** — Strategic foundation
+2. **Trigger Map** — Strategic foundation
 3. **Customer Awareness Cycle** — Content strategy
 4. **Action Mapping** — Content filter
 5. **Badass Users** — Tone & frame
@@ -36,7 +33,7 @@ Execute steps in `./steps-c/`:
 | Step | File | Purpose |
 |------|------|---------|
 | 00 | step-00-define-purpose.md | Define content purpose |
-| 01 | step-01-load-vtc-context.md | Load VTC context |
+| 01 | step-01-load-trigger-map-context.md | Load Trigger Map context |
 | 02 | step-02-awareness-strategy.md | Awareness strategy |
 | 03 | step-03-action-filter.md | Action mapping filter |
 | 04 | step-04-empowerment-frame.md | Empowerment framing |

package/src/workflows/6-asset-generation/workflow-figma.md

@@ -14,11 +14,8 @@ web_bundle: true
 
 ## INITIALIZATION
 
-### Agent Dialog Gate
-
-1. Check for pending activity dialogs
-2. If none, suggest creating one
-3. Load dialog context
+### Design Log
+Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
 
 
 ## WHEN TO USE

package/src/workflows/6-asset-generation/workflow-icons.md

@@ -11,11 +11,8 @@ description: Generate icon sets and individual icons matching design system
 
 ## INITIALIZATION
 
-### Agent Dialog Gate
-
-1. Check for pending activity dialogs
-2. If none, suggest creating one
-3. Load dialog context
+### Design Log
+Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
 
 
 ## Steps

package/src/workflows/6-asset-generation/workflow-images.md

@@ -11,11 +11,8 @@ description: Generate photos, illustrations, and backgrounds from specifications
 
 ## INITIALIZATION
 
-### Agent Dialog Gate
-
-1. Check for pending activity dialogs
-2. If none, suggest creating one
-3. Load dialog context
+### Design Log
+Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
 
 
 ## Steps

package/src/workflows/6-asset-generation/workflow-page-designs.md

@@ -11,11 +11,8 @@ description: Generate full page design compositions from specifications
 
 ## INITIALIZATION
 
-### Agent Dialog Gate
-
-1. Check for pending activity dialogs
-2. If none, suggest creating one
-3. Load dialog context
+### Design Log
+Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
 
 
 ## Steps

package/src/workflows/6-asset-generation/workflow-stitch.md

@@ -14,11 +14,8 @@ web_bundle: true
 
 ## INITIALIZATION
 
-### Agent Dialog Gate
-
-1. Check for pending activity dialogs
-2. If none, suggest creating one
-3. Load dialog context
+### Design Log
+Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
 
 
 ## OVERVIEW
@@ -59,12 +56,11 @@ Visual Reference + Sketch + Specification = Stitch Generation
 
 ## WORKFLOW
 
-### Step 1: Create Dialog
+### Step 1: Create Generation Log
 
-Create a Stitch generation dialog in the project's Agent Dialogs folder.
+Create a Stitch generation log in the agent experiences folder.
 
-**Template:** `_agent-dialogs/templates/dialog-types/stitch-generation.template.md`
-**Location:** `{output_folder}/_progress/agent-dialogs/{YYYY-MM-DD}-freya-stitch-{feature}.md`
+**Location:** `{output_folder}/_progress/agent-experiences/{YYYY-MM-DD}-stitch-{feature}.md`
 
 ### Step 2: Pre-Generation Questions
 

package/src/workflows/6-asset-generation/workflow-ui-elements.md

@@ -11,11 +11,8 @@ description: Generate UI components — buttons, cards, forms, navigation elemen
 
 ## INITIALIZATION
 
-### Agent Dialog Gate
-
-1. Check for pending activity dialogs
-2. If none, suggest creating one
-3. Load dialog context
+### Design Log
+Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
 
 
 ## Steps

package/src/workflows/6-asset-generation/workflow-videos.md

@@ -11,11 +11,8 @@ description: Generate motion content and animations from specifications
 
 ## INITIALIZATION
 
-### Agent Dialog Gate
-
-1. Check for pending activity dialogs
-2. If none, suggest creating one
-3. Load dialog context
+### Design Log
+Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
 
 
 ## Steps

package/src/workflows/6-asset-generation/workflow-wireframes.md

@@ -11,11 +11,8 @@ description: Generate outline wireframes from page specifications
 
 ## INITIALIZATION
 
-### Agent Dialog Gate
-
-1. Check for pending activity dialogs
-2. If none, suggest creating one
-3. Load dialog context
+### Design Log
+Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
 
 
 ## Steps

package/src/workflows/6-asset-generation/workflow.md

@@ -30,7 +30,7 @@ Phase 6 is **menu-driven**, not linear. The user picks what to generate.
 1. **READ COMPLETELY**: Always read the entire step file before action
 2. **FOLLOW SEQUENCE**: Execute all sections in order
 3. **WAIT FOR INPUT**: Halt at menus and wait for user selection
-4. **SAVE STATE**: Update dialog tracking when completing steps
+4. **SAVE STATE**: Update design log when completing steps
 
 ---
 
@@ -42,11 +42,9 @@ Load and read full config from `{project-root}/_bmad/wds/config.yaml` and resolv
 - `project_name`, `output_folder`, `user_name`
 - `communication_language`, `document_output_language`
 
-### 2. Agent Dialog Gate
+### 2. Design Log
 
-1. Check `{output_folder}/_progress/agent-dialogs/` for pending asset generation dialogs
-2. If pending, present with status
-3. If none, suggest creating one
+Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
 
 ### 3. Activity Menu
 

package/src/workflows/7-design-system/steps-c/step-01-scan-existing.md

@@ -94,7 +94,7 @@ Display: "**Select an Option:** [C] Continue to Compare Attributes"
 
 #### Menu Handling Logic:
 
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF C: Update design log, then load, read entire file, then execute {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#6-present-menu-options)
 
 #### EXECUTION RULES:
@@ -117,7 +117,7 @@ ONLY WHEN [C continue option is selected and scan is complete with candidate lis
 - All instructions executed in sequence
 - Results documented and presented to user
 - User confirmed before proceeding
-- Agent dialog updated
+- Design log updated
 
 ### ❌ SYSTEM FAILURE:
 

package/src/workflows/7-design-system/steps-c/step-02-compare-attributes.md

@@ -333,7 +333,7 @@ Display: "**Select an Option:** [C] Continue to Calculate Similarity"
 
 #### Menu Handling Logic:
 
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF C: Update design log, then load, read entire file, then execute {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options](#8-present-menu-options)
 
 #### EXECUTION RULES:
@@ -356,7 +356,7 @@ ONLY WHEN [C continue option is selected and all four dimensions compared with s
 - All instructions executed in sequence
 - Results documented and presented to user
 - User confirmed before proceeding
-- Agent dialog updated
+- Design log updated
 
 ### ❌ SYSTEM FAILURE: