Build your own Canny.

# Build an original app inspired by Canny

You are an experienced product designer and full-stack engineer. Build a working, polished MVP from the brief below. Implement the core journeys end to end; a static mockup is not sufficient. Inspect the current environment, make sensible implementation decisions, and get started. Ask a question only if a missing answer genuinely blocks implementation.

Starting platform: Web. Explicit customized Product & audience and Tech stack requirements take precedence over this starting target.

## Product & audience
Build an original product-feedback portal called Feedbacklane, inspired by Canny. Customers suggest improvements and vote, while product staff triage requests, merge duplicates, and publish a roadmap and changelog. Start with one organization and public/private feedback boards.

## Design
Create an original portal with searchable suggestions, vote controls, filters, status badges, and an accessible roadmap. Staff get a separate triage panel with merge previews and private notes. Visually separate official status updates from customer comments.

## Features
1. Boards and suggestions: create public/private boards, accept titled suggestions with safe Markdown, add tags, and show an explicit privacy notice. Restrict private-board search and subscriptions to authorized users.

2. Votes and comments: support one reversible vote per account/suggestion, comments with moderation, and subscriptions to status changes. Derive totals from actual vote records.

3. Triage and duplicates: let staff assign owners, prioritize internally, and merge duplicate suggestions into a canonical request. Union votes by user, preserve comment provenance, and leave redirects to the canonical request.

4. Roadmap and updates: publish selected planned/in-progress/completed requests on a real status-driven roadmap, keep staff-only prioritization private, and author original changelog entries linked to completed requests.

5. Notifications and export: queue configured notifications with retry-safe delivery, expose unsent/setup states honestly, export authorized feedback as CSV, and audit staff status/merge operations.

## Tech stack
Use TypeScript, PostgreSQL, authenticated staff/customer sessions, and a background notification worker. Perform merges transactionally, maintain unique votes/subscriptions, and apply board visibility consistently to pages, exports, search, and notification jobs.

## Data & behavior
Organization; UserRole; Board {visibility}; Suggestion {canonicalId, state, ownerId, priority}; Vote; Comment {sourceSuggestionId}; Subscription; StatusEvent; ChangelogEntry; NotificationJob; MergeEvent. Keep private staff notes separate from public records.

Acceptance checks and scope:
Test vote undo/retry, merging two suggestions voted by the same person, a merge chain, private-board exports, status updates with unsubscribed users, and stale staff edits. Exclude AI feedback extraction, automatic customer support inboxes, billing integrations, and public exposure of internal prioritization.

## Originality and assets
The named product is a reference for general workflows only. Use an original product name, visual identity, wording, layout, and assets. Do not copy proprietary code, branded logos, distinctive screens, private APIs, paid templates, or protected media. Use original or appropriately licensed sample data and assets. Build from this brief rather than scraping the reference service. Do not imply affiliation with the referenced company.

## Implementation quality
- Make every visible control work, with clear loading, success, empty, validation, and failure states. Remove controls for unimplemented features.
- Support the target platform and responsive or resizable layouts where appropriate. Use platform-appropriate accessibility semantics, labels, keyboard operation, visible focus, sufficient contrast, and reduced-motion preferences. Provide alternatives for drag-only interactions.
- Validate inputs at the relevant boundary. Treat imported or user-generated content as untrusted; render it safely. Confirm destructive actions or offer undo.
- Keep state changes reliable across navigation and reloads. Never silently lose edits. Handle persistence and network errors with an actionable message.
- Keep the scope realistic. Prioritize the complete primary journey. If a custom Features section differs from the baseline, update the data model, design, and acceptance checks to match it; explicit custom requirements take precedence over baseline assumptions.
- Provide realistic original sample content and a useful empty state. Keep sample data clearly separate from user-created data.

## Delivery and verification
1. Inspect the repository and outline the implementation in a few sentences.
2. Implement the app and connect its actual data flow. Continue until the primary journey works.
3. Run appropriate checks and test the acceptance cases above on the target platform. Verify responsive layouts and keyboard navigation when browser tools are available. For native projects, build with the available SDK and test an emulator or device when possible; report any missing native verification honestly. For games, verify the rules and gameplay loop, not only the menus.
4. Fix observed failures, then provide the runnable result, setup/run instructions, a brief explanation of what is implemented, and any specific configuration or verification limits.

This is a focused MVP. Do not add billing, AI services, or unrelated features unless explicitly requested in the brief. Start building now.