aceTRV-2026-0011Version 1 · Certified
Reason for this version
Record certified retroactively at institutional-layer launch
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-0011 version: 1 kind: certified reason: Record certified retroactively at institutional-layer launch timestamp: 2026-07-11T21:15:52.378521Z status: published lens: general sector: other headline: From the old to the new generation of a product : unlearn, improve, and prosper dek: Purpose Drawing on the theories of planned obsolescence and dynamic capabilities, this study aims to jointly address marketing and organizational aspects of the transition from the existing to the new generation of a product (i.e. a product rollover). It conceptualizes the relevance of organizational unlearning in rollovers and relates it to the improvement in the marketing mix of multigenerati... gain_reading: Purpose Drawing on the theories of planned obsolescence and dynamic capabilities, this study aims to jointly address marketing and organizational aspects of the transition from the existing to the new generation of a product (i.e. a product rollover). It conceptualizes the relevance of organizational unlearning in rollovers and relates it to the improvement in the marketing mix of multigenerati... problem_reading: (none) limitation: Machine-ingested summary: the claims above reflect a single primary source and have not been weighed against contradicting evidence by a Truvace editor yet. tag: (none) key_points: (none) rundown: (none) sources: - peer_reviewed | Strathprints: The University of Strathclyde institutional repository (University of Strathclyde) | https://strathprints.strath.ac.uk/view/author/837763.html> | 2026-12-14 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- 10266d70b68b6d8ff3a844d2428cd9ae3499ce3da8dc77ba94e2a579b051b029
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-0011 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.