whiteport-design-studio 0.2.2 → 0.3.0

package/src/workflows/1-project-brief/vtc-workshop/steps-c/step-05b-define-solution.md

@@ -1,117 +0,0 @@
----
-name: 'step-05b-define-solution'
-description: 'Define what solution is being built - NOT in Trigger Map, solutions stay out of map'
-
-# File References
-nextStepFile: './step-06b-customer-awareness.md'
-workflowFile: '../../workflow.md'
-activityWorkflowFile: '../workflow.md'
----
-
-# Step 5: Define Solution
-
-## STEP GOAL:
-Define what we're building - solutions are NOT in the Trigger Map, they are defined per VTC as the bridge between business goal and user.
-
-## 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 Business Analyst facilitating VTC selection from an existing Trigger Map
-- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
-- We engage in collaborative dialogue, not command-response
-- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
-- Maintain collaborative and strategic tone throughout
-
-### Step-Specific Rules:
-- Focus: Specific solution definition, test connection to map elements
-- FORBIDDEN: Do not accept vague solution descriptions
-- Approach: Ask, apply guidelines, test chain connection, validate
-
-## EXECUTION PROTOCOLS:
-- Primary goal: Solution defined and validated against map elements
-- Save/document outputs appropriately
-- Avoid generating content without user input
-
-## CONTEXT BOUNDARIES:
-- Available context: Trigger Map, selected goal, user, forces from steps 1-4
-- Focus: Solution definition (new element, not from map)
-- Limits: Specific, focused, user-facing
-- Dependencies: Step 04b completed
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Ask for Solution
-
-> "What solution are you building to serve this VTC?"
-
-**Reminder:** This is the bridge between business goal and user.
-
-### 2. Apply Guidelines
-
-Same as Creation Workshop - specific about WHAT this is:
-
-**Good examples:**
-- "Landing page with newsletter signup"
-- "Onboarding flow for new users"
-- "User profile settings page"
-
-**Bad examples:**
-- "A great experience" (too vague)
-- "Lots of features" (not specific)
-
-### 3. Capture Format
-
-```yaml
-solution: "[Specific solution being built]"
-```
-
-### 4. Test Connection
-
-Business Goal (from map) -> Solution (new) -> User (from map) -> Forces (from map)
-
-Does this chain make sense?
-
-### 5. Validation
-
-- [ ] Solution is specific?
-- [ ] Solution serves selected business goal?
-- [ ] Solution connects to selected user and forces?
-
-### N. Present MENU OPTIONS
-Display: "**Select an Option:** [C] Continue to next step"
-
-#### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
-- IF M: Return to {workflowFile} or {activityWorkflowFile}
-- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
-
-#### EXECUTION RULES:
-- ALWAYS halt and wait for user input after presenting menu
-- User can chat or ask questions - always respond and then redisplay menu options
-
-## CRITICAL STEP COMPLETION NOTE
-ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
-
----
-
-## SYSTEM SUCCESS/FAILURE METRICS
-
-### SUCCESS:
-- Specific solution defined
-- Chain connection tested (goal -> solution -> user -> forces)
-- User confirmed the solution
-- Solution bridges business goal and user
-
-### FAILURE:
-- Accepted vague solution description
-- Skipped chain connection test
-- Generated solution without user input
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/workflows/1-project-brief/vtc-workshop/steps-c/step-06a-customer-awareness.md

