Slice an epic into small releasable increments

Break this epic into small, independently releasable slices. Epic: [DESCRIPTION AND GOAL] Users and main workflow: [WHO DOES WHAT] Full scope as currently imagined: [LIST] Constraints: [DEADLINE, TEAM SIZE, TECH LIMITS] What we most need to learn early: [RISKIEST ASSUMPTION] Rules for slicing: - Slice vertically: each slice works end to end for a user (UI, logic, data), not by technical layer. - Each slice is shippable (behind a flag if needed) and fits in a sprint or less. - Use slicing patterns where they help: happy path first, one user type first, manual before automated, one platform or integration first, simple rules before complex ones, read-only before edit. - The first slice should test the riskiest assumption or deliver the core value with the least work. Return: 1. A table: Slice | User value delivered | What is deliberately left out | Pattern used | Relative size (S/M/L). 2. A recommended release order with the reason for the order. 3. The minimum set of slices that would let us call the epic useful. 4. A user story with acceptance criteria for the first slice. 5. Any slice that is still too big, with a suggestion to split it further.