Field note 02 / private assistant tooling
Rock-Gog is the second DaD-Labs field note.
The second note moves from public shop infrastructure into the private tooling bench: a Google OAuth helper that lets Rock, the local DaD-Labs assistant, reach a dedicated operator-controlled mailbox without turning personal accounts into shared plumbing.
Rock-Gog is not a product launch. It is a narrow, private integration built for one job: give the local assistant a clean Google consent surface for a dedicated assistant mailbox. That makes it a good DaD-Labs field note because it shows the same practical discipline as the first note: scoped access, plain documentation, and boring operational boundaries.
OAuth app details
Operator: the DaD-Labs owner. App name on Google's consent screen: Rock-Gog. Intended account: a dedicated assistant mailbox controlled by the operator. Intended user: the operator and the local assistant environment they administer.
Verification documents are kept at stable public URLs: privacy policy and terms of service.
Why this belongs here
The first field note documented Surfadillo as a public web and shop surface. Rock-Gog is the other side of the bench: the internal tool that supports a small operation without pretending to be a platform. OAuth consent pages, privacy copy, terms, account boundaries, and permission scopes are not glamorous, but they decide whether an assistant integration is trustworthy enough to keep.
The app name on Google's consent screen is Rock-Gog. The intended user is the DaD-Labs owner. The first intended permission path is read-only Gmail access for the assistant mailbox so Rock can check mail when asked. Calendar or other Google services are added only if the operator turns them on later.
What it does
After the operator signs in with Google and grants permission, Rock-Gog lets the local assistant use the Google APIs that have been explicitly enabled. It keeps the public-facing brand work separate from the private assistant workflow, while still giving Google and future operators a clear home page, privacy policy, and terms of service.
What it does not do
It does not sell access. It does not show ads. It does not create Google accounts for the public. Other people should not sign into this app.
For the formal consent-screen documents, read the privacy policy and terms of service.