Settings
No Invented Commitments
NephAI follows this whenever the situation you described comes up.
One thing NephAI does · must follow
Do not write language that creates a commitment President Ortolano has not made. Do not automatically write: - “I will take care of this.” - “I will contact them.” - “I have approved this.” - “I will attend.” - “We will proceed.” - “I agree.” Such language may be used only when supported by an explicit instruction, prior decision, authorized Automation, or the routine reimbursement policy. An ordinary Church reimbursement request with an attached receipt or invoice may support independent approval language when current evidence does not say the purchase was unauthorized, disputed, or withheld. The current stake clerk owns processing. This permits approval wording in a prepared reply; it does not authorize sending.
What this rule says
Work this covers
When it kicks in
What NephAI does
When NephAI checks it
- While it decides what to do
- Just before it acts
Where it does not apply
- Commitment language is permitted when supported by an explicit instruction, prior decision, or authorized Automation.
- A routine Church reimbursement request with an attached receipt or invoice may support independent approval wording when current evidence does not contradict prior purchase authorization.
Limited to
Your test cases
If NephAI cannot satisfy it
Try it out
See where this rule would take effect and how NephAI reads the cases you set up. This only shows you the result — nothing is saved, sent, or changed.
Where this rule has been used
Clashes with other rules
0None. This rule has never asked for something another rule contradicted.
Times NephAI used it
50Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 10:56 PM
Taken into account · Stewardship situation detection
while deciding what to do
Sep 9, 2026, 10:20 PM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 9:57 PM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 9:57 PM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 9:56 PM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 9:55 PM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 8:26 PM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 8:18 PM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 8:18 PM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 8:08 PM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 7:08 PM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 7:04 PM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 6:18 PM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 2:32 PM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 2:16 PM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 2:16 PM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 2:04 PM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 1:58 PM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 1:22 PM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 1:18 PM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 12:50 PM
Taken into account · Pre-drafted reply
on an email conversation
Sep 9, 2026, 12:31 PM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 12:30 PM
Taken into account · Reply availability grounding
on an email conversation
Sep 9, 2026, 12:14 PM
Taken into account · Pre-drafted reply
on an email conversation
Sep 9, 2026, 12:13 PM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 12:12 PM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 11:48 AM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 11:44 AM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 11:12 AM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 10:25 AM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 10:24 AM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 9:58 AM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 9:38 AM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 9:36 AM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 9:04 AM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 8:22 AM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 8:04 AM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 7:58 AM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 7:46 AM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 7:46 AM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 7:32 AM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 7:28 AM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 6:58 AM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 6:58 AM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 6:48 AM
Taken into account · Pre-drafted reply
on an email conversation
Sep 9, 2026, 6:08 AM
Taken into account · Pre-drafted reply
on an email conversation
Sep 9, 2026, 6:07 AM
Taken into account · Pre-drafted reply
on an email conversation
Sep 9, 2026, 6:06 AM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 5:04 AM
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 2:02 AM