## Thinking Path
> - Paperclip is the open source app people use to manage AI agents for
work
> - The built-in Google Workspace connector is going through Google's
restricted-scope review
> - Three docs track that work: the working memory, the production
checklist and the code-fix plan
> - Four pull requests merged on November 17 and one more is open, so
the docs are out of date
> - This pull request updates the three docs to match the merged work
and the Cloud audit results
> - The benefit is one current place for decisions, scopes, shipped work
and open questions
## Linked Issues or Issue Description
Refs #21996, #21998, #21999, #22000, #22001
**Issue type**
Outdated documentation.
**Where is the issue?**
`doc/memory/google-connector-memory.md`,
`doc/plans/2026-11-17-google-workspace-production-checklist.md` and
`doc/plans/2026-11-17-google-workspace-code-fixes.md`.
**What's wrong?**
The docs describe fixes 1 to 4 as not done. They plan a new npm package
for the REST tool set, but the tool set is a folder inside the server.
The scope table is in two files. The docs do not record the Cloud broker
audit or where Google content is kept.
**Suggested fix**
Record what shipped, add the new decisions, keep one scope table, add
the broker and data-retention findings (marked as reported), and tick
the checklist items that are now true.
## What Changed
- Working memory: three new decisions (no new npm packages, the scope
handling contract, agents merge their PRs on the coordinator's approval
at green checks and Greptile 5/5).
- Working memory: new "What has shipped" table (#21996, #21998, #21999,
#22001 and #22000, with merged commits).
- Working memory: the single copy of the 14-scope table. "Known
mismatches" now lists only what is still true after #22001.
- Working memory: new "Cloud broker (paperclip-cloud)" and "Where Google
content is kept" sections, from the November 17 read-only audit, marked
as reported and not re-verified.
- Working memory: how to create the staging tester, its two obstacles,
and two new open decisions with a recommendation.
- Working memory: the privacy policy draft location and what it must
also cover (the OpenRouter screening model and the picker's retention
statement).
- Working memory: a note that the ponytail reviewer flagged the summary
of Google's reply. The summary stays.
- Checklist: the scope table is now one sentence with a link. Four
product items are ticked with date and PR link. Items that are not fully
true stay unticked.
- Code-fix plan: fixes 1 to 4 marked done with PR links. Section 9
layout is now the folder inside the server. Two one-line lessons.
Section 10 lists the broker changes and the deploy order.
## Verification
- Each fact was checked against `gh pr view` for #21996, #21998, #21999,
#22000 and #22001, and against
`packages/shared/src/google-workspace-connectors.ts` and
`server/src/services/tool-access/oauth/grant-refresh.ts` on
`origin/master`.
- The broker and data-retention facts come from an audit that this PR
does not re-verify. The docs say so.
- Searched the changed files for client IDs, secrets and project
numbers: none.
- Docs only. No tests apply.
## Risks
- Low risk. Docs only. No code or behavior changes.
> For core feature work, check [`ROADMAP.md`](ROADMAP.md) first and
discuss it in `#dev` before opening the PR. Feature PRs that overlap
with planned core work may need to be redirected — check the roadmap
first. See `CONTRIBUTING.md`.
## Model Used
- Claude Opus 5.5 (`claude-opus-5-5`), Anthropic, in Claude Code with
tool use (shell, file edits, GitHub CLI).
## Checklist
- [x] I have included a thinking path that traces from project context
to this change
- [x] I have specified the model used (with version and capability
details)
- [x] I have checked ROADMAP.md and confirmed this PR does not duplicate
planned core work
- [x] I have searched GitHub for duplicate or related PRs and linked
them above
- [x] I have either (a) linked existing issues with `Fixes: #` / `Closes
#` / `Refs #` OR (b) described the issue in-PR following the relevant
issue template
- [x] I have not referenced internal/instance-local Paperclip issues or
links (only public GitHub `#NNN` / `github.com/paperclipai/paperclip`
URLs)
- [x] My branch name describes the change (e.g. `docs/...`, `fix/...`)
and contains no internal Paperclip ticket id or instance-derived details
- [x] I have run tests locally and they pass
- [x] I have added or updated tests where applicable
- [x] I have updated relevant documentation to reflect my changes
- [x] I have considered and documented any risks above
- [x] All Paperclip CI gates are green
- [x] Greptile is 5/5 with no open P2s, recommendations, or follow-ups
- [x] I will address all Greptile and reviewer comments before
requesting merge
🤖 Generated with [Claude Code](https://claude.com/claude-code)
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>