The Task Fragmentation Problem
You create a task in Google Tasks. Your PM adds one in Asana. Sales logs one in the CRM. Support files a ticket in Zendesk. Now you have four systems, four inboxes, and zero visibility into what actually needs to get done.
This is the fundamental problem: tasks don't belong to apps. Tasks belong to people.
The Unified Task Layer
0nCore introduces a master unified_tasks table that becomes the single source of truth for every task in your business. Each task has a sources array — it can exist in Google Tasks AND your CRM AND Asana simultaneously.
The sync engine runs bidirectionally. Create a task in 0nCore → it appears in Google Tasks. Complete it in Google Tasks → 0nCore marks it done. The task is one entity, visible everywhere.
The Task Guardian
Every task gets an AI guardian that monitors three things:
- Stalled: No progress in 72 hours? Guardian flags it.
- Overdue: Past the due date? Guardian escalates.
- Recurring: Time for the next occurrence? Guardian spawns a new instance automatically.
The guardian runs on a cron schedule. It never sleeps. It never forgets. Your tasks are safe.
How It Works Technically
Each task stores its sync state in a JSONB sources array:
[{ "service": "google_tasks", "external_id": "abc123", "synced_at": "..." }]When the sync engine runs, it compares timestamps. Newer wins. Conflicts are logged in task_sync_log for audit. The guardian checks guardian_status (healthy, stalled, overdue) and acts accordingly.