Project Atlas AetherDev project hub
Atlas project pilot

Google Groups Guard

Provide a deterministic Rust plan/apply CLI for Google Group membership and settings reconciliation, with guardrails and service-style deployment options.

Internal-only entry. Do not publish externally without review.
Type
Component
Lifecycle
Pilot
Last touched
2026-03-25
Visibility
Internal

Purpose

Document the candidate successor tool for Google Group reconciliation without confusing it for the already confirmed GAM-based district production workflow.

Current state

Workbench evidence confirms this tool is operationally mature enough for guarded plan/apply workflows and can be deployed with service-style scheduling support, but Atlas still does not have confirmation that it is the authoritative production runner for district group enforcement.

Next step

Record an explicit runtime decision: replacement, parallel shadow run, or targeted-scope utility; then publish host ownership, scheduler/service definition, and rollback governance.

Interfaces

Inputs
  • group configuration
  • service-account credentials
  • directory and group state
Outputs
  • plan artifacts
  • group membership changes
  • settings updates

Reality to Action trace

Reality Ingestion

Not in scope.

Canonical Storage

Not in scope.

Automation Engines

Not in scope.

Human Interfaces

Contributes in this stage.

Operational Adoption

Contributes in this stage.

Core workflow

TBD. Document the 5-10 steps that define the core workflow.

Data integrity and contracts

Source of truth rules

  • Google Directory and group settings remain canonical for runtime state.
  • Stored plan artifacts are audit outputs and should not become the source of truth for group policy.

Safe handling

  • Keep service-account keys and stored plans out of public docs.
  • Limit plan/apply usage to approved administrators.
  • Document cutover criteria before treating this as a production replacement.

Operational notes

Reliability posture

The CLI has strong guardrails (plan/apply semantics and artifacted reconciliation), but the registry does not yet confirm it as the canonical production runner.

Observability

  • structured CLI logs
  • plan and summary artifacts
  • optional notifications

Security and privacy

Service-account credentials, plan artifacts, and group membership data remain sensitive and should stay internal.

Dependencies

Upstream
  • Google Admin Directory API
  • Google Groups Settings API
Downstream
  • future group-governance workflows
  • possible successor to GAM maintenance scripts

Ownership

Owners

Josh Barton

Users

Technology Services

Google Groups Guard

Operational Notes

  • This page intentionally documents the candidate Rust successor, not the confirmed live district runner. The registry still points to the GAM-based Google Workspace Group Membership Maintenance Automation as the production enforcement path.
  • The value here is modernization: plan/apply workflows, structured reconciliation artifacts, and safer cutover potential than ad hoc script editing. That matters even before a full cutover is approved.
  • Treat deployment status as unresolved until there is a clear decision on whether this CLI replaces, shadows, or merely supplements the GAM runner.

Registry Alignment

  • Related registry entries: INT-076, INT-072.
  • Registry clarified: this tool is part of the active cross-repo implementation story for group governance, but strongest day-to-day production evidence still points to GAM-based scripts such as Push-GoogleGroupsModify.sh.
  • Validation gaps: deployment scope, cutover decision, operational owner, and retained role in district admin work remain unresolved.