Saved on device

Evidence discipline

Mechanisms over mythology.

Every product claim separates established evidence, plausible interpretation, and what STACKS is testing for one person.

What we know

Directly supported findings, described without decoration.

What may be happening

Mechanism-level interpretation, labeled as interpretation.

What STACKS tests

Personal descriptive evidence that can outrank generic defaults over time.

Implementation intentions

Evidence A

Know

Specific if–then plans can improve follow-through in relevant settings.

Think

They reduce repeated decision-making when the anticipated cue appears.

Test

Which failure cue and response are useful for this person and Stack?

Minimum contracts

Evidence B

Know

Smaller entry commitments reduce the amount of behavior required before someone can honestly say they started.

Think

The permission to stop may reduce perceived effort before action.

Test

Whether reaching the minimum increases continuation for this person.

External attention

Evidence B

Know

Task-relevant external focus is supported in many performance settings.

Think

It may reduce unhelpful self-monitoring before precise or social action.

Test

Whether outward cues shorten latency or improve process scores in a specific context.

Performer routines

Evidence C

Know

Many performers use repeatable pre-performance sequences.

Think

Their value depends on function, context, and flexibility—not fame or repetition alone.

Test

Whether a transferred mechanism helps without becoming a dependency.

Excluded as foundations

Lucky charms, power-pose hormone claims, arbitrary ritual claims built on retracted evidence, outcome-only fantasy, precise dopamine-spike claims, universal habit timelines, and universal optimal-arousal levels do not justify product behavior.