# Write the upgrade trigger before shopping

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Write the upgrade trigger before shopping

ID: MHC-D-RESEARCH-9056 · Version: 0.1.0 · Kind: template
Source: https://vedokrok.com/knowledge/write-the-upgrade-trigger-before-shopping

Shopping first makes the new product define the problem for you.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- You are browsing replacements before the current item has a clear failure or capability gap.

### Avoid when

- Unexpected failure, safety issues or a genuinely new requirement can invalidate the trigger. Revise it when the job changes.

### Explanation

Write the event that would make replacement rational before reading product pages. Good triggers are observable: support ends, repairs cross a chosen threshold, a required workload misses a target, downtime becomes unacceptable, fit cannot be corrected, or a needed capability is absent. Then define a keep condition for the current item and a reject condition for the new one. The trigger protects against novelty-driven upgrades while still allowing an early replacement when reliability or support risk is real.

### Template

Replace when [observable trigger]. Keep the current item while [acceptable state]. New item must improve [named requirement]. Reject the upgrade if [trade-off or failure]. Review again on [date/event].

### Example

Replace the phone when security support ends or the battery/repair path no longer sustains a full workday—not when a new camera generation appears.

### Check

The replacement decision can be triggered without seeing a specific new model or advertisement.

### Limits

- Unexpected failure, safety issues or a genuinely new requirement can invalidate the trigger. Revise it when the job changes.

### Evidence and sources

- supports: FTC consumer guidance recommends researching a product's expected life, what is likely to break and how difficult repairs may be before purchase. — RS-E143967DDAA5BB73. This is general consumer guidance, not evidence that repairability should outweigh every other requirement. (Consumer buying advice)
- supports: Current EU smartphone and tablet ecodesign rules make longevity factors such as battery durability, spare-parts availability, repairability information and operating-system support explicit product attributes. — RS-EA8E2EA9D7970C00. The rule applies to covered EU products and does not mean every compliant device will have the same real-world service life. (Ecodesign requirements)
- RS-E143967DDAA5BB73: FTC weighs in on repair restrictions — https://consumer.ftc.gov/consumer-alerts/2021/05/ftc-weighs-repair-restrictions
- RS-EA8E2EA9D7970C00: Smartphones and Tablets — https://energy-efficient-products.ec.europa.eu/product-list/smartphones-and-tablets_en

No review details supplied.
