Settings

Settings

Back

Task Ownership

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 analyzing an email thread, distinguish among: - Tasks assigned to the user: direct requests or action items explicitly addressed to President Ortolano; - follow-ups for the user: direct reminders or clarifications addressed to him; and - Tasks for others: action items or follow-ups directed at someone else in the thread, including copied recipients. Do not assume every follow-up in an email is directed to the user. Assign an action item to him only when the sender explicitly asks him to do it. If another person is asked or reminded, responsibility stays with that person. A request addressed to a visible To or Cc recipient remains that person's responsibility when the user received only a hidden copy. Hidden delivery alone does not assign the request or create a need for the user to reply. Before drafting a reply, determine: - who is being asked to do what; - whether the user or someone else is the intended owner; and - whether the reply preserves Task ownership without shifting responsibility.

What this rule says

Work this covers

Tool - Inbox and Tasks

When it kicks in

An email thread is analyzed or answered

What NephAI does

When analyzing an email thread, distinguish among: - Tasks assigned to the user: direct requests or action items explicitly addressed to President Ortolano; - follow-ups for the user: direct reminders or clarifications addressed to him; and - Tasks for others: action items or follow-ups directed at someone else in the thread, including copied recipients. Do not assume every follow-up in an email is directed to the user. Assign an action item to him only when the sender explicitly asks him to do it. If another person is asked or reminded, responsibility stays with that person. A request addressed to a visible To or Cc recipient remains that person's responsibility when the user received only a hidden copy. Hidden delivery alone does not assign the request or create a need for the user to reply. Before drafting a reply, determine: - who is being asked to do what; - whether the user or someone else is the intended owner; and - whether the reply preserves Task ownership without shifting responsibility.

When NephAI checks it

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

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 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 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: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 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: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 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:19 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: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: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 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 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: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 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:03 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 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 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: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 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:13 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 11:13 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:13 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:01 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:01 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 11:01 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:00 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 11:00 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 11:00 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 10:59 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 10:59 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 10:59 PM

  • Taken into account · Automation occurrence planning

    while deciding what to do

    Sep 9, 2026, 10:57 PM

  • Taken into account · Automation occurrence planning

    while working out who this belongs to

    Sep 9, 2026, 10:57 PM