mohd/Salon

Files

T

mohd 229975c612 docs: revise ADR 0001, risks, and architecture for accuracy

- ADR 0001: distinguish payment/OTP (sync by design) from notifications
  (fire-and-forget); correct misleading claim that notification failures
  surface to clients — they are silently absorbed as FAILED status
- risks.md: upgrade USERNAME_FIELD entry with concrete breakage (admin,
  create_superuser, JWT lookup); add booking overlap race condition with
  root cause and fix (select_for_update)
- architecture.md: document notification/OTP provider coupling as an MVP
  shortcut and note the Phase 2 fix (dedicated NotificationProvider)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-03-01 23:30:04 +03:00

0001-synchronous-external-calls-mvp.md

docs: revise ADR 0001, risks, and architecture for accuracy

2026-03-01 23:30:04 +03:00

0002-moyasar-payment-gateway.md

Fleshed out documentation

2026-02-28 17:41:00 +03:00

0003-authentica-otp-provider.md

Fleshed out documentation

2026-02-28 17:41:00 +03:00

README.md

Fleshed out documentation

2026-02-28 17:41:00 +03:00

README.md

Architecture Decision Records

ADRs capture cross-cutting or hard-to-reverse decisions. Add a new ADR when changing providers, async strategy, data model boundaries, or other architectural choices.

Use the template in docs/templates/adr.md and increment the numeric prefix (0002, 0003, ...).