Files
openclaw-ops/docs/google-workspace-sync.md

55 lines
1.4 KiB
Markdown

# Google Workspace Sync
## Purpose
Keep Claw's workspace project state synced with Google Tasks and Google Calendar.
## Current model
- `state/projects.json` = canonical structured sync state
- Google Tasks = actionable items
- Google Calendar (`Claw Ops`) = timed reminders / scheduled commitments
- Memory files = narrative context and decisions
## Google resources
### Calendar
- `Claw Ops`
### Task lists
- `Claw Inbox`
- `Claw Projects`
- `Claw Follow-ups`
- `Claw Waiting`
## Scripts
### Sync
```bash
python3 scripts/google-sync.py
```
What it does now:
- ensures project tasks exist for known projects
- ensures one next-action task exists per project
- syncs currently recognized future reminders into `Claw Ops`
### Drift audit
```bash
python3 scripts/google-drift-audit.py
```
What it reports:
- stale projects (14+ days since `last_activity_at`)
- projects missing next actions
- projects missing tasks
## Current limitations
- Reminder parsing is intentionally conservative
- Only currently recognized reminder patterns are auto-synced
- Missed-event -> task escalation policy is approved but not fully automated yet
- Email triage -> inbox/task/calendar transformation is not automated yet
## Next improvements
1. robust reminder registry with exact UTC timestamps
2. event/task dedupe beyond task-id presence
3. missed-event escalation into `Claw Follow-ups`
4. inbox triage pipeline from `claw@ben.io`
5. daily overview integration using drift-audit output