Shelfery Feature Inventory (Not Yet Populated)¶
This document is a placeholder. No features are approved yet for Shelfery.
Why this is empty¶
A feature inventory should be derived from approved product requirements
(product/product-requirements.md), which do not yet exist. Listing
candidate features here before requirements exist would risk them being
mistaken for commitments — something this venture's roadmap explicitly
avoids (see docs/strategy/roadmap.md: "no features are committed until
product/product-requirements.md is defined and reviewed").
Note that some feature-shaped ideas already appear elsewhere in this
venture's documentation as explicitly labeled hypotheses — for example,
barcode scanning or household-sharing are mentioned as open questions in
docs/strategy/assumptions-and-open-questions.md, not as planned
features. Their appearance there does not mean they belong in this
inventory; they remain unresolved until a requirements process addresses
them.
What any future feature must respect¶
When this inventory is eventually populated, every feature entry should be
checked against ventures/shelfery/docs/strategy/product-principles.md —
particularly the principles on low-friction data entry, avoiding shame
around waste, making uncertain information visibly uncertain, and never
presenting food-safety estimates as guarantees. Features that conflict
with those principles should not be added without deliberately revisiting
the principles first.
What must happen before this can be populated¶
product/product-requirements.mdmust exist and be approved.- Features should be derived from those requirements, not proposed independently of them.