ProvelyNo. Google Drive API returns a success response when it accepts the request. Provely proves content_stored, created and granted as separate promises.
| Fact | Value |
|---|---|
| Skill version | 0.1.0 |
| Publisher | Built and signed by Provely. |
| Certification | Provisional |
| Last conformance run | 2026-09-05T12:00:00Z: 41 of 41 cases passed, 0 critical false VERIFIED |
| Provider API versions | v3.20260901 |
| Default provider API version | v3.20260901 |
| Compiled | 2026-09-05 |
| Manifest hash | 653fa6b461e7e6e6 |
| Manifest hash check | the document hashes to the value the manifest states |
| Signature | valid, key provely-skill-2026-09, trusted by this build |
What does this page prove?
| Claim | Proven by | Evidence | Status |
|---|---|---|---|
| A file resource that exists is not a file whose content arrived. This level compares the size and the checksum that Drive publishes. | google_drive.file.content_stored | E2 + E3 | proven |
| The record exists with the intended name in the intended folder. It does not prove that the content of the file arrived. | google_drive.file.created | E2 + E3 | proven |
| A permission that exists is not a permission for the right person. This level reads the address, the type and the role of the grantee. | google_drive.permission.granted | E3 | proven |
| An outcome outside Google Drive API, such as a bank credit or a person who read a message | not proven | no E5 channel | not proven |
| The meaning of a Google Drive API state that no source states | not proven | no source states it | not proven |
| The agent report that the action worked | never counts | E0 | not proven |
Which completion levels does the Google Drive API skill expose?
Each level is one promise with one contract. An agent picks the level that matches the promise it makes. It cannot upgrade a level. Read the completion level definition.
| Level | Contract | Promise | Evidence | Certification |
|---|---|---|---|---|
content_stored | google_drive.file.content_stored v1.0.0 | A file resource that exists is not a file whose content arrived. This level compares the size and the checksum that Drive publishes. | E2 + E3 | Provisional |
created | google_drive.file.created v1.0.0 | The record exists with the intended name in the intended folder. It does not prove that the content of the file arrived. | E2 + E3 | Provisional |
granted | google_drive.permission.granted v1.0.0 | A permission that exists is not a permission for the right person. This level reads the address, the type and the role of the grantee. | E3 | Provisional |
Which ways can a Google Drive API action look done and not be?
| Contract | Case | Verdict |
|---|---|---|
| google_drive.file.content_stored | duplicate side effect | CONTRADICTED |
| google_drive.file.content_stored | other | CONTRADICTED |
| google_drive.file.content_stored | partial completion | CONTRADICTED |
| google_drive.file.content_stored | pre existing state | CONTRADICTED |
| google_drive.file.content_stored | wrong subject | CONTRADICTED |
| google_drive.file.created | duplicate side effect | CONTRADICTED |
| google_drive.file.created | other | CONTRADICTED |
| google_drive.file.created | pre existing state | CONTRADICTED |
| google_drive.file.created | wrong subject | CONTRADICTED |
| google_drive.permission.granted | duplicate side effect | CONTRADICTED |
| google_drive.permission.granted | other | CONTRADICTED |
| google_drive.permission.granted | pre existing state | CONTRADICTED |
| google_drive.permission.granted | wrong subject | CONTRADICTED |
What did the last conformance run show?
The last conformance run on 2026-09-05T12:00:00Z passed 41 of 41 cases with 0 critical false VERIFIED. One critical false VERIFIED rejects a skill.
| Contract | Certification |
|---|---|
google_drive.file.content_stored | Provisional |
google_drive.file.created | Provisional |
google_drive.permission.granted | Provisional |
The weakest contract is google_drive.file.content_stored. It reaches Provisional. The package level is Provisional, because a package level never rises above its weakest contract. Read the level of the contract you use.
| Case class | Passed | Total |
|---|---|---|
| duplicate side effect | 3 | 3 |
| error after execution | 3 | 3 |
| error before execution | 3 | 3 |
| evidence unavailable | 3 | 3 |
| pre existing state | 3 | 3 |
| stale readback | 3 | 3 |
| still transitional | 3 | 3 |
| terminal success | 3 | 3 |
| timeout after commit | 3 | 3 |
| version mismatch | 3 | 3 |
| webhook duplicate | 3 | 3 |
| webhook out of order | 3 | 3 |
| wrong subject | 3 | 3 |
| wrong terminal state | 2 | 2 |
The conformance artifact digest is c1afe7a533b6e2fa. The harness signs the run, so a reader can check that these numbers come from that run.
What remains uncertain?
The level is Provisional because of it. Provely does not guess a rule that a source does not state.
Where do these facts come from?
Every claim above cites a source assertion in the skill provenance. The compiler records the source, its hash, and the retrieval date. A page never states a provider rule without one.
| Source | Kind | Retrieved | Excerpt |
|---|---|---|---|
| google_drive.docs.push | docs | 2026-09-09 | authored |
| google_drive.docs.sharing | docs | 2026-09-09 | authored |
| google_drive.docs.uploads | docs | 2026-09-09 | authored |
| google_drive.docs.versions | docs | 2026-09-09 | authored |
| google_drive.events | event sample | 2026-09-09 | authored |
| google_drive.openapi | openapi | 2026-09-09 | trimmed |
How do I verify a Google Drive API action?
Verify a Google Drive API action with Provely
- Begin the operation.Call
beginwith the contractgoogle_drive.file.content_storedand the input. Keep the operation id. - Make the Google Drive API call you make today.Send the request with the correlation metadata that
beginreturned. - Submit the acknowledgement.Call
action_resultwith the Google Drive API response. This is evidence level E1. It is not completion. - Verify.Call
verify. The runtime reads the evidence that the contract names, from Google Drive API and not from the agent, and evaluates the contract. - Report the verdict exactly as returned.VERIFIED comes with a signed receipt. PENDING comes with the operation id. CONTRADICTED and UNVERIFIABLE are not success.
Questions developers ask
Does the content_stored level prove the granted level?
No. A file resource that exists is not a file whose content arrived. This level compares the size and the checksum that Drive publishes. A permission that exists is not a permission for the right person. This level reads the address, the type and the role of the grantee. Use google_drive.permission.granted to prove granted.
What does the agent say while the Google Drive API action is still in progress?
It says: "The action is accepted but not yet verified. Operation: <id>." The verdict is PENDING. The runtime observes again on the contract timing policy.
Which Google Drive API API versions does the skill support?
v3.20260901. An operation on another version returns UNVERIFIABLE with the reason version_unsupported. The runtime never guesses.
Does Provely need write access to Google Drive API?
No. The agent keeps its write key. The verifier reads with a separate read-only credential where Google Drive API permits it, and it never shares that credential with the agent.