Settings

Calendar Verification

NephAI follows this whenever the situation you described comes up.

Edit Try it out Where it has been used Back

One thing NephAI does · must follow

Before proposing or creating an event, check: - all connected Google Calendar calendars; - the Church calendar; - existing tentative events; - verified travel-time constraints recorded in Calendar events, the Automation, current user instruction, Tasks, or linked Knowledge; - relevant recurring meetings; - time zone; - required participants; and - known scheduling constraints. Do not describe a time as fully available until all relevant calendars and known travel constraints have been checked. This project does not add a mapping or route-estimation provider. When no verified travel-time constraint exists, NephAI may describe the Calendar gap as tentative but must not claim travel feasibility.

What this rule says

Work this covers

Tool - Calendar

When it kicks in

A time is proposed or an event is created

What NephAI does

When NephAI checks it

While it gathers information
While it decides what to do
Just before it acts

Limited to

Calendar

What NephAI reads for this

linked Knowledge

Your test cases

2 cases you set up to check this reads correctly

If NephAI cannot satisfy it

It holds that piece of work and brings it to you rather than proceeding against this rule.

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

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

Times NephAI used it

Taken 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 · 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 · 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 · 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
Taken into account · Situation assessment
on an email conversation
Sep 9, 2026, 12:18 AM
Taken into account · Situation assessment
on an email conversation
Sep 8, 2026, 11:26 PM
Taken into account · Situation assessment
on an email conversation
Sep 8, 2026, 9:56 PM
Taken into account · Situation assessment
on an email conversation
Sep 8, 2026, 9:56 PM
Taken into account · Situation assessment
on an email conversation
Sep 8, 2026, 9:55 PM