## Thinking Path
> - Paperclip is the open source app people use to manage AI agents for
work
> - The built-in Google Workspace connector lets agents read and write
Gmail, Drive, Docs, Sheets, Slides and Calendar data
> - The connector stays behind an experimental setting until Google
approves its data access and the security assessment is accepted
> - The approval work has many steps, and the decisions behind them were
spread across chats and private notes
> - This pull request adds one checklist, one code-fix plan and one
temporary working-memory file for that effort
> - The benefit is that contributors and agents share one source for the
scope contract, the decisions and the remaining work
## Linked Issues or Issue Description
**Type of issue**
Missing documentation for an in-progress effort.
**Description**
The Google Workspace connector needs Google approval before it can go to
all users. There is no single document that lists what "approved and
released" means, which code changes must land before submission, or the
decisions taken so far (launch transport, owner, test instance, 14-scope
contract).
**Proposed change**
Add a production and approval checklist, a code-fix plan for section 2
of that checklist, and a temporary working-memory file. Keep
identifiers, credentials and review correspondence out of the public
repository.
## What Changed
- Added `doc/plans/2026-11-17-google-workspace-production-checklist.md`:
the "done means" criteria, the 14-scope contract, and checklists for
decisions, baseline, product and code, policy, security assessment,
reviewer environment, live acceptance, demo video, submission, release
and ongoing work.
- Added `doc/plans/2026-11-17-google-workspace-code-fixes.md`: ten
ordered code fixes (disclosure in the picker, scope lock to 14,
`gmail.modify` removal from the managed client, injection screening
check, revoke on last disconnect, retention audit, scan findings, gate
removal, REST-backed tool set, scope cleanup). Each item is marked
confirmed or to check.
- Added `doc/memory/google-connector-memory.md`: a temporary file with
decisions, open questions, environments, Google app layout, scopes,
review history and privacy-policy gaps. It says to delete it once the
connector is released.
## Verification
- Docs only. No code, schema or test changes.
- Read all three files before the push and confirmed that they contain
no passwords, client IDs, client secrets, project numbers or review
login codes.
- Relative links between the three files and to
`doc/connections/GOOGLE-WORKSPACE.md` resolve in the repository.
- CI checks on this PR.
## Risks
- Low risk. Documentation only.
- The plans describe intended work. Some items are marked "to check" and
can change after the code is traced.
- The working-memory file is temporary and must be deleted after
release.
## Model Used
- Claude Opus 5.5 (`claude-opus-5-5`, Anthropic), used through Claude
Code with tool use (shell, git, GitHub CLI) to commit the files and open
this PR.
## 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
- [ ] All Paperclip CI gates are green
- [ ] 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>