Comments, suggested edits, and approvals in Google Docs are a fine loop when humans write and humans edit. The loop breaks when the author is an agent: it can't read the comments, the mock won't render in a doc, and the approval stops at the document's edge.
| Capability | Google Docs | Artifakt |
|---|---|---|
| What you review | Documents in Google's formats. Live app mocks, HTML pages, and interactive artifacts don't render. | Any artifact your agents produce, rendered live: docs, specs, interactive mocks, pages, decks. |
| Comment anchoring | Select text in the doc and comment. Solid for prose. | Click an element or select text in the rendered artifact — including a button in a running mock. |
| Who picks feedback up | A person reads the comments and edits, or accepts suggested edits by hand. | Any connected agent picks the round up over MCP and revises exactly the section the comment points at. |
| Approval | Docs approvals can lock a document once approvers accept. Scoped to Google's formats and workspace. | A named sign-off bound to the content hash of the version approved — for any artifact, from any agent, any vendor. |
| Enforcement | The doc locks. Nothing outside the doc is gated. | artifakt check blocks CI, publish webhooks hold a release, pending sign-offs route to Slack. |
| Agents learn | Comments teach the next human reader. | Rejection reasons become team rules; workspace guidelines are read by every agent before it revises; history exports as an eval set. |
A Docs approval locks a document. An Artifakt sign-off is a named, hash-bound event that your pipeline can enforce — CI stays red, the release holds, until someone on your team signs.