Tested offline
It validates fixture envelopes and metadata without signing in to Google or contacting Drive.
The Living Reach · Private Solaria utility
A small bridge, clearly marked.
The Solaria Mail Metadata Listing Adapter is being prepared for Gal’s owner-controlled Drive relay. This page explains what exists now, what Google access is proposed, and where the boundaries are.
Offline candidate · Google connection on hold
Current build
No live Google connection yet
The current build works only with saved, synthetic test responses marked OFFLINE_FIXTURE. It has no OAuth flow, network client, credential reader, file writer, scheduler, router, or state-store connection.
No file contents
Its proposed operation is metadata listing only. It is not designed to download documents, images, messages, or other file contents.
No Drive writes
It is not designed to create, change, move, delete, share, or mark files in Google Drive.
If Gal activates it later
Why Google metadata is requested
In this Solaria workflow, “mail” means an owner-only relay folder in Google Drive—not Gmail. The proposed adapter would use Drive’s files.list operation to identify items placed in the designated 00_To_Scotty relay folder and produce a local metadata listing for the owner’s workflow.
- File ID and name
- MIME type and parent
- Trash and shared status
- Owner email address
- File size when Google supplies it
An important distinction
The Google grant is broader than the relay folder
The proposed
drive.metadata.readonly permission is a restricted, account-wide metadata scope. The one-folder boundary is an additional check in Solaria’s code; it does not narrow the access Google grants. Connection remains on hold while authentication, local storage, retention, deletion, and revocation controls are reviewed and tested.
Plain-language records
Read the boundaries before any sign-in
The privacy page separates current behavior from planned behavior. The terms page explains the private, owner-only nature of this utility.