whiteport-design-studio 0.2.2 → 0.3.0

package/src/workflows/5-agentic-development/steps-p/1-prototype-setup.md

@@ -108,7 +108,7 @@ HTML files will be placed in root as they're created.
 Display: "**Select an Option:** [C] Continue to Step 2: Scenario Analysis"
 
 #### 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]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-p/2-scenario-analysis.md

@@ -99,7 +99,7 @@ Create `work/Logical-View-Map.md` with view details, build order, and notes.
 Display: "**Select an Option:** [C] Continue to Step 3: Logical View Breakdown"
 
 #### 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]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-p/3-logical-view-breakdown.md

@@ -96,7 +96,7 @@ Present breakdown to user for approval.
 Display: "**Select an Option:** [C] Continue to Step 4a: Announce and Gather"
 
 #### 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]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-p/4a-announce-and-gather.md

@@ -80,7 +80,7 @@ Present requirements summary to user including object count, specifications refe
 Display: "**Select an Option:** [C] Continue to Step 4b: Create Story File"
 
 #### 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]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-p/4b-create-story-file.md

@@ -79,7 +79,7 @@ Present summary and offer user the choice to review the story first or proceed t
 Display: "**Select an Option:** [C] Continue to Step 4c: Implement Section"
 
 #### 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]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-p/4c-implement-section.md

@@ -106,7 +106,7 @@ Announce implementation start.
 Display: "**Select an Option:** [C] Continue to Step 4d: Present for Testing"
 
 #### 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]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-p/4d-present-for-testing.md

@@ -95,7 +95,7 @@ Display based on user feedback:
 - **If improvement suggested**: "[C] Continue to Step 4f: Handle Improvement"
 
 #### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute the appropriate next step file
+- IF C: Update design log, then load, read entire file, then execute the appropriate next step file
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-p/4e-handle-issue.md

@@ -94,7 +94,7 @@ Present the fix, explain what changed, why it works now, and request re-testing.
 Display: "**Select an Option:** [C] Continue to Step 4d: Present for Testing (re-test)"
 
 #### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute `./4d-present-for-testing.md`
+- IF C: Update design log, then load, read entire file, then execute `./4d-present-for-testing.md`
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-p/4f-handle-improvement.md

@@ -90,7 +90,7 @@ After re-presenting, route back to Step 4d for user feedback.
 Display: "**Select an Option:** [C] Continue to Step 4d: Present for Testing (re-test)"
 
 #### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute `./4d-present-for-testing.md`
+- IF C: Update design log, then load, read entire file, then execute `./4d-present-for-testing.md`
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-p/4g-section-approved.md

@@ -90,8 +90,8 @@ Display based on status:
 - **If all complete**: "[C] Continue to Step 5: Finalization"
 
 #### Menu Handling Logic:
