wmj/nur-falah-prevention
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: resolve both governance gates (OPEN-01, Horizon 2 Phase 0)

Browse Source 
OPEN-01 (scholarly-review-log.md): ruled NOT subject to the one-third
cap for an inter-vivos waqf made in health. The existing
FamilyWaqfDesignator logic already applied no health-state cap absent a
marad al-mawt trigger, so no behavior change — only the open-question
framing in the exported deed, InfoPanel copy, on-screen note, and source
comments moved from "open" to "resolved."

Horizon 2 Phase 0 (legal opinion + signed institutional partner
agreement): both now signed. This clears the PRD's gate to begin real
institutional-integration engineering, but that integration hasn't been
built yet — the Claims module (DigitalClaims.svelte, claims.js) still
ships as a local, non-custodial demonstration only, and the pilot banner
is updated to say so precisely rather than implying the module itself
is now production-ready.

Updated README.md and deploy/DEPLOY.md to match.
This commit is contained in:
wmj
2026-10-23 10:40:26 +08:00
parent e711783087
commit e87e329731
5 changed files with 66 additions and 55 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+23 -18
View File
@@ -12,28 +12,33 @@ system of the live `moslem03.falahos.my` (Nur Falah Muslim Companion) app.
| 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 | **Built ahead of scholarly sign-off** — see below |
| Digital Beneficial Claims | 2 | **Pre-pilot demo only** — see below |
| Family Waqf Designator | 1 | Scholarly sign-off received — see below |
| Digital Beneficial Claims | 2 | Phase 0 complete; module itself still a demo — see below |
## Important: two governance gates were overridden for this build
## Governance gates — both now resolved
Per explicit product direction, this build proceeded past two gates stated in the
project's own PRDs and review log:
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) is gated on scholarly sign-off.
`scholarly-review-log.md` (in the `digital-waqif` docs repo) tracks **OPEN-01** —
whether a healthy-state waqf is subject to the one-third cap — as unresolved.
This module ships anyway; the in-app copy states the open question rather than
presenting invented certainty.
2. **Horizon 2** (Digital Beneficial Claims) PRD states: *"No engineering work begins
until Phase 0 (legal opinion + signed institutional partner agreement) is
complete."* No confirmation of Phase 0 completion was available. The Claims module
ships as a local, non-custodial demonstration of the data model and transfer
restriction only — no real legal wrapper, no institutional integration, no real
claims issued. It carries a persistent in-app banner saying so.
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.
Both are flagged here, in `deploy/DEPLOY.md`, and in the relevant module's source
comments so this isn't silently presented as production-ready.
Resolution status is reflected here, in `deploy/DEPLOY.md`, and in the relevant
module's source comments.
## Development