# Nur Falah — Estate & Waqf Suite Horizon 1 (Prevention Suite) + Horizon 2 (Unlock Programme, pre-pilot demo) from the Nur Falah PRDs, built as a standalone Svelte 5 + Vite PWA, styled to match the visual system of the live `moslem03.falahos.my` (Nur Falah Muslim Companion) app. ## Modules | Module | Horizon | Status | |---|---|---| | Faraid Calculator | 1 | Shared calc core, 14 classical cases passing (`src/lib/calc/faraid.test.js`) | | Asset Registry | 1 | Local-first, feeds every other module's estate total | | Wassiyah Generator | 1 | 1/3 meter, heir-exclusion block, jurisdiction-aware export | | Hibah Tracker | 1 | Shared marad al-mawt guardrail | | Family Waqf Designator | 1 | Scholarly sign-off received — see below | | Digital Beneficial Claims | 2 | Phase 0 complete; module itself still a demo — see below | ## Governance gates — both now resolved Per explicit product direction, this build originally proceeded past two gates stated in the project's own PRDs and review log, before either was resolved. Both are now closed: 1. **Family Waqf Designator** (Horizon 1 PRD §8.5) was gated on scholarly sign-off. `scholarly-review-log.md` (in the `digital-waqif` docs repo) tracked **OPEN-01** — whether a healthy-state waqf is subject to the one-third cap. **Resolved: ruled NOT subject to the one-third cap.** This matches the module's existing implementation (no health-state cap applied absent a `marad al-mawt` trigger), so no logic change was needed — only the open-question framing in the UI and source comments has been updated to reflect the ruling. 2. **Horizon 2** (Digital Beneficial Claims) PRD required: *"No engineering work begins until Phase 0 (legal opinion + signed institutional partner agreement) is complete."* **Resolved: both the legal opinion and the institutional partner agreement are signed.** This clears the PRD's gate to begin real engineering on institutional integration. It does **not** by itself mean the live Claims module now issues real claims — no institutional integration has been built yet, so the module still ships as a local, non-custodial demonstration of the data model and transfer restriction only, pending that integration work. Resolution status is reflected here, in `deploy/DEPLOY.md`, and in the relevant module's source comments. ## Development ```bash npm install npm run dev # http://localhost:5173 npm run test # classical faraid test suite npm run build ``` ## Deploy See `deploy/DEPLOY.md`. Target: `moslem04.falahos.my`.