gworkspace-mcp

Cross-service coordination in Google Workspace uses two-phase commit to enforce atomic transactions across Gmail, Drive, Calendar, Docs, Sheets, Tasks, and Meet. This Skill orchestrates replay-deterministic workflows with temporal consistency checkpoints, ensuring all services commit or roll back together for data integrity.

Temporal consistency enforces causal ordering and replay determinism across services using a poset framework. It ensures that multi-service workflows execute reliably in the same order every time, preventing race conditions and data conflicts when coordinating Gmail messages, calendar events, and document updates simultaneously.

This Skill provides robust error recovery using GF(3)-driven retry semantics with 1069 checkpoints for failure detection and restart. When a service fails mid-transaction, the system replays deterministically from the last checkpoint, restoring consistency across all Google Workspace services without data loss.

Yes. This Skill builds cross-service workflows that coordinate Gmail messages, calendar events, and Drive/Docs updates as a single atomic transaction. It applies GF(3) triadic reasoning to classify actions as PLUS, ERGODIC, or MINUS, balancing the workflow while enforcing global consistency.

Configure the MCP server with a ruler.toml file containing GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, and GF3_SEED parameters. Once configured, use tools like gmail_list, calendar_create, and tasks_create to build and execute coordinated multi-service workflows with consistency guarantees.

ANIMA condensation reaches fixed points like Inbox Zero or Task Zero, creating stable end-states for multi-service workflows. It ensures that coordinated Gmail, Calendar, and Tasks actions converge to a consistent, clean state after execution completes.