# Sample artifacts — Ops reporting discovery workshop

Produced by Ava after a live requirements session. This is a real-shaped example, not a transcript dump.

## Meeting summary

Ops asked for a regional ticket report before 9 AM. The room confirmed 9:00 is a hard SLA deadline, not a preference. Engineering flagged that the export currently fails on empty regions; Sam owns a fix by end of sprint.

## Business requirements

### Goal
Give operations yesterday's tickets by region before 9:00 AM so SLA reviews can start on time.

### In scope
- Regional ticket report for the prior calendar day
- Hard 9:00 AM delivery for SLA reviews
- Empty-region export that does not fail

### Requirements
1. **Must** — Regional ticket report ready by 9:00 AM (Maya, Ops).
2. **Must** — Export succeeds when a region has zero tickets (Sam, Engineering, end of sprint).

### Out of scope
- Real-time in-day ticket dashboards
- Changing the SLA review process itself

## User stories

### As an ops lead
I need yesterday's tickets grouped by region before 9:00 AM
so I can start SLA reviews on time.

**Acceptance criteria**
- Report covers the prior calendar day
- 9:00 AM is treated as a hard deadline
- Empty regions still appear with a zero count

### As an engineer
I need the export to survive a region with no tickets
so the morning report does not fail.

**Acceptance criteria**
- Empty region produces a valid file
- Fix owned by Sam, due end of sprint

## RAID / actions

| Type | Title | Owner | Due |
|---|---|---|---|
| Risk | Export fails on empty regions | Sam | End of sprint |
| Action | Fix empty-region export | Sam | End of sprint |
| Decision | 9:00 AM is a hard SLA deadline | Maya | — |