strat-unique-mechanism

name	strat-unique-mechanism
description	Defines the unique mechanism that explains why the offer works differently from the old way. Use after product-offer and before MVP scope.

Unique Mechanism

Explain why the solution works in a way the old way does not.

Workflow

1. Load ../_shared/references/strategy.md, ../_shared/references/artifact-conventions.md, and ../_shared/references/quality-gates.md.
2. Read .ai/strategy/signal/* and .ai/strategy/offer/product-offer.md.
3. Identify the old way, why it fails, the new way, mechanism type, mechanism name, steps, proof hooks, and metaphor.
4. Include a concise comparison table: Old Way vs New Way.
5. Prefer concrete mechanisms such as process, technical, workflow, constraint, delivery, community, or educational mechanisms.
6. Save .ai/strategy/offer/unique-mechanism.md.

Output template

# Unique Mechanism

## Old Way

## Why The Old Way Fails

## New Way

## Mechanism Name

## Mechanism Summary

## Steps

Use 3 to 7 steps.

1.
2.
3.

## Why It Works

## Proof Hooks

## Visual Metaphor

## Mechanism One-Liner

## Risks

## Assumptions

## Open Questions

Quality bar

Avoid vague mechanisms like "we use AI to accelerate". Prefer concrete pipelines such as "Signal → Offer → MVP → Page".

Output quality checklist

• Old way failure is concrete.
• New way is operational, not slogan.
• Mechanism has a name and 3–7 steps.
• Proof hooks are listed.
• Old vs New comparison is included.

Critical rules

• Do not create MVP scope before mechanism clarity.
• Do not create downstream deliverables or implementation code.