ProvelyProve that the document holds the revision that this batch update produced. The document that the person named holds the revision that this update produced. This level does not prove what the update changed.
| Fact | Value |
|---|---|
| Contract id | google_docs.document.update_applied |
| Version | 1.0.0 |
| Hash | a2ac6d735ebff5d7 |
| Completion level | update_applied |
| Publisher | Built and signed by Provely. |
| Certification | Provisional |
| Skill | Google Docs API 0.1.0 |
| Valid for provider API versions | v1.20260902 |
What is the intent?
Apply the batch update to the document.
What is the subject and the action?
| Member | Value |
|---|---|
| Subject type | google_docs.document |
| Canonical effect | document.batch_update |
| Provider operation | POST /v1/documents/{documentId}:batchUpdate |
| Idempotency | none, retry is not safe |
Which false successes give CONTRADICTED?
- 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_docs.openapi#/paths/~1v1~1documents~1{documentId}:batchUpdate/post: google_docs.openapi, retrieved 2026-09-09google_docs.openapi#/paths/~1v1~1documents~1{documentId}:batchUpdate/post/responses/200: google_docs.openapi, retrieved 2026-09-09google_docs.openapi#/components/schemas/BatchUpdateDocumentResponse/properties/writeControl: google_docs.openapi, retrieved 2026-09-09google_docs.openapi#/components/schemas/WriteControl/properties/requiredRevisionId: google_docs.openapi, retrieved 2026-09-09google_docs.docs.write_control#state-consistency-and-the-revision-of-a-document/the-response-of-a-batch-update-carries-a-write-control: google_docs.docs.write_control, retrieved 2026-09-09google_docs.openapi#/components/schemas/Document/properties/documentId: google_docs.openapi, retrieved 2026-09-09google_docs.openapi#/components/schemas/BatchUpdateDocumentResponse/properties/documentId: google_docs.openapi, retrieved 2026-09-09google_docs.openapi#/components/schemas/Document/properties/revisionId: google_docs.openapi, retrieved 2026-09-09google_docs.docs.write_control#state-consistency-and-the-revision-of-a-document/the-published-schema-of-the-document-revision: google_docs.docs.write_control, retrieved 2026-09-09google_docs.docs.write_control#state-consistency-and-the-revision-of-a-document/read-the-revision-then-write-against-it: google_docs.docs.write_control, retrieved 2026-09-09
Can google_docs.document.update_applied 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 Docs API.
What happens after the timeout?
The verdict is UNVERIFIABLE. The operation goes to a person for review.