gog Safety Profiles

Build and deploy gog binaries with compile-time command removal. Commands that are disabled don't exist in the binary — no runtime bypass possible.

Quick Start

1. Choose a safety level

For full details: INLINECODE1

2. Build

CODEBLOCK0

Requires: Go 1.22+, git. First run clones the PR #366 branch (~30s).

3. Deploy

CODEBLOCK1

The deploy script:

• - Backs up the existing gog as INLINECODE3
• Installs the new binary
• Verifies version output
• Optionally tests that blocked commands are gone and allowed commands work

4. Rollback

CODEBLOCK2

How It Works

Uses gogcli's compile-time safety profiles feature (PR #366 on steipete/gogcli). A YAML file specifies which commands are enabled (true) or removed (false). The build system generates Go source files with only the enabled commands, then compiles. The resulting binary's version is tagged with -safe.

YAML Profiles

In references/:

• - l1-draft.yaml — Draft & Organize
• INLINECODE10 — Draft & Collaborate
• INLINECODE11 — Full Write (No Admin)

Custom profiles: copy any YAML, edit the true/false flags, pass to build-gog-safe.sh.

Verification

After deployment, verify with:
CODEBLOCK3

Known Edge Cases

• - Filter forwarding: gmail settings filters create is allowed at L1+ for inbox organization. A filter with a forward action could auto-forward email. Accepted risk for v1.
• Drive sharing: drive share is allowed at L1+ because sharing grants access without sending a message notification. The shared user sees it in "Shared with me" but doesn't get an email.