Product idea inbox

Capture rough, shareable product ideas here. No idea is a commitment or assignment. Check product vision, existing entries, feature cards and team tickets first. Link duplicates rather than creating another record. Tickets remain the team's reporting mechanism; link them instead of copying them.

Entry format

Copy this format when an actual idea is captured; do not create placeholder tasks.

ID: IDEA-<next number>
Title:
Captured: YYYY-MM-DD · Contributor:
Status: raw | discussing | prototyping | handed-off | parked | delivered
Raw thought: Preserve the contributor's intent.
User / problem: Unknown is fine.
Links: Related ticket, vision section, research or screenshot.
Discussion: Dated conclusions, open questions and excluded scope.
Handoff: Feature card, approved prototype revision and team task IDs when available.

Keep statuses descriptive. Only confirmed outcomes become decisions. Attach screenshots without customer or private data. Record why an idea is parked so future discussions retain context.

Ideas

ID: IDEA-1
Title: Strong place knowledge for Pailas
Captured: 2026-10-25 · Contributor: Prakash
Status: discussing
Raw thought: Strong Pailas need strong place knowledge. For every place NepWalk should
  know where it is, how long people stay (some like a short visit, some stay longer;
  offer both), its essence (what makes it special), restaurants around it and
  activities nearby (for example a clay-pot class in Bhaktapur).
User / problem: Travellers and Paila authors; Pailas feel generic without it.
Links: docs/v1/features/planner.md (ideas section), docs/v1/features/day-plan.md (P51
  visit time per place), place library M9, activities P31.
Discussion: 2026-10-25 visit time per place (minimum, typical, maximum, optional) is
  decided in P51 and built in v1. Essence, nearby restaurants and activities are open;
  to discuss with feature 8 (place page and place library).
Handoff: none yet.