Prove that Drive holds the content of the file, and that the bytes match. A file resource that exists is not a file whose content arrived. This level compares the size and the checksum that Drive publishes.

Contract identity.
FactValue
Contract idgoogle_drive.file.content_stored
Version1.0.0
Hasha06dbef40106e525
Completion levelcontent_stored
PublisherBuilt and signed by Provely.
CertificationProvisional
SkillGoogle Drive API 0.1.0
Valid for provider API versionsv3.20260901

What is the intent?

Upload the content of the file into the folder without a change.

What is the subject and the action?

MemberValue
Subject typegoogle_drive.file
Canonical effectstorage.file_upload
Provider operationPOST /drive/v3/files
Idempotencynone, retry is not safe

Which false successes give CONTRADICTED?

  • duplicate side effect
  • other
  • partial completion
  • 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_drive.openapi#/components/schemas/File/properties/size: google_drive.openapi, retrieved 2026-09-09
  • google_drive.openapi#/components/schemas/File/properties/md5Checksum: google_drive.openapi, retrieved 2026-09-09
  • google_drive.docs.uploads#upload-file-data/upload-the-content: google_drive.docs.uploads, retrieved 2026-09-09
  • google_drive.docs.uploads#upload-file-data/resume-an-upload-that-broke: google_drive.docs.uploads, retrieved 2026-09-09
  • google_drive.openapi#/components/schemas/File/properties/id: google_drive.openapi, retrieved 2026-09-09
  • google_drive.openapi#/paths/~1drive~1v3~1files~1{fileId}/get/responses/200: google_drive.openapi, retrieved 2026-09-09
  • google_drive.openapi#/components/schemas/File/properties/name: google_drive.openapi, retrieved 2026-09-09
  • google_drive.openapi#/paths/~1drive~1v3~1files/post/requestBody: google_drive.openapi, retrieved 2026-09-09
  • google_drive.openapi#/components/schemas/File/properties/parents: google_drive.openapi, retrieved 2026-09-09
  • google_drive.openapi#/components/schemas/File/properties/createdTime: google_drive.openapi, retrieved 2026-09-09
  • google_drive.events#/events/drive.file.update.children: google_drive.events, retrieved 2026-09-09
  • google_drive.docs.push#push-notifications/the-changed-members: google_drive.docs.push, retrieved 2026-09-09
  • google_drive.openapi#/paths/~1drive~1v3~1files~1{fileId}~1watch/post: google_drive.openapi, retrieved 2026-09-09
  • google_drive.docs.uploads#upload-file-data/what-a-caller-cannot-read-from-these-pages: google_drive.docs.uploads, retrieved 2026-09-09

Can google_drive.file.content_stored 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 Drive API.

What happens after the timeout?

The verdict is UNVERIFIABLE. The operation goes to a person for review.