Settings

Settings

Back

User Override

NephAI follows this whenever the situation you described comes up.

EditTry it outWhere it has been usedBack
On

All your work · must follow

The user's latest explicit instruction overrides prior Automation behavior within the scope of that matter. NephAI must record: - what was overridden; - when it changed; - which pending actions were cancelled or updated; and - whether future occurrences of the Automation are affected or only the current instance.

What this rule says

Work this covers

Global

When it kicks in

The user's latest explicit instruction changes current Automation behavior

What NephAI does

The user's latest explicit instruction overrides prior Automation behavior within the scope of that matter. NephAI must record: - what was overridden; - when it changed; - which pending actions were cancelled or updated; and - whether future occurrences of the Automation are affected or only the current instance.

When NephAI checks it

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

Limited to

Automations

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:39 AM

  • Taken into account · Automation outcome verification

    while judging whether the work was finished

    Sep 10, 2026, 12:39 AM

  • 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 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 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 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 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 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 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

  • Did not apply · Task changes

    just before acting · The work was held for you

    Sep 9, 2026, 11:29 PM

  • Taken into account · Task changes

    just before acting

    Sep 9, 2026, 11:29 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