ProvelyProve 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.
| Fact | Value |
|---|---|
| Contract id | google_calendar.event.rescheduled |
| Version | 1.0.0 |
| Hash | a9eb7474a30680a4 |
| Completion level | rescheduled |
| Publisher | Built and signed by Provely. |
| Certification | Provisional |
| Skill | Google Calendar API 0.1.0 |
| Valid for provider API versions | v3.20260826 |
What is the intent?
Move the meeting to the stated new time.
What is the subject and the action?
| Member | Value |
|---|---|
| Subject type | google_calendar.event |
| Canonical effect | calendar.event_update |
| Provider operation | PATCH /calendar/v3/calendars/{calendarId}/events/{eventId} |
| Idempotency | none, retry is not safe |
Which false successes give CONTRADICTED?
- duplicate side effect
The signed contract states the exact conditions, the evidence and the timing. The runtime reads them. The page states the promise.
Where do these rules come from?
google_calendar.openapi#/paths/~1calendar~1v3~1calendars~1{calendarId}~1events~1{eventId}/patch: google_calendar.openapi, retrieved 2026-09-09google_calendar.openapi#/components/schemas/Event/properties/updated: google_calendar.openapi, retrieved 2026-09-09google_calendar.docs.times#events-times-and-the-change-of-a-time/events-move-does-not-change-a-time: google_calendar.docs.times, retrieved 2026-09-09google_calendar.docs.times#events-times-and-the-change-of-a-time/one-instant-five-spellings: google_calendar.docs.times, retrieved 2026-09-09google_calendar.events#/events/calendar.events.exists: google_calendar.events, retrieved 2026-09-09google_calendar.docs.push#push-notifications/one-resource-state-covers-three-different-changes: google_calendar.docs.push, retrieved 2026-09-09google_calendar.openapi#/paths/~1calendar~1v3~1calendars~1{calendarId}~1events~1watch/post: google_calendar.openapi, retrieved 2026-09-09google_calendar.docs.push#push-notifications/what-the-page-refuses-to-promise: google_calendar.docs.push, retrieved 2026-09-09
Can google_calendar.event.rescheduled return VERIFIED from the action response alone?
No. The action response is E1, and an acknowledgement is never terminal success. The contract needs evidence of level E2 or higher from Google Calendar API.
What happens after the timeout?
The verdict is UNVERIFIABLE. The operation goes to a person for review.