@@ -1,216 +0,0 @@
----
-name: 'step-06a-customer-awareness'
-description: 'Define where user starts and where we move them in their awareness journey'
-
-# File References
-nextStepFile: './step-07a-review-and-save.md'
-workflowFile: '../../workflow.md'
-activityWorkflowFile: '../workflow.md'
----
-
-# Step 6: Position Customer Awareness
-
-## STEP GOAL:
-Define where user starts and where we move them in their awareness journey - explore what the user knows NOW, and what transformation we want to create.
-
-## 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 Business Analyst facilitating VTC creation from scratch
-- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
-- We engage in collaborative dialogue, not command-response
-- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
-- Maintain collaborative and strategic tone throughout
-
-### Step-Specific Rules:
-- Focus: Customer awareness start and end positions with realistic progression
-- FORBIDDEN: Do not skip validating realistic progression (usually 1-2 stages)
-- Approach: Explore current state, define transformation, validate realistic progression, storytelling validation
-
-## EXECUTION PROTOCOLS:
-- Primary goal: Customer awareness journey defined and validated
-- Save/document outputs appropriately
-- Avoid generating content without user input
-
-## CONTEXT BOUNDARIES:
-- Available context: Business goal, solution, user, driving forces from steps 1-5
-- Focus: Customer awareness positioning
-- Limits: Realistic progression, usually 1-2 stages
-- Dependencies: Step 05a completed
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Understand Current State (6A)
-
-**Start with exploration:**
-
-> "Let's understand where [user name] is right now. When they encounter [solution], what's going on in their head?"
-
-**Ask progressively:**
-
-**"Do they know something's wrong?"**
-- If NO: "Interesting - so they don't even realize there's a problem yet. What would make them suddenly notice?" -> Starting at **Unaware**
-- If YES: "Okay, they know something's not working. Tell me more about that..."
-
-**"What language are they using?"**
-> "When they talk about this problem - to themselves or others - what words do they use?"
-
-**Listen for:**
-- Generic problem language -> **Problem Aware**
-- Comparing solutions -> **Solution Aware**
-- Mentioning your product -> **Product Aware**
-- Sharing their experience -> **Most Aware**
-
-**"What are they looking for?"**
-> "If they're searching for help, what would they type into Google?"
-
-**Examples show awareness:**
-- "how to fix [problem]" -> Problem Aware
-- "best tools for [need]" -> Solution Aware
-- "[your product name] review" -> Product Aware
-
-**"Have they tried anything?"**
-> "Are they already trying other solutions? Or still figuring out if solutions exist?"
-
-**Reveals:**
-- Never tried anything -> Problem Aware
-- Tried competitors -> Solution Aware
-- Using your free version -> Product Aware
-- Paying customer -> Most Aware
-
-**Capture their current position:**
-
-```yaml
-customer_awareness:
-  start: "[One of: Unaware / Problem Aware / Solution Aware / Product Aware / Most Aware]"
-  start_context: "[What they know, what they're looking for, language they use]"
-```
-
-**The 5 stages:** Unaware -> Problem Aware -> Solution Aware -> Product Aware -> Most Aware
-
-### 2. Define Desired Transformation (6B)
-
-> "After they interact with [solution], what should change in their understanding?"
-
-**"What will they realize?"**
-> "What new insight or understanding will they gain?"
-
-**"What will they be able to articulate?"**
-> "After this experience, if they told a friend about it, what would they say?"
-
-**"What action becomes possible?"**
-> "What can they do NOW that they couldn't before?"
-
-**Actions show awareness level:**
-- Admit problem -> Problem Aware
-- Compare solutions -> Solution Aware
-- Try your product -> Product Aware
-- Recommend it -> Most Aware
-
-### 3. Validate Realistic Progression (6C)
-
-> "So they're starting at [start stage]. Where's realistic to move them with [this solution]?"
-
-**Important:** Usually move 1-2 stages, not jumping from Unaware -> Most Aware
-
-**Guide with questions:**
-- "Is this a quick interaction or deep engagement?"
-- "Will they actually USE it, or just learn about it?"
-- "What's preventing bigger jump?"
-
-**Capture:**
-
-```yaml
-customer_awareness:
-  start: "[Current stage]"
-  start_context: "[What they know/feel NOW]"
-  end: "[Target stage]"
-  end_context: "[What they'll know/feel AFTER]"
-  transformation: "[Key shift that happens]"
-```
-
-### 4. Validation Through Storytelling
-
-**Ask user to tell the story:**
-
-> "Walk me through their awareness journey: They start knowing what? -> They encounter this solution -> They realize what? -> They end up able to do what?"
-
-**Listen for:** Coherent narrative, Realistic transformation, Matches driving forces, Supports business goal
-
-**If story doesn't flow** - one of the stages is wrong.
-
-### 5. Common Patterns Reference
-
-| Context | Typical Journey |
-|---------|-----------------|
-| **Landing Pages** | Problem/Solution -> Product Aware |
-| **Onboarding** | Product -> Most Aware |
-| **Educational Content** | Unaware -> Problem Aware |
-| **Feature Announcements** | Most Aware -> Most Aware (deepen) |
-
-### 6. Handle Common Issues
-
-**Issue:** User wants to jump multiple stages
-> "That's the ultimate goal, but THIS interaction likely moves them 1-2 stages. What's the next realistic step?"
-
-**Issue:** User not sure about stages
-> "Let's think about it this way: What do they know BEFORE? What should they know AFTER?"
-
-**Issue:** Starting and ending are the same stage
-> "If awareness doesn't change, what IS changing? Maybe we're maintaining Most Aware, or maybe the starting point needs adjustment?"
-
-### 7. How This Guides Design
-
-**Content Strategy:**
-- **Start stage** -> what language to use (theirs, not yours)
-- **End stage** -> what message to deliver (the transformation)
-- **Gap between** -> how much explanation needed
-
-**Tone:** Earlier = exploratory, educational | Later = direct, action-oriented
-
-**Depth:**
-- Unaware: Need context (why should I care?)
-- Problem Aware: Need options (what solves this?)
-- Solution Aware: Need differentiation (why yours?)
-- Product Aware: Need proof (does it work?)
-- Most Aware: Need expansion (what else?)
-
-### N. Present MENU OPTIONS
-Display: "**Select an Option:** [C] Continue to next step"
-
-#### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
-- IF M: Return to {workflowFile} or {activityWorkflowFile}
-- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
-
-#### EXECUTION RULES:
-- ALWAYS halt and wait for user input after presenting menu
-- User can chat or ask questions - always respond and then redisplay menu options
-
-## CRITICAL STEP COMPLETION NOTE
-ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
-
----
-
-## SYSTEM SUCCESS/FAILURE METRICS
-
-### SUCCESS:
-- Customer awareness start and end defined
-- Progression is realistic (1-2 stages)
-- Storytelling validation passed
-- Transformation is clear and actionable
-- User confirmed the awareness journey
-
-### FAILURE:
-- Skipped realistic progression validation
-- Accepted unrealistic stage jumps without questioning
-- Generated awareness positions without user input
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/workflows/1-project-brief/vtc-workshop/steps-c/step-06b-customer-awareness.md

