ProvelyProve that Calendar holds the event at the requested instant. The event exists with the intended title, start and end. It does not prove that a guest is on it, was told, or comes.
| Fact | Value |
|---|---|
| Contract id | google_calendar.event.created |
| Version | 1.0.0 |
| Hash | 4182cf3a94b3e409 |
| Completion level | created |
| 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?
Put the meeting on the calendar at the stated time.
What is the subject and the action?
| Member | Value |
|---|---|
| Subject type | google_calendar.event |
| Canonical effect | calendar.event_create |
| Provider operation | POST /calendar/v3/calendars/{calendarId}/events |
| Idempotency | none, retry is not safe |
Which false successes give CONTRADICTED?
- duplicate side effect
- pre existing state
- wrong subject
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/post: google_calendar.openapi, retrieved 2026-09-09google_calendar.openapi#/paths/~1calendar~1v3~1calendars~1{calendarId}~1events/post/responses/200: google_calendar.openapi, retrieved 2026-09-09google_calendar.docs.events#create-an-event-and-invite-guests/an-event-needs-a-start-and-an-end: google_calendar.docs.events, retrieved 2026-09-09google_calendar.docs.times#events-times-and-the-change-of-a-time/a-read-chooses-the-spelling-of-the-answer: google_calendar.docs.times, retrieved 2026-09-09google_calendar.openapi#/components/schemas/Event/properties/id: google_calendar.openapi, retrieved 2026-09-09google_calendar.openapi#/paths/~1calendar~1v3~1calendars~1{calendarId}~1events~1{eventId}/get/responses/200: google_calendar.openapi, retrieved 2026-09-09google_calendar.openapi#/components/schemas/Event/properties/summary: google_calendar.openapi, retrieved 2026-09-09google_calendar.openapi#/paths/~1calendar~1v3~1calendars~1{calendarId}~1events/post/requestBody: google_calendar.openapi, retrieved 2026-09-09google_calendar.openapi#/components/schemas/Event/properties/status: google_calendar.openapi, retrieved 2026-09-09google_calendar.docs.times#events-times-and-the-change-of-a-time/the-status-of-an-event: google_calendar.docs.times, retrieved 2026-09-09google_calendar.openapi#/components/schemas/Event/properties/created: google_calendar.openapi, retrieved 2026-09-09google_calendar.docs.times#events-times-and-the-change-of-a-time/the-two-times-that-calendar-publishes-about-an-event: 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.created 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.