Promote “Stand Partner” From Behavior to Product Identity

Capture

Potential identities included concepts such as:

• Violin Companion;
• Between Lessons;
• Violin Coach;
• Stand Partner;
• page-turning companion;
• memory or practice partner.

“Stand Partner” initially functioned as a description of how the AI should behave.

It later became strong enough to carry the product.

Adopt Violin Stand Partner as the product name and organizing relationship.

Why

• it is native to the violin domain;

• it describes relationship rather than authority;

• it implies proximity and continuity;

• it respects ensemble culture;

• it supports the broader Benchantech “stand” motif;

• it can mean both standing beside and withstanding judgment.

• “Companion” was generic;

• “Coach” implied broad authority;

• “Between Lessons” described timing but not relationship;

• “Practice” narrowed the product too much;

• “AI” in the title foregrounded the mechanism instead of the trust model.

Why-Not

• “Companion” was generic;

• “Coach” implied broad authority;

• “Between Lessons” described timing but not relationship;

• “Practice” narrowed the product too much;

• “AI” in the title foregrounded the mechanism instead of the trust model.

• trademark strategy;

• domain acquisition plan;

• unannounced naming tests;

• internal launch naming variants.

---

Commit

Decision: Adopt Violin Stand Partner as the product name and organizing relationship.

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

Public boundary: This ADR publishes the judgment and product boundary while withholding exact prompts, routes, thresholds, schemas, tests, and other reproducible implementation details where applicable.

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

Timestamp

2026-07-17