@@ -1,123 +0,0 @@
----
-name: 'step-06b-customer-awareness'
-description: 'Define awareness start/end - typically NOT in Trigger Map, defined per scenario'
-
-# File References
-nextStepFile: './step-07b-review-and-save.md'
-workflowFile: '../../workflow.md'
-activityWorkflowFile: '../workflow.md'
----
-
-# Step 6: Position Customer Awareness
-
-## STEP GOAL:
-Define awareness start/end positions - typically NOT in the Trigger Map, defined per scenario. Explore what user knows NOW and what transformation happens.
-
-## 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 Business Analyst facilitating VTC selection from an existing Trigger Map
-- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
-- We engage in collaborative dialogue, not command-response
-- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
-- Maintain collaborative and strategic tone throughout
-
-### Step-Specific Rules:
-- Focus: Customer awareness start and end with context, realistic progression
-- FORBIDDEN: Do not skip storytelling validation of the awareness journey
-- Approach: Use same exploratory approach as Creation Workshop, capture with context, validate through story
-
-## EXECUTION PROTOCOLS:
-- Primary goal: Customer awareness journey defined and validated
-- Save/document outputs appropriately
-- Avoid generating content without user input
-
-## CONTEXT BOUNDARIES:
-- Available context: Trigger Map, selected goal, user, forces, solution from steps 1-5
-- Focus: Customer awareness positioning (new element, not from map)
-- Limits: Realistic progression, usually 1-2 stages
-- Dependencies: Step 05b completed
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Quick Exploration Questions
-
-**Current State:**
-
-1. **"Do they know something's wrong?"**
-2. **"What language are they using?"** (when talking about this)
-3. **"What are they looking for?"** (search terms, questions)
-4. **"Have they tried anything?"** (your product, competitors, nothing)
-
-**Desired Transformation:**
-
-1. **"What will they realize?"** (new insight)
-2. **"What will they be able to articulate?"** (to a friend)
-3. **"What action becomes possible?"** (what can they DO now)
-
-### 2. Capture with Context
-
-```yaml
-customer_awareness:
-  start: "[Stage]"
-  start_context: "[What they know/feel NOW]"
-  end: "[Stage]"
-  end_context: "[What they'll know/feel AFTER]"
-  transformation: "[Key shift that happens]"
-```
-
-**Example:**
-```yaml
-customer_awareness:
-  start: "Solution Aware"
-  start_context: "Researching design tools, overwhelmed by options"
-  end: "Product Aware"
-  end_context: "Knows WDS exists, understands it's agent-based, considering trial"
-  transformation: "From 'tools are complex' to 'this specific approach might work'"
-```
-
-### 3. Validate Through Story
-
-**Ask user:**
-> "Walk me through their awareness journey in this scenario."
-
-Story should flow naturally and match the selected driving forces from Trigger Map.
-
-### N. Present MENU OPTIONS
-Display: "**Select an Option:** [C] Continue to next step"
-
-#### Menu Handling Logic:
-- IF C: Update agent dialog, then load, read entire file, then execute {nextStepFile}
-- IF M: Return to {workflowFile} or {activityWorkflowFile}
-- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
-
-#### EXECUTION RULES:
-- ALWAYS halt and wait for user input after presenting menu
-- User can chat or ask questions - always respond and then redisplay menu options
-
-## CRITICAL STEP COMPLETION NOTE
-ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
-
----
-
-## SYSTEM SUCCESS/FAILURE METRICS
-
-### SUCCESS:
-- Customer awareness start and end defined with context
-- Transformation clearly articulated
-- Storytelling validation passed
-- Journey matches selected driving forces
-
-### FAILURE:
-- Skipped storytelling validation
-- Defined positions without context
-- Generated awareness positions without user input
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.