-- IF C (more sections): Update agent dialog, then load, read entire file, then execute `./4a-announce-and-gather.md`
-- IF C (all complete): Update agent dialog, then load, read entire file, then execute {nextStepFile}
+- IF C (more sections): Update design log, then load, read entire file, then execute `./4a-announce-and-gather.md`
+- IF C (all complete): Update design log, then load, read entire file, then execute {nextStepFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-p/5-finalization.md

@@ -102,7 +102,7 @@ If YES: Scenario prototype complete!
 Display: "**Select an Option:** [M] Return to Activity Menu"
 
 #### Menu Handling Logic:
-- IF M: Update agent dialog, then load, read entire file, then execute {activityWorkflowFile}
+- IF M: Update design log, then load, read entire file, then execute {activityWorkflowFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-r/step-01-identify-target.md

@@ -125,7 +125,7 @@ Target Overview:
 Display: "**Select an Option:** [C] Continue to Step 2: Explore and Capture"
 
 #### 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]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-r/step-02-explore-and-capture.md

@@ -139,7 +139,7 @@ Note the base spacing unit and common values.
 Display: "**Select an Option:** [C] Continue to Step 3: Generate Specs"
 
 #### 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]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-r/step-03-generate-specs.md

@@ -112,7 +112,7 @@ output/
 Display: "**Select an Option:** [C] Continue to Step 4: Extract Design System"
 
 #### 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]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-r/step-04-extract-design-system.md

@@ -110,7 +110,7 @@ Save to the output folder alongside the page specs from Step 03.
 Display: "**Select an Option:** [M] Return to Activity Menu"
 
 #### Menu Handling Logic:
-- IF M: Update agent dialog, then load, read entire file, then execute {activityWorkflowFile}
+- IF M: Update design log, then load, read entire file, then execute {activityWorkflowFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-t/step-01-prepare.md

@@ -145,7 +145,7 @@ Calculate total testing time with 20% buffer.
 Display: "**Select an Option:** [C] Continue to Step 2: Execute"
 
 #### 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]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-t/step-02-execute.md

@@ -138,7 +138,7 @@ After all tests complete, create overall test summary:
 Display: "**Select an Option:** [C] Continue to Step 3: Document Issues"
 
 #### 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]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-t/step-03-document-issues.md

@@ -103,7 +103,7 @@ After creating all issues, create summary with total count and breakdown by seve
 Display: "**Select an Option:** [C] Continue to Step 4: Report"
 
 #### 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]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-t/step-04-report.md

@@ -99,7 +99,7 @@ Organize testing folder with report, screenshots, recordings, and test data.
 Display: "**Select an Option:** [C] Continue to Step 5: Iterate"
 
 #### 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]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/steps-t/step-05-iterate.md

@@ -94,7 +94,7 @@ If after 3 iterations issues persist:
 Display: "**Select an Option:** [M] Return to Activity Menu"
 
 #### Menu Handling Logic:
-- IF M: Update agent dialog, then load, read entire file, then execute {activityWorkflowFile}
+- IF M: Update design log, then load, read entire file, then execute {activityWorkflowFile}
 - IF Any other comments or queries: help user respond then [Redisplay Menu Options]
 
 #### EXECUTION RULES:

package/src/workflows/5-agentic-development/workflow-acceptance-testing.md

@@ -13,11 +13,8 @@ description: Design and run acceptance tests from specification criteria
 
 ## INITIALIZATION
 
-### Agent Dialog Gate
-
-1. Check for pending testing dialogs
-2. If none, suggest creating one with test target
-3. Load dialog context (which delivery/feature to test)
+### Design Log
+Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
 
 ---
 
@@ -40,8 +37,36 @@ Execute steps in `./steps-t/`:
 
 ---
 
+## DESIGN LOG REPORTING POINT
+
+When all tests pass and the user approves, append to the Design Loop Status table in `{output_folder}/_progress/00-design-log.md`:
+
+```
+| [Scenario slug] | [NN.X] | [Page name] | approved | [YYYY-MM-DD] |
+```
+
+Do NOT skip this. The design log drives Phase 4's adaptive dashboard.
+
 ## AFTER COMPLETION
 
-1. Update design log
-2. If approved, suggest handover (Phase 4 [H]) or next iteration
-3. Return to activity menu
+**If all tests pass:**
+
+Design log updated with `approved` status (see above). Present the transition:
+
+<output>
+**"[page name]" is approved!**
+
+1. **Explore the next scenario step** — [next page name]
+2. **Design delivery** — package for development handoff (Phase 4 [H])
+</output>
+
+**If issues found:**
+
+Status stays `built`. Present:
+
+<output>
+**"[page name]" has [N] issues to fix.**
+
+1. **Fix the issues** — route to bugfixing
+2. **Explore the next scenario step** — fix later, continue designing
+</output>

package/src/workflows/5-agentic-development/workflow-analysis.md

@@ -21,11 +21,8 @@ description: Understand an existing codebase through systematic exploration
 
 ## INITIALIZATION
 
-### Agent Dialog Gate
-
-1. Check for pending analysis dialogs
-2. If none, suggest creating one with analysis focus
-3. Load dialog context
+### Design Log
+Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
 
 ### Essential Guides
 
@@ -59,6 +56,6 @@ Execute steps in `./steps-a/`:
 
 ## AFTER COMPLETION
 
-1. Update design log with analysis artifacts
-2. Suggest next action (feed into development? reverse engineer further? start prototyping?)
-3. Return to activity menu
+1. Append a progress entry to `{output_folder}/_progress/00-design-log.md` under `## Progress`:
+   `### [date] — Analysis: [what was analyzed, key findings]`
+2. Suggest next action: feed into development, reverse engineer further, or start prototyping

package/src/workflows/5-agentic-development/workflow-bugfixing.md

@@ -21,11 +21,8 @@ description: Fix bugs in existing code through structured investigation and veri
 
 ## INITIALIZATION
 
-### Agent Dialog Gate
-
-1. Check for pending bugfix dialogs
-2. If none, suggest creating one with bug details
-3. Load dialog context
+### Design Log
+Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
 
 ### Essential Guides
 
@@ -62,6 +59,6 @@ Execute steps in `./steps-f/`:
 
 ## AFTER COMPLETION
 
-1. Update design log
-2. Suggest next action
-3. Return to activity menu
+1. Append a progress entry to `{output_folder}/_progress/00-design-log.md` under `## Progress`:
+   `### [date] — Bugfix: [what was fixed]`
+2. Suggest re-running acceptance testing (Phase 5 [T]) to verify the fix

package/src/workflows/5-agentic-development/workflow-development.md

@@ -51,11 +51,8 @@ Guides in `./data/guides/` support this workflow:
 
 ## INITIALIZATION
 
-### Agent Dialog Gate
-
-1. Check for pending development 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.
 
 ---
 
@@ -73,8 +70,20 @@ Execute steps in `./steps-d/`:
 
 ---
 
+## DESIGN LOG REPORTING POINTS
+
+Append to the Design Loop Status table in `{output_folder}/_progress/00-design-log.md`:
+
+**On entry (step 01 complete):** `| [Scenario slug] | [NN.X] | [Page name] | building | [YYYY-MM-DD] |`
+**On completion (step 05 approved):** `| [Scenario slug] | [NN.X] | [Page name] | built | [YYYY-MM-DD] |`
+
 ## AFTER COMPLETION
 
-1. Update design log
-2. Suggest next action (acceptance testing? handover?)
-3. Return to activity menu
+Design log updated with `built` status (see above). Present the transition:
+
+<output>
+**"[page name]" is built!**
+
+1. **Run acceptance testing** — validate against the specification
+2. **Explore the next scenario step** — [next page name]
+</output>

package/src/workflows/5-agentic-development/workflow-evolution.md

@@ -21,11 +21,8 @@ description: Add features to existing products through targeted changes
 
 ## INITIALIZATION
 
-### Agent Dialog Gate
-
-1. Check for pending evolution 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.
 
 ### Essential Guides
 
@@ -62,6 +59,6 @@ Execute steps in `./steps-e/`:
 
 ## AFTER COMPLETION
 
-1. Update design log
-2. Suggest next action
-3. Return to activity menu
+1. Append a progress entry to `{output_folder}/_progress/00-design-log.md` under `## Progress`:
+   `### [date] — Evolution: [what was evolved/added]`
+2. Suggest acceptance testing (Phase 5 [T]) to validate the changes

package/src/workflows/5-agentic-development/workflow-prototyping.md

@@ -13,11 +13,8 @@ description: Build interactive prototypes from specifications
 
 ## INITIALIZATION
 
-### Agent Dialog Gate
-
-1. Check for pending prototype 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.
 
 ### Essential Guides
 
@@ -59,8 +56,29 @@ Execute steps in `./steps-p/`:
 
 ---
 
+## DESIGN LOG REPORTING POINTS
+
+This workflow has TWO reporting points. Both append to the Design Loop Status table in `{output_folder}/_progress/00-design-log.md`:
+
+**1. On entry (step 1 complete):** Append status `building`
+```
+| [Scenario slug] | [NN.X] | [Page name] | building | [YYYY-MM-DD] |
+```
+
+**2. On completion (step 5 approved):** Append status `built`
+```
+| [Scenario slug] | [NN.X] | [Page name] | built | [YYYY-MM-DD] |
+```
+
+Do NOT skip these updates. The design log drives Phase 4's adaptive dashboard.
+
 ## AFTER COMPLETION
 
-1. Update design log
-2. Suggest next action (handover? next scenario?)
-3. Return to activity menu
+Design log already updated with `built` status (see above). Present the transition:
+
+<output>
+**"[page name]" is built!**
+
+1. **Run acceptance testing** — validate against the specification
+2. **Explore the next scenario step** — [next page name]
+</output>

package/src/workflows/5-agentic-development/workflow-reverse-engineering.md

@@ -25,11 +25,8 @@ description: Analyze any software or website to extract specifications and desig
 
 ## INITIALIZATION
 
-### Agent Dialog Gate
-
-1. Check for pending reverse engineering dialogs
-2. If none, suggest creating one with target description
-3. Load dialog context
+### Design Log
+Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
 
 ### Essential Guides
 
@@ -63,6 +60,6 @@ Execute steps in `./steps-r/`:
 
 ## AFTER COMPLETION
 
-1. Update design log with extracted artifacts
-2. Suggest next action (feed specs into prototyping? analyze further? start development?)
-3. Return to activity menu
+1. Append a progress entry to `{output_folder}/_progress/00-design-log.md` under `## Progress`:
+   `### [date] — Reverse Engineering: [what was extracted]`
+2. Suggest next action: feed specs into prototyping, analyze further, or start development

package/src/workflows/5-agentic-development/workflow.md

@@ -20,7 +20,7 @@ Phase 5 is **menu-driven**, not linear. The user picks an activity.
 
 - **Activity-Based**: Pick the right activity for the current need
 - **Non-Linear**: Start anywhere, switch between activities freely
-- **Agent Dialog Driven**: Every activity creates/resumes agent dialogs for high-level planning
+- **Design Log Driven**: Every activity reads/updates the design log for state tracking
 - **Specification as Truth**: All work traces back to approved specifications
 
 ### Step Processing Rules
@@ -28,7 +28,7 @@ Phase 5 is **menu-driven**, not linear. The user picks an activity.
 1. **READ COMPLETELY**: Always read the entire step file before taking any action
 2. **FOLLOW SEQUENCE**: Execute all sections in order within a step
 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
 
 ---
 
@@ -40,11 +40,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 development dialogs
-2. If pending dialogs exist, present them with status
-3. User can resume existing or start new
+Read `{output_folder}/_progress/00-design-log.md`. Check Current and Backlog for context.
 
 ### 3. Activity Menu
 
@@ -96,5 +94,4 @@ Activity-specific output in project structure.
 
 ## AFTER COMPLETION
 
-1. Update design log
-2. Suggest next action or return to Activity Menu
+Each activity workflow has its own explicit design log reporting points. See the individual workflow files for details on what to log and where.

package/src/workflows/6-asset-generation/data/00-purpose-examples.md

@@ -24,7 +24,7 @@ content_purpose:
 
   model_priorities:
     primary: ["Customer Awareness ⭐⭐⭐", "Golden Circle ⭐⭐⭐"]
-    secondary: ["Badass Users ⭐⭐", "VTC ⭐⭐"]
+    secondary: ["Badass Users ⭐⭐", "Trigger Map ⭐⭐"]
     tertiary: ["Action Mapping ⭐"]
 
   review_question: "Does a Problem Aware hairdresser feel seen and want to learn more?"
@@ -60,7 +60,7 @@ content_purpose:
   model_priorities:
     primary: ["Badass Users ⭐⭐⭐", "Action Mapping ⭐⭐⭐"]
     secondary: ["Customer Awareness ⭐"]
-    tertiary: ["Golden Circle ⭐", "VTC ⭐"]
+    tertiary: ["Golden Circle ⭐", "Trigger Map ⭐"]
 
   review_question: "Can user fix error quickly without feeling frustrated?"
 ```
@@ -92,7 +92,7 @@ content_purpose:
     - "User sees this as competitive advantage worth paying for"
 
   model_priorities:
-    primary: ["VTC ⭐⭐⭐", "Badass Users ⭐⭐"]
+    primary: ["Trigger Map ⭐⭐⭐", "Badass Users ⭐⭐"]
     secondary: ["Action Mapping ⭐⭐", "Customer Awareness ⭐"]
     tertiary: ["Golden Circle ⭐"]
 
@@ -102,7 +102,7 @@ content_purpose:
 **Analysis:**
 - **Comparison context:** User actively evaluating competitors
 - **Value connection:** Not just "3x longer" but "saves money/hassle"
-- **Model priority:** VTC emphasized for understanding driving forces
+- **Model priority:** Trigger Map emphasized for understanding driving forces
 - **Testable:** Can assess if users understand and value the advantage
 
 ---

package/src/workflows/6-asset-generation/data/03-action-filter-example.md

@@ -1,6 +1,6 @@
 # Action Filter Example: Hairdresser Newsletter
 
-**VTC Context:** Hairdresser newsletter signup
+**Trigger Map Context:** Hairdresser newsletter signup
 
 **Action Filter:**
 

package/src/workflows/6-asset-generation/data/04-example-empowerment-frame.md

@@ -1,6 +1,6 @@
 # Example: Badass Users Framework Applied to Hairdresser Newsletter
 
-**VTC Context:** Hairdresser newsletter signup
+**Trigger Map Context:** Hairdresser newsletter signup
 
 **Empowerment Frame:**
 

package/src/workflows/6-asset-generation/data/05-example-golden-circle.md

@@ -1,6 +1,6 @@
 # Example: Golden Circle Applied to Hairdresser Newsletter
 
-**VTC Context:** Hairdresser newsletter signup
+**Trigger Map Context:** Hairdresser newsletter signup
 
 **Structural Order:**
 

package/src/workflows/6-asset-generation/data/05-golden-circle-guide.md

@@ -38,7 +38,7 @@
 - "Sign up now" (jumping to action without motivation)
 
 **Connects to:**
-- User's driving forces (from VTC)
+- User's driving forces (from Trigger Map)
 - Current emotional state (from Empowerment Frame)
 - The problem or aspiration that matters
 

package/src/workflows/6-asset-generation/data/06-example-hairdresser-newsletter.md

@@ -1,6 +1,6 @@
 # Example: Hairdresser Newsletter Signup
 
-**VTC Context:** Hairdresser newsletter signup
+**Trigger Map Context:** Hairdresser newsletter signup
 
 **Content Generations:**
 

package/src/workflows/6-asset-generation/data/06-generation-instructions.md

@@ -7,7 +7,7 @@
 ## 1. Synthesize All Context
 
 Before generating, review and confirm you understand:
-- [ ] WHO the user is and what drives them (VTC)
+- [ ] WHO the user is and what drives them (Trigger Map)
 - [ ] WHERE they are in awareness (START → END)
 - [ ] WHAT action this content must enable (Action Filter)
 - [ ] HOW to make them feel capable (Empowerment Frame)