Use household and distribution together
Synthetic programme D1 permits one kit per confirmed household. A and B belong to H1; C belongs to H2. H1 already received its D1 kit. A second H1 request cannot use B’s person ID to claim another. The policy is an invented programme limit, not public benefit eligibility.
| Constraint | Required record | Example decision rule |
|---|---|---|
| Household evidence | Participant → confirmed household | A/B both map H1 |
| Allocation key | Distribution D1 + household H1 | One fulfilment per pair |
| New occurrence | Separate D2 ledger | D1 use does not consume D2 rule |
Test another person from the same household
| Case | Input | Expected decision |
|---|---|---|
| B requests D1 | H1 already served | No second D1 kit |
| C requests D1 | H2 not served | Household limit available |
- Identify participant household
- Identify distribution occurrence
- Read household fulfilment
- Record one supported allocation
An unconfirmed household relationship stays pending; it is not a reason to invent a new household ID.
D2 begins with the same one-kit-per-household rule. Does H1’s D1 record alone block D2?
Show the worked answer
No. The limit is per distribution and household. Check H1’s D2 record and current programme conditions separately.
Include two people linked to one household and one person in a new distribution, testing both sides of the allocation key.