package/src/workflows/1-project-brief/vtc-workshop/steps-c/step-07a-review-and-save.md

@@ -1,250 +0,0 @@
----
-name: 'step-07a-review-and-save'
-description: 'Validate completeness and save the VTC - final step of Creation Workshop'
-
-# File References
-workflowFile: '../../workflow.md'
-activityWorkflowFile: '../workflow.md'
----
-
-# Step 7: Review and Save VTC
-
-## STEP GOAL:
-Validate completeness and save the VTC for use - review the complete VTC for coherence, then save it to the appropriate location.
-
-## 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 Business Analyst completing the VTC Creation Workshop
-- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
-- We engage in collaborative dialogue, not command-response
-- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
-- Maintain collaborative and strategic tone throughout
-
-### Step-Specific Rules:
-- Focus: Read back complete VTC, validate with 4 questions, refine if needed, determine save location, save
-- FORBIDDEN: Do not skip any of the 4 validation questions
-- Approach: Present VTC, validate coherence/actionability/specificity/realism, refine, save, communicate
-
-## EXECUTION PROTOCOLS:
-- Primary goal: VTC validated, saved, and user understands what they have
-- Save/document outputs appropriately
-- Avoid generating content without user input
-
-## CONTEXT BOUNDARIES:
-- Available context: All VTC elements from steps 1-6
-- Focus: Review, validation, and save
-- Limits: Finalizing, not starting new work
-- Dependencies: Steps 01a-06a completed
-
-## Sequence of Instructions (Do not deviate, skip, or optimize)
-
-### 1. Read Back Complete VTC (7A)
-
-**Present the full VTC to user:**
-
-```yaml
-vtc:
-  business_goal: "[goal]"
-  solution: "[solution]"
-  user:
-    name: "[name]"
-    description: "[description]"
-    context: "[context]"
-  driving_forces:
-    positive:
-      - "[wish 1]"
-      - "[wish 2]"
-    negative:
-      - "[fear 1]"
-      - "[fear 2]"
-  customer_awareness:
-    start: "[start stage]"
-    end: "[end stage]"
-```
-
-### 2. Validate with Questions (7B)
-
-**Ask each validation question:**
-
-**Coherence:**
-> "Does this tell a coherent story?"
-- Business goal -> Solution -> User -> Forces -> Awareness
-- Does it flow logically?
-- Does each piece connect to the others?
-
-**Actionable:**
-> "Can you make design decisions from this?"
-- Specific enough to guide choices?
-- Clear what would/wouldn't serve this VTC?
-- Could someone else use this?
-
-**Specific:**
-> "Are the driving forces specific enough?"
-- Go beyond generic?
-- Emotionally resonant?
-- Different from other users?
-
-**Realistic:**
-> "Does the awareness progression make sense?"
-- Can solution realistically move user that far?
-- Appropriate for this interaction type?
-- Supports business goal?
-
-**All YES?** -> VTC is ready to save
-**Any NO?** -> Refine that specific element
-
-### 3. Quick Refinement (7C) - if needed
-
-**If any validation failed:**
-
-1. Identify which element needs work
-2. Return to that step briefly
-3. Make adjustment
-4. Re-validate
-
-**Keep momentum** - don't get stuck perfecting. "Good enough to guide design" is the bar.
-
-### 4. Determine Save Location (7D)
-
-**Ask:**
-> "What is this VTC for?"
-
-**If Product Pitch:**
-- Location: `{output_folder}/A-Product-Brief/vtc-primary.yaml`
-- Purpose: Stakeholder communication, strategic alignment
-
-**If Scenario:**
-- Location: `{output_folder}/C-UX-Scenarios/[scenario-name]/vtc.yaml`
-- Purpose: Guide scenario design decisions
-
-**If Prototype/Other:**
-- Location: `{output_folder}/[appropriate-folder]/vtc-[name].yaml`
-- Purpose: As defined by user
-
-### 5. Create VTC File (7E)
-
-**Use template:** Copy from `../../templates/vtc-template.yaml`
-
-**Fill in all sections:**
-
-```yaml
-vtc:
-  business_goal: "[captured value]"
-  solution: "[captured value]"
-  user:
-    name: "[captured value]"
-    description: "[captured value]"
-    context: "[captured value]"
-  driving_forces:
-    positive: [captured values]
-    negative: [captured values]
-  customer_awareness:
-    start: "[captured value]"
-    end: "[captured value]"
-
-metadata:
-  created_date: "[today's date]"
-  created_by: "[team/person]"
-  version: "1.0"
-  source: "creation"
-  purpose: "[product_pitch / scenario / etc]"
-  phase: "[WDS phase]"
-
-notes: |
-  Created: [date]
-  Context: [why this VTC was created]
-
-  Key decisions made:
-  - [Important choices during workshop]
-  - [Insights captured]
-
-  Usage guidance:
-  - [How this VTC should inform design]
-```
-
-**Save file to determined location**
-
-### 6. Communicate What They Have (7F)
-
-**Explain to user:**
-
-> "Excellent! We've created a Value Trigger Chain that shows:
->
-> **Business Goal:** [goal]
-> **User:** [name] who wants to [positive force] and avoid [negative force]
-> **Solution:** [solution] that moves them from [start] to [end] awareness
->
-> This VTC will guide all design decisions for [context]. Every piece of content, every interaction, every design choice should serve this strategic chain.
->
-> **Next time you're making a design decision, ask:**
-> 'Does this serve the business goal by triggering these driving forces while moving the user forward in awareness?'
->
-> If yes -> Good decision
-> If no -> Reconsider"
-
-### 7. Define Next Actions (7G)
-
-**If Product Pitch:**
-> "Next steps:
-> 1. Add this VTC to your pitch document
-> 2. Structure pitch narrative around this chain
-> 3. Use it to explain strategic reasoning to stakeholders
-> 4. Can evolve into full Trigger Map later as project grows"
-
-**If Scenario:**
-> "Next steps:
-> 1. Use this VTC to guide page design in this scenario
-> 2. All content should address these driving forces
-> 3. Track if you're actually moving users through awareness
-> 4. Create additional VTCs for other scenarios as needed"
-
-### 8. Completion Checklist
-
-- [ ] VTC validated with all 4 questions
-- [ ] VTC saved to appropriate location
-- [ ] Metadata completed (date, source, purpose)
-- [ ] Notes section filled with context
-- [ ] User understands what they have
-- [ ] User knows how to use VTC
-- [ ] Next actions defined
-
-### N. Present MENU OPTIONS
-Display: "**Select an Option:** [M] Return to workflow menu"
-
-#### Menu Handling Logic:
-- IF M: Return to {workflowFile} or {activityWorkflowFile}
-- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
-
-#### EXECUTION RULES:
-- ALWAYS halt and wait for user input after presenting menu
-- User can chat or ask questions - always respond and then redisplay menu options
-
-## CRITICAL STEP COMPLETION NOTE
-This is the FINAL step of the VTC Creation Workshop. Workshop is complete.
-
----
-
-## SYSTEM SUCCESS/FAILURE METRICS
-
-### SUCCESS:
-- Complete VTC presented and validated
-- All 4 validation questions answered YES
-- VTC saved to correct location with metadata
-- User understands what they have and how to use it
-- Next actions defined
-
-### FAILURE:
-- Skipped validation questions
-- Saved without metadata or notes
-- Did not communicate value to user
-- Left user without clear next actions
-
-**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.