Collections track acquisition price, marketplaces export listing prices, and users will ask for it. But price data drags in currency codes, price kinds (paid, ask, market, trend), timestamps (a price without a date is noise) and a maintenance burden that card identity does not have.
Should v1 define a price field, reserve a shape for a 1.x addition, or declare prices permanently out of scope?
See the open questions section in the README.
Collections track acquisition price, marketplaces export listing prices, and users will ask for it. But price data drags in currency codes, price kinds (paid, ask, market, trend), timestamps (a price without a date is noise) and a maintenance burden that card identity does not have.
Should v1 define a price field, reserve a shape for a 1.x addition, or declare prices permanently out of scope?
See the open questions section in the README.