Skip to content

CRITICAL_FLOWS.md

Latest commit

 

History

History
84 lines (57 loc) · 1.22 KB

CRITICAL_FLOWS.md

File metadata and controls

84 lines (57 loc) · 1.22 KB
Raw

🔄 Critical System Flows

EN: These core flows must remain reliable in every release.

PT: Estes fluxos core devem manter-se fiáveis em todas as releases.

These flows must always work reliably.

1. Member Check-in (QR)

  1. Member scans QR
  2. System validates membership
  3. Check-in recorded
  4. UI confirms success

Failure:

  • Show clear error
  • Allow retry

2. Member Check-in (PIN)

  1. Member enters PIN
  2. System validates PIN
  3. Check-in recorded

Failure:

  • Increment failed attempts
  • Lock after threshold
  • Show lockout message

Recovery:

  • Admin override required

3. Payment (Cash)

  1. Create payment
  2. Mark as completed
  3. Reflect in reports

4. Payment (Multicaixa / Transfer)

  1. Create payment
  2. Upload proof
  3. Payment marked as pending
  4. Operator reviews proof
  5. Approve → completed
  6. Reject → flagged

5. Booking Flow

  1. Member books class
  2. Capacity validated
  3. Booking confirmed
  4. Check-in consumes booking

6. User Creation (Admin)

  1. Admin creates user
  2. Role assigned
  3. User receives access
  4. Linked to gym/member

🚨 Rule

If any flow:

  • blocks user
  • loses data
  • produces incorrect financial state

→ system is not production-ready