moveros 4.0.8 → 4.1.0

package/src/workflows/pivot-strategy.md

@@ -1,218 +1,218 @@
----
-description: Formal strategy pivot with logging. Documents old to new strategy with data-driven reason.
----
-
-# Pivot Strategy (V4)
-
-**Trigger:** User runs `/pivot-strategy`
-**Target:** `02_Areas/Engine/Strategy.md`
-**Role:** Strategic Pivot Facilitator.
-**Task:** Formally document and execute a strategy change with data validation.
-**Risk Tier:** HIGH (modifies Engine file)
-
----
-
-## 0. PRE-FLIGHT
-
-Global Rules are pre-loaded as CLAUDE.md / GEMINI.md. Output `[Rules Loaded - DATE]`.
-
-LOAD (Memory Hierarchy):
-1. Auto_Learnings.md (P0)
-2. Active_Context.md (P1)
-3. Strategy.md (P2 - full file, current state)
-4. Identity_Prime.md (P3)
-5. Goals.md (if exists)
-
-PREREQUISITE: Strategy.md must exist. If not: BLOCK. "No Strategy.md found. Run `/setup` first."
-
-CONSTRAINTS:
-- Data-driven pivots only. Emotional pivots flagged as [HYPOTHESIS ONLY].
-- Sample size must be validated before recommending pivot.
-- Append-only: old strategy goes to CHANGELOG, never deleted.
-- Engine file changes require user confirmation (HIGH-RISK).
-- Update Version and Last Updated after changes.
-- Windows: no && in commands.
-
----
-
-## 1. PIVOT VALIDATION
-
-Before pivoting, verify this is data-driven:
-
-"What data supports this pivot?"
-- Did you hit the sample size defined in Strategy.md?
-- What were actual results vs expected?
-
-**If no data:** Flag as `[HYPOTHESIS ONLY]` and warn.
-"You're pivoting without completing the test. This may be emotional, not strategic."
-
-**If under sample:**
-"You're in the Valley of Despair. Are you sure you want to pivot without completing the test? [X]/[Target] of sample completed."
-
-**Cross-reference Auto_Learnings:** Is this a recurring pivot pattern?
-If so: "You've pivoted [X] times in [Y] weeks. Pattern detected (Confidence: [Z])."
-
----
-
-## 2. DOCUMENT CURRENT STATE
-
-Before ANY changes:
-
-1. Capture current strategy: Hypothesis, Vehicle, Metrics, Test Duration.
-2. Log to CHANGELOG:
-```markdown
-## CHANGELOG
-* [YYYY-MM-DD] [Old Strategy] -> [New Strategy]
-* Reason: [Data that validated this OR "HYPOTHESIS ONLY"]
-* Sample Size: [X/Target]
-* Result: [Metric achieved vs target]
-* Duration: [How long was this tested]
-```
-
----
-
-## 3. DEFINE NEW STRATEGY
-
-Ask:
-- "What is the new hypothesis?"
-- "What vehicle/approach will you test?"
-- "What is the new Primary Metric?"
-- "What is the sample size for this test?"
-- "What are the constants (things you won't change while testing)?"
-
-**Challenge the new strategy before accepting it:**
-- If the new hypothesis sounds like the old one reworded: "This looks like the same strategy with different words. What specifically changes in your daily behavior?"
-- If no new metric defined: "A strategy without a metric is a wish. What number tells you this is working?"
-- If sample size is vague ("a few weeks"): "That's not a sample size. How many units (DMs, users, sales, posts) before you evaluate?"
-- If the user can't articulate why this will work when the last one didn't: "What makes you believe THIS will succeed where the last strategy failed? What's structurally different?"
-
-**Do NOT write to Strategy.md yet.** Collect all answers, then proceed to CISC and verification gate.
-
----
-
-## 4. SELF-VERIFICATION (CISC)
-
-Before presenting the verification gate to the user, self-check:
-1. Is the CHANGELOG entry complete and accurate? (90%+ accuracy required)
-2. Is the new strategy grounded in Goals.md and Identity_Prime.md?
-3. Is the pivot flagged [HYPOTHESIS ONLY] if no data was provided?
-4. Are old strategy fields fully captured before any write operation?
-5. Are all constraints from Section 0 met?
-
-If any check < 90% confident: flag it before presenting to user.
-
----
-
-## 5. VERIFICATION GATE (HIGH-RISK)
-
-"I am about to make the following changes to Strategy.md:
-
-OLD:
-- Hypothesis: [Old]
-- Vehicle: [Old]
-- Metric: [Old]
-
-NEW:
-- Hypothesis: [New]
-- Vehicle: [New]
-- Metric: [New]
-
-CHANGELOG entry: [Show entry]
-
-Confirm:
-- Is this accurate?
-- Proceed with writing?"
-
-WAIT FOR USER CONFIRMATION. [Mover_Global_Rules.md: S3, S7, S8]
-
----
-
-## 6. UPDATE STRATEGY.MD
-
-1. Append old strategy to CHANGELOG section (never delete).
-2. Update main sections with new strategy.
-3. Update `**Last Updated:**` field.
-4. Update `**Version:**` (increment by 1).
-
----
-
-## 7. GIT COMMIT
-
-- `git add 02_Areas/Engine/Strategy.md`
-- `git commit -m "pivot(strategy): [Old] -> [New] - [Reason]"`
-- Do NOT use && to chain commands.
-
----
-
-## 8. UPDATE DEPENDENT ENGINE FILES (MANDATORY)
-
-Strategy changes cascade. These updates are required, not optional.
-
-### 8A. Active_Context.md
-Update to reflect the new strategic direction:
-- Section 1 (Strategic Verdict): new model, goal, obstacle, status
-- Section 2 (Graveyard): add the OLD strategy as a killed idea with date and reason for killing
-- Workflow State: write `pivot_strategy_last_run: [YYYY-MM-DD]`
-
-Present proposed changes. WAIT FOR CONFIRMATION. [Mover_Global_Rules.md: S3 HIGH-RISK]
-
-### 8B. Goals.md (if exists)
-Review goals against new strategy. Flag any goals that conflict with the new direction:
-- "Goal [X] was tied to old hypothesis [Y]. Update, keep, or remove?"
-
-Present proposed changes. WAIT FOR CONFIRMATION.
-
-### 8C. Git Commit (Cascade)
-After all dependent updates confirmed:
-- `git add 02_Areas/Engine/Active_Context.md`
-- `git add 02_Areas/Engine/Goals.md` (if changed)
-- `git commit -m "pivot(cascade): update Active_Context + Goals for new strategy"`
-- Do NOT use && to chain commands.
-
----
-
-## 9. PROACTIVE SUGGESTIONS
-
-Based on the pivot:
-1. "Run `/refactor-plan` to update your project plan for the new strategy?"
-2. "Run `/plan-tomorrow` to create a plan aligned with the new strategy?"
-3. If recurring pivot pattern detected: "This is pivot #[X] in [Y] weeks. Consider running `/debug-resistance` to check if this is avoidance."
-
----
-
-## 10. ANSWER GATING
-
-Do not suggest handoff until:
-- User has confirmed the CHANGELOG entry is accurate (Section 5 gate passed).
-- Strategy.md has been written successfully.
-- Active_Context.md updated (Section 8A — mandatory).
-- Goals.md reviewed against new strategy (Section 8B — mandatory if Goals.md exists).
-- All git commits completed (Sections 7 and 8C).
-
-If pending: "Strategy.md hasn't been updated yet. Confirm the changes above or tell me what to adjust."
-
----
-
-## 11. SELF-IMPROVEMENT
-
-If user corrected AI during this workflow:
-1. Acknowledge: "I made a mistake."
-2. Identify the rule violated.
-3. Append to Auto_Learnings.md:
-   `* [YYYY-MM-DD] CORRECTION: [Description]. Source: User correction. Confidence: 3.`
-4. If same correction seen 3x+, escalate confidence to 5.
-
----
-
-## HANDOFF
-
-Sources used: Auto_Learnings.md, Active_Context.md, Strategy.md, Identity_Prime.md, Goals.md (if loaded)
-Confidence range: [X-Y across outputs]
-
-**Next:** "Strategy pivoted and logged. Run `/refactor-plan` to update your project plan, then `/plan-tomorrow` for a new Battle Plan."
-If no active project: "Run `/plan-tomorrow` for a new Battle Plan."
-
-Key rules still active:
-- All claims must be grounded in source files
-- Confidence < 3 = ask, don't assert
-- Append-only: never delete from Strategy.md CHANGELOG
+---
+description: Formal strategy pivot with logging. Documents old to new strategy with data-driven reason.
+---
+
+# Pivot Strategy (V4)
+
+**Trigger:** User runs `/pivot-strategy`
+**Target:** `02_Areas/Engine/Strategy.md`
+**Role:** Strategic Pivot Facilitator.
+**Task:** Formally document and execute a strategy change with data validation.
+**Risk Tier:** HIGH (modifies Engine file)
+
+---
+
+## 0. PRE-FLIGHT
+
+Global Rules are pre-loaded as CLAUDE.md / GEMINI.md. Output `[Rules Loaded - DATE]`.
+
+LOAD (Memory Hierarchy):
+1. Auto_Learnings.md (P0)
+2. Active_Context.md (P1)
+3. Strategy.md (P2 - full file, current state)
+4. Identity_Prime.md (P3)
+5. Goals.md (if exists)
+
+PREREQUISITE: Strategy.md must exist. If not: BLOCK. "No Strategy.md found. Run `/setup` first."
+
+CONSTRAINTS:
+- Data-driven pivots only. Emotional pivots flagged as [HYPOTHESIS ONLY].
+- Sample size must be validated before recommending pivot.
+- Append-only: old strategy goes to CHANGELOG, never deleted.
+- Engine file changes require user confirmation (HIGH-RISK).
+- Update Version and Last Updated after changes.
+- Windows: no && in commands.
+
+---
+
+## 1. PIVOT VALIDATION
+
+Before pivoting, verify this is data-driven:
+
+"What data supports this pivot?"
+- Did you hit the sample size defined in Strategy.md?
+- What were actual results vs expected?
+
+**If no data:** Flag as `[HYPOTHESIS ONLY]` and warn.
+"You're pivoting without completing the test. This may be emotional, not strategic."
+
+**If under sample:**
+"You're in the Valley of Despair. Are you sure you want to pivot without completing the test? [X]/[Target] of sample completed."
+
+**Cross-reference Auto_Learnings:** Is this a recurring pivot pattern?
+If so: "You've pivoted [X] times in [Y] weeks. Pattern detected (Confidence: [Z])."
+
+---
+
+## 2. DOCUMENT CURRENT STATE
+
+Before ANY changes:
+
+1. Capture current strategy: Hypothesis, Vehicle, Metrics, Test Duration.
+2. Log to CHANGELOG:
+```markdown
+## CHANGELOG
+* [YYYY-MM-DD] [Old Strategy] -> [New Strategy]
+* Reason: [Data that validated this OR "HYPOTHESIS ONLY"]
+* Sample Size: [X/Target]
+* Result: [Metric achieved vs target]
+* Duration: [How long was this tested]
+```
+
+---
+
+## 3. DEFINE NEW STRATEGY
+
+Ask:
+- "What is the new hypothesis?"
+- "What vehicle/approach will you test?"
+- "What is the new Primary Metric?"
+- "What is the sample size for this test?"
+- "What are the constants (things you won't change while testing)?"
+
+**Challenge the new strategy before accepting it:**
+- If the new hypothesis sounds like the old one reworded: "This looks like the same strategy with different words. What specifically changes in your daily behavior?"
+- If no new metric defined: "A strategy without a metric is a wish. What number tells you this is working?"
+- If sample size is vague ("a few weeks"): "That's not a sample size. How many units (DMs, users, sales, posts) before you evaluate?"
+- If the user can't articulate why this will work when the last one didn't: "What makes you believe THIS will succeed where the last strategy failed? What's structurally different?"
+
+**Do NOT write to Strategy.md yet.** Collect all answers, then proceed to CISC and verification gate.
+
+---
+
+## 4. SELF-VERIFICATION (CISC)
+
+Before presenting the verification gate to the user, self-check:
+1. Is the CHANGELOG entry complete and accurate? (90%+ accuracy required)
+2. Is the new strategy grounded in Goals.md and Identity_Prime.md?
+3. Is the pivot flagged [HYPOTHESIS ONLY] if no data was provided?
+4. Are old strategy fields fully captured before any write operation?
+5. Are all constraints from Section 0 met?
+
+If any check < 90% confident: flag it before presenting to user.
+
+---
+
+## 5. VERIFICATION GATE (HIGH-RISK)
+
+"I am about to make the following changes to Strategy.md:
+
+OLD:
+- Hypothesis: [Old]
+- Vehicle: [Old]
+- Metric: [Old]
+
+NEW:
+- Hypothesis: [New]
+- Vehicle: [New]
+- Metric: [New]
+
+CHANGELOG entry: [Show entry]
+
+Confirm:
+- Is this accurate?
+- Proceed with writing?"
+
+WAIT FOR USER CONFIRMATION. [Mover_Global_Rules.md: S3, S7, S8]
+
+---
+
+## 6. UPDATE STRATEGY.MD
+
+1. Append old strategy to CHANGELOG section (never delete).
+2. Update main sections with new strategy.
+3. Update `**Last Updated:**` field.
+4. Update `**Version:**` (increment by 1).
+
+---
+
+## 7. GIT COMMIT
+
+- `git add 02_Areas/Engine/Strategy.md`
+- `git commit -m "pivot(strategy): [Old] -> [New] - [Reason]"`
+- Do NOT use && to chain commands.
+
+---
+
+## 8. UPDATE DEPENDENT ENGINE FILES (MANDATORY)
+
+Strategy changes cascade. These updates are required, not optional.
+
+### 8A. Active_Context.md
+Update to reflect the new strategic direction:
+- Section 1 (Strategic Verdict): new model, goal, obstacle, status
+- Section 2 (Graveyard): add the OLD strategy as a killed idea with date and reason for killing
+- Workflow State: write `pivot_strategy_last_run: [YYYY-MM-DD]`
+
+Present proposed changes. WAIT FOR CONFIRMATION. [Mover_Global_Rules.md: S3 HIGH-RISK]
+
+### 8B. Goals.md (if exists)
+Review goals against new strategy. Flag any goals that conflict with the new direction:
+- "Goal [X] was tied to old hypothesis [Y]. Update, keep, or remove?"
+
+Present proposed changes. WAIT FOR CONFIRMATION.
+
+### 8C. Git Commit (Cascade)
+After all dependent updates confirmed:
+- `git add 02_Areas/Engine/Active_Context.md`
+- `git add 02_Areas/Engine/Goals.md` (if changed)
+- `git commit -m "pivot(cascade): update Active_Context + Goals for new strategy"`
+- Do NOT use && to chain commands.
+
+---
+
+## 9. PROACTIVE SUGGESTIONS
+
+Based on the pivot:
+1. "Run `/refactor-plan` to update your project plan for the new strategy?"
+2. "Run `/plan-tomorrow` to create a plan aligned with the new strategy?"
+3. If recurring pivot pattern detected: "This is pivot #[X] in [Y] weeks. Consider running `/debug-resistance` to check if this is avoidance."
+
+---
+
+## 10. ANSWER GATING
+
+Do not suggest handoff until:
+- User has confirmed the CHANGELOG entry is accurate (Section 5 gate passed).
+- Strategy.md has been written successfully.
+- Active_Context.md updated (Section 8A — mandatory).
+- Goals.md reviewed against new strategy (Section 8B — mandatory if Goals.md exists).
+- All git commits completed (Sections 7 and 8C).
+
+If pending: "Strategy.md hasn't been updated yet. Confirm the changes above or tell me what to adjust."
+
+---
+
+## 11. SELF-IMPROVEMENT
+
+If user corrected AI during this workflow:
+1. Acknowledge: "I made a mistake."
+2. Identify the rule violated.
+3. Append to Auto_Learnings.md:
+   `* [YYYY-MM-DD] CORRECTION: [Description]. Source: User correction. Confidence: 3.`
+4. If same correction seen 3x+, escalate confidence to 5.
+
+---
+
+## HANDOFF
+
+Sources used: Auto_Learnings.md, Active_Context.md, Strategy.md, Identity_Prime.md, Goals.md (if loaded)
+Confidence range: [X-Y across outputs]
+
+**Next:** "Strategy pivoted and logged. Run `/refactor-plan` to update your project plan, then `/plan-tomorrow` for a new Battle Plan."
+If no active project: "Run `/plan-tomorrow` for a new Battle Plan."
+
+Key rules still active:
+- All claims must be grounded in source files
+- Confidence < 3 = ask, don't assert
+- Append-only: never delete from Strategy.md CHANGELOG