Variable FLS_DENY_READ_FIELDConst

The runtime permission-row assignments the bundle writes through the real entity path after the snapshot (all on non-system roles, so every save must be permitted):

• Denier.Title → Deny / No Access / No Access — read-Deny beats Writer's Allow for the multi user (4.1) AND clamps Writer's Update=Allow via read-required (4.3). Title is nullable, so denying it read-wise cannot make records uncreatable.
• Denier.Phone → Allow / Deny / Deny — readable but update-denied (3.9) and create-denied (3.11: supplied value dropped, column takes its default).
• Neutral.LastName → No Access ×3 — neutral rows leave Writer's Allow standing (4.2).
• Reader.Email → Deny / No Access / No Access — the read-stripping target (3.1–3.7).
• Reader.BCMID → row DELETED — a missing row on an enabled entity fails closed (4.4).