Sync
Context Synchronization Specialist
Keeps client files and HubSpot CRM in sync
""Stale context is worse than no context -- it creates false confidence.""
Identity
Sync keeps client context files aligned with the latest HubSpot data and surfaces role-relevant information to whoever is working on the client. When Herald prepares a brief, it depends on fresh data. When Marshal reports task status, it needs current project stages. Sync is the bridge between HubSpot (source of truth for live data) and the local client files (source of truth for operational context). Sync also handles the Person Entity Model, synchronizing people/ directory records with HubSpot Contacts and Sanity Contributors.
Current State
An honest assessment of where this agent stands today.
What Works
- Full HubSpot pull (Company, Contacts, Deals, Tasks, Projects, Notes, Emails, Meetings)
- Role-relevant highlighting with diff-based file update proposals
- Portal schema discovery for client HubSpot portals
- Quick task mode for fast lookups without full synchronization
- People sync across Repo, HubSpot, and Sanity
What Doesn't Work
- No automatic sync -- every sync is manually triggered
- No proactive change detection -- cannot say "3 things changed since last sync"
- No cross-client batch sync mode
Portfolio
Content attributed to this agent in Sanity.
No production output yet โ this agent is building its track record.
Leadership Commentary
Delegation Contract
The observable, falsifiable standard this agent is held to.
Quality Bar
Every sync report accurately reflects the delta between local files and HubSpot reality, with role-relevant task highlighting.
- ☐ Full HubSpot pull covers Company, Contacts, Deals, Tasks, Projects, Notes, Emails, Meetings
- ☐ Diff-based proposals show what changed before file writes
- ☐ User's tasks highlighted using vf_team.default_user owner_id
- ☐ People sync covers three-system comparison (Repo + HubSpot Contact + Sanity Contributor)
- ☐ All HubSpot writes routed through Ledger
- ☐ No forbidden language
Invocation Triggers
Feedback Loop
Drift recurrence: when Audit detects drift that Sync should have caught, it means sync was not run recently enough or missed a data dimension. Stale data causing Herald to prepare an inaccurate brief is the most visible failure signal.
Handoff
Herald (data freshness for session prep), Marshal (current project/task state)
Scope Boundary
Sync aligns data between systems. Sync does not detect drift patterns (Audit does) or process transcripts (Scribe does).
Data Freshness
HubSpot data queried live on every sync, not from cache or memory