ProvelyNo. Google Docs API returns a success response when it accepts the request. Provely proves text_replaced and update_applied 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: 22 of 22 cases passed, 0 critical false VERIFIED |
| Provider API versions | v1.20260902 |
| Default provider API version | v1.20260902 |
| Compiled | 2026-09-05 |
| Manifest hash | ab666762d202e381 |
| 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 batch update that landed is not one that reached its promise. This level reads the text runs of every tab against the confirmed text. | google_docs.document.text_replaced | E2 | proven |
| The document that the person named holds the revision that this update produced. This level does not prove what the update changed. | google_docs.document.update_applied | E2 | proven |
| An outcome outside Google Docs API, such as a bank credit or a person who read a message | not proven | no E5 channel | not proven |
| The agent report that the action worked | never counts | E0 | not proven |
Which completion levels does the Google Docs 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 |
|---|---|---|---|---|
text_replaced | google_docs.document.text_replaced v1.0.0 | A batch update that landed is not one that reached its promise. This level reads the text runs of every tab against the confirmed text. | E2 | Provisional |
update_applied | google_docs.document.update_applied v1.0.0 | The document that the person named holds the revision that this update produced. This level does not prove what the update changed. | E2 | Provisional |
Which ways can a Google Docs API action look done and not be?
| Contract | Case | Verdict |
|---|---|---|
| google_docs.document.text_replaced | wrong subject | CONTRADICTED |
| google_docs.document.update_applied | wrong subject | CONTRADICTED |
What did the last conformance run show?
The last conformance run on 2026-09-05T12:00:00Z passed 22 of 22 cases with 0 critical false VERIFIED. One critical false VERIFIED rejects a skill.
| Contract | Certification |
|---|---|
google_docs.document.text_replaced | Provisional |
google_docs.document.update_applied | Provisional |
The weakest contract is google_docs.document.text_replaced. 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 | 2 | 2 |
| error after execution | 2 | 2 |
| error before execution | 2 | 2 |
| evidence unavailable | 2 | 2 |
| pre existing state | 2 | 2 |
| stale readback | 2 | 2 |
| still transitional | 2 | 2 |
| terminal success | 2 | 2 |
| timeout after commit | 2 | 2 |
| version mismatch | 2 | 2 |
| wrong subject | 2 | 2 |
The conformance artifact digest is 45a9e667907800e3. 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_docs.docs.batch | docs | 2026-09-09 | authored |
| google_docs.docs.versions | docs | 2026-09-09 | authored |
| google_docs.docs.write_control | docs | 2026-09-09 | authored |
| google_docs.openapi | openapi | 2026-09-09 | trimmed |
How do I verify a Google Docs API action?
Verify a Google Docs API action with Provely
- Begin the operation.Call
beginwith the contractgoogle_docs.document.text_replacedand the input. Keep the operation id. - Make the Google Docs API call you make today.Send the request with the correlation metadata that
beginreturned. - Submit the acknowledgement.Call
action_resultwith the Google Docs 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 Docs 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 text_replaced level prove the update_applied level?
No. A batch update that landed is not one that reached its promise. This level reads the text runs of every tab against the confirmed text. The document that the person named holds the revision that this update produced. This level does not prove what the update changed. Use google_docs.document.update_applied to prove update_applied.
What does the agent say while the Google Docs 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 Docs API API versions does the skill support?
v1.20260902. An operation on another version returns UNVERIFIABLE with the reason version_unsupported. The runtime never guesses.
Does Provely need write access to Google Docs API?
No. The agent keeps its write key. The verifier reads with a separate read-only credential where Google Docs API permits it, and it never shares that credential with the agent.