Contract: google_docs.document.update

Prove 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.

Contract identity.
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`
Subject identity	document_id = `$action.result.documentId`
Canonical effect	`document.batch_update`
Provider operation	`POST /v1/documents/{documentId}:batchUpdate`
Idempotency	none, retry is not safe

How does the evidence correlate with this operation?

Strategy	Assurance	Keys	Required
`resource_id`	strong	document_id from `$action.result.documentId`	yes
`resource_id`	strong	write_revision_id from `$action.result.writeControl.requiredRevisionId`	no

Which evidence does the contract require?

Minimum evidence level E2. An independent channel is required. Minimum channels: 1.

Channel	Level	Independence	Verifier	Description
`document_readback`	E2	provider readback	`http`	Read the document from the provider. A condition path is $observed.document_readback.revisionId. The read states includeTabsContent, so the content sits under tabs and the legacy member body stays empty.

Which conditions must all hold for VERIFIED?

Condition	Meaning	Path	Operator	Expected	Evidence
`document_is_the_subject`	The document that the read returned is the document that the intent named. The read names the document of the write answer.	`$observed.document_readback.documentId`	`eq`	`$input.document_id`	`document_readback`
`revision_is_the_revision_of_this_write`	The document holds the revision that this batch update produced. The published schema states that a required revision identifier inside a response is the revision of the document after the request was applied.	`$observed.document_readback.revisionId`	`eq`	`$action.result.writeControl.requiredRevisionId`	`document_readback`
`revision_moved_from_the_base`	The revision differs from the revision that the agent read before the write. The published sentence states that an unchanged revision identifier means an unchanged document.	`$observed.document_readback.revisionId`	`ne`	`$input.base_revision_id`	`document_readback`

Which conditions give CONTRADICTED?

Condition	Class	Reason	Path	Operator	Expected
`document_subject_differs`	wrong subject	The agent changed a different document than the intent named.	`$observed.document_readback.documentId`	`ne`	`$input.document_id`

Which observed states map to a verdict before completion?

Rule	Match	Verdict	Reason
`document_moved_past_this_write`	(`$observed.document_readback.revisionId` ne `"$action.result.writeControl.requiredRevisionId"`) and (`$observed.document_readback.revisionId` ne `"$input.base_revision_id"`)	CONTRADICTED	The document holds a revision that this write did not produce. A second batch update or another person wrote after it. The Docs API states no idempotency key, so do not write again. Ask a person.
`revision_not_published`	`$observed.document_readback.revisionId` absent `undefined`	PENDING	The read carries no revision identifier. The published description states that the member needs edit access. Check the credential of the verifier.

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	600000 ms
Stale read window	20000 ms
On timeout	UNVERIFIABLE (`evidence_unavailable_before_timeout`), escalated to a person

Where do these rules come from?

google_docs.openapi#/paths/~1v1~1documents~1{documentId}:batchUpdate/post: google_docs.openapi, retrieved 2026-09-09
google_docs.openapi#/paths/~1v1~1documents~1{documentId}:batchUpdate/post/responses/200: google_docs.openapi, retrieved 2026-09-09
google_docs.openapi#/components/schemas/BatchUpdateDocumentResponse/properties/writeControl: google_docs.openapi, retrieved 2026-09-09
google_docs.openapi#/components/schemas/WriteControl/properties/requiredRevisionId: google_docs.openapi, retrieved 2026-09-09
google_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-09
google_docs.openapi#/components/schemas/Document/properties/documentId: google_docs.openapi, retrieved 2026-09-09
google_docs.openapi#/components/schemas/BatchUpdateDocumentResponse/properties/documentId: google_docs.openapi, retrieved 2026-09-09
google_docs.openapi#/components/schemas/Document/properties/revisionId: google_docs.openapi, retrieved 2026-09-09
google_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-09
google_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 minimum evidence level is E2. The action response is E1. The completion conditions read document_readback.

What happens after the timeout?

The verdict is UNVERIFIABLE with the reason evidence_unavailable_before_timeout. The operation goes to a person for review.