Treat No-Match and Non-Intervention as Successful Outcomes
The system must not stretch a Compact to fit an uncertain case.
Capture
This ADR should carry the public history of First Response.
Stage 1 — Repair help
The idea began as assistance for things that looked wrong.
Stage 2 — Damage prevention
The stronger value was not repair. It was preventing non-experts from making the problem worse.
Stage 3 — Diagnostic first
The product became primarily about identifying what changed and determining the next judgment owner.
Stage 4 — Before diagnosis
The route moved earlier:
- isolate the environment;
- calm the moment;
- separate the bow;
- clear a surface;
- improve lighting;
- safely receive the violin;
- establish a protected angle;
- only then inspect.
Stage 5 — Protected parent point of view
Existing videos often assume the user already knows how to hold and orient the instrument.
The new content begins before that assumption.
Stage 6 — Full routes versus lightweight media
A full video library for every problem created excessive launch work.
Decision:
- full protected-POV route for action-authorizing cases;
- short voiceover with photos for recognition and handoff;
- text-only where visuals add little.
Stage 7 — Tuning becomes the flagship complete route
Tuning survived because it is:
- common;
- necessary;
- meaningful;
- conditionally safe;
- musically useful;
- risky when mishandled;
- suitable for looping visual instruction.
Stage 8 — Daily ritual rejected
First Response was considered as a daily health ritual.
Why not:
- most days nothing is wrong;
- daily checking could create anxiety;
- it might encourage needless handling;
- it could displace musical progress.
Decision:
First Response remains always visible and event-driven.
Stage 9 — Standalone-first launch considered
Why:
- narrower scope;
- lower reputational risk;
- clear damage-prevention promise;
- easier architecture.
Stage 10 — Standalone-first launch rejected
Why not:
- weak natural daily retention;
- Studio’s scarce guidance would be spent on the easier app;
- it would create another product obligation;
- the same assets already strengthen Stand Partner.
Final role
- First Response is a major protective layer inside Stand Partner.
- It may earn standalone extraction later.
- Actual usage must prove independent demand.
- Decision Tree remains the stronger second standalone daily product.
The system must not stretch a Compact to fit an uncertain case.
Why
This amendment chain is one of the clearest examples of the YY Method being applied to product creation itself.
Why-Not
The rejected path would make treat No-Match and Non-Intervention as Successful Outcomes 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 system must not stretch a Compact to fit an uncertain case.
- preserve the instrument;
- stop manipulation;
- document the concern;
- capture relevant images or audio;
- prepare a teacher or shop message;
- pause playing when appropriate;
- transfer judgment.
Confidence: Medium-high for public architecture; implementation details remain private and subject to launch evidence.
Timestamp
2026-07-17