What does google_calendar.event.rescheduled prove?
Last reviewed 2026-09-05Skill version 0.1.0Provisional
Prove that the event now starts and ends at the requested instants. The provider changed the event inside this operation, and the stored start and end name the new instants. It does not prove that a guest was told.
How does the evidence correlate with this operation?
Strategy
Assurance
Keys
Required
resource_id
strong
event_id from $input.event_id
no
resource_id
weak
calendar_id from $input.calendar_id
no
Which evidence does the contract require?
Minimum evidence level E2. An independent channel is required. Minimum channels: 1.
Channel
Level
Independence
Verifier
Description
event_intent_readback
E2
provider readback
http
Read the event that the intent names. A condition path is $observed.event_intent_readback.updated. The read states no maxAttendees parameter.
calendar_change_events
E3
provider event
webhook
The notifications of a channel that watches the events collection of the calendar, since the operation started. The webhook verifier returns {events, count, latest, earliest, types, duplicates_dropped}. The body is empty, so a count names no event.
Which conditions must all hold for VERIFIED?
Condition
Meaning
Path
Operator
Expected
Evidence
calendar_changed_for_the_reschedule
At least one notification says that the events collection of the calendar changed since the operation started. The verdict map holds the rest of the promise, because the read-back of this level can date no state.
$observed.calendar_change_events.count
gte
1
calendar_change_events
Which conditions give CONTRADICTED?
Condition
Class
Reason
Path
Operator
Expected
duplicate_calendar_change_on_reschedule
duplicate side effect
The calendar changed more than once since the operation started. A second update mails every guest a second time. Stop and ask a person.
$observed.calendar_change_events.count
gt
1
Which observed states map to a verdict before completion?
The event is one occurrence of a recurring event. A change of one occurrence and a change of the whole series are different operations, and this skill covers neither. Ask a person.
rescheduled_to_the_wrong_time
($observed.event_intent_readback.updated time_after "$operation.created_at") and (($observed.event_intent_readback.start.dateTime time_before "$input.new_start_time") or ($observed.event_intent_readback.start.dateTime time_after "$input.new_start_time"))
CONTRADICTED
The agent changed the event inside this operation, and the event now starts at another instant than the person named. Every guest holds a wrong time. Stop and ask a person.
the_new_time_is_not_stored_yet
(not ($observed.event_intent_readback.id eq "$input.event_id")) or (not ($observed.event_intent_readback.start.dateTime time_after "$input.new_start_time")) or (not ($observed.event_intent_readback.start.dateTime time_before "$input.new_start_time")) or (not ($observed.event_intent_readback.end.dateTime time_after "$input.new_end_time")) or (not ($observed.event_intent_readback.end.dateTime time_before "$input.new_end_time")) or (not ($observed.event_intent_readback.updated time_after "$operation.created_at"))
PENDING
The provider does not yet report the event with the requested start and end. The runtime observes again later.
How long does the runtime observe?
Timing member
Value
Initial delay
1000 ms
Poll interval
5000 ms
Backoff
exponential factor 2, max 60000 ms
Maximum attempts
40
Timeout
900000 ms
Stale read window
20000 ms
On timeout
UNVERIFIABLE (evidence_unavailable_before_timeout), escalated to a person
Provely