Calendar event operation acceptance contract

Operation acceptance contract: target the exact requested Calendar event and never substitute another resource family. Validate arguments without creating a temporary resource. Execute the intended create operation once; retries in the same turn with the same target name must replay the original result rather than create another resource.

After a successful create or update, use the returned resource ID for a live server readback. Verify title, eventId, start/end time, timezone, and calendar. The response is complete only when the readback matches the request and reports verificationSource=live_read. If any requested field is absent or mismatched, report partial completion and identify the mismatch. Never create a second resource merely to validate a schema or verify the first one.

Tool output and the live Action Registry override this card. A successful write response without live readback proves only that a skeleton exists; it does not satisfy the operation.

Related actions

arinova.calendar.create_event, arinova.calendar.get_event

Also known as

operation acceptance, completion verification, create and read back, live readback, no duplicate resource

---

Machine-readable Markdown · Knowledge index