Schema-per-tenant was the original call, but falah-os-master's
infrastructure/postgres/init.sql already establishes database-per-service
as the platform convention (falahid, falahwallet, falahramz, falahmock,
falahistore). Database-per-tenant matches that pattern and is a stronger
isolation boundary than schemas would have been.
Clio/Stripe competitive benchmark, moslem03/04 backend reality check,
and the moslem04 sync API spec, plus the resolved schema-per-tenant
isolation decision that unblocks Phase 2 of the sync spec.
Adds a 7th persona (Emergency/Community Contact — mosque, khairat
officer, police, ambulance, notified automatically the moment a trigger
fires) and extends every existing journey with what shipped since the
last version: Zakat, Khairat, Sadaqah, jurisdiction/professional review,
draft will PDF, and the prayer-times/Qibla/locate/Quran/neighbourhood
lifestyle tools. New footnote clarifying Neighbourhood is scoped to the
account, not the estate-planning family.
Six personas mapped against the app's actual roles and features: Head of
Family (owner), Family Member, Estate Agent/Mutawalli, the multi-family
professional-mutawalli variant, plus two no-account personas reached only
through data others enter — the Heir/Beneficiary (notified by the
notify-heirs email relay once a trigger fires) and the Professional
Reviewer (tracked via the Wassiyah review-request workflow). Each journey
is stage-by-stage through real tabs, not generic template steps.
wmj