User Story Backlog

Purpose

This folder turns the PRD suite into a practical backlog.

Each story should be understandable by a product designer, a builder, and a QA tester without opening the old code first.

Files

• platform-user-story-backlog.md: complete platform-level backlog grouped by epic.

Story Format

Each story uses:

ID: US-AREA-000
Story: As a <actor>, I want <capability>, so that <benefit>.
Acceptance criteria:
- Given ...
- When ...
- Then ...
PRD: ...
Evidence: ...

Coverage Rule

The backlog must cover these platform areas:

• preservation and migration;
• auth, tenancy, team, and access;
• flows, boards, companions, forms, and publishing;
• Studio visual flow and runtime;
• chat, agents, controls, widgets, and agent teams;
• AI tools, ingestion, research, and knowledge;
• billing, quotas, usage, and wallet;
• integrations, media, webhooks, submissions, and statistics;
• admin navigation, analytics, Hetzner deployment, backup, and operations.