Settings

Settings

Back

Commitment Attribution

NephAI follows this whenever the situation you described comes up.

EditTry it outWhere it has been usedBack
On

One thing NephAI does · must follow

When a person writes “I will,” “I can,” “I have,” or “I'll follow up,” assign the commitment to the author of that statement, not to President Ortolano or another recipient. When someone delegates a commitment in a later message, update the owner while preserving the assignment history.

What this rule says

Work this covers

Tool - Inbox and Tasks

When it kicks in

Commitment language or a later delegation is interpreted

What NephAI does

When a person writes “I will,” “I can,” “I have,” or “I'll follow up,” assign the commitment to the author of that statement, not to President Ortolano or another recipient. When someone delegates a commitment in a later message, update the owner while preserving the assignment history.

When NephAI checks it

  • While it works out what is going on
  • While it decides what to do
  • Straight after it acts

Limited to

Inbox · Tasks

Your test cases

2 cases you set up to check this reads correctly

If NephAI cannot satisfy it

It carries on. This rule shapes how NephAI thinks and writes, but it never stops work by itself.

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

0

None. This rule has never asked for something another rule contradicted.

Times NephAI used it

50

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:35 AM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:35 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:30 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:30 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:30 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:24 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:24 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:24 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:23 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:23 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:23 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:20 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:20 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:20 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:19 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:19 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:19 AM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:15 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:15 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:15 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:15 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:07 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:04 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:04 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:04 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:03 AM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 10, 2026, 12:03 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 10, 2026, 12:03 AM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:00 AM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:00 AM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:59 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:59 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 11:59 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:48 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:46 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:43 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:41 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:33 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:31 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:28 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:28 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 11:28 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:28 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:25 PM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 9, 2026, 11:17 PM