Translate the Five-Step Method Into Natural Violin Behavior

Capture

• Capture → What did you hear, feel, or notice?
• Why → Why does this matter now?
• Why-Not → What makes the first explanation incomplete?
• Commit → What is the smallest next experiment or handoff?
• Timestamp → When should this be reviewed again?

The app is governed by:

• Capture;
• Why;
• Why-Not;
• Commit;
• Timestamp.

But users do not need to recite the formal labels in every interaction.

Why

This decision matters because translate the Five-Step Method Into Natural Violin Behavior constrains the product toward continuity, evidence, and human judgment rather than broad AI helpfulness.

Why-Not

The rejected path would make translate the Five-Step Method Into Natural Violin Behavior too easy to treat as an implementation detail instead of a public boundary. The ADR preserves the tradeoff explicitly so later product work cannot silently widen authority.

Commit

Decision: The app is governed by:

• Capture;
• Why;
• Why-Not;
• Commit;
• Timestamp.

But users do not need to recite the formal labels in every interaction.

The decision becomes a constraint on future product behavior and public positioning.

Confidence: Medium-high for public architecture; implementation details remain private and subject to launch evidence.

Timestamp

2026-07-17