{"slug":"documentation/PLATFORM_FEATURES_COMPLETE","title":"IntegrateWise — Complete Platform Features","section":"documentation","sectionLabel":"Documentation","status":"unclassified","type":"document","path":"documentation/PLATFORM_FEATURES_COMPLETE.mdx","bytes":31185,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\n> A Knowledge Workspace over the Spine, powered by AI.\n> Everything the platform does, organized by layer.\n\n---\n\n## Canonical Internal Doctrine Guardrail\n\n- User Workbench = the single projection-native customer/product surface.\n- Twin = silent contextual AI Co-worker behavior inside the Workbench, not a\n  separate Workbench, panel or shell.\n- Governance = shared platform module and hard execution/promotion gate.\n- Neon = canonical tenant truth; D1/KV = bounded operational state; R2 =\n  evidence bytes.\n- When this doc uses public-facing language like \"Workbench\", interpret that internally as the User Workbench unless stated otherwise.\n- Twin runtime surfaces use the canonical Forest + Paper system language.\n- Midnight Executive is investor-deck / fundraising language only.\n\n---\n\n## 1. THE SPINE (Single Source of Truth)\n\nThe Spine is the canonical tenant data model. Connector data first enters the\nOperational Spine, is normalized, resolved and staged, and reaches canonical\ntruth only through promotion and Governed Spine Writers.\n\n### What it does\n\n- **Entity-based storage**: 150+ entity types in tenant-scoped entity tables;\n  department never determines a physical table namespace.\n- **Tenant isolation**: Row-Level Security on Spine DB. Workspace A cannot see Workspace B. Ever.\n- **Entity type routing**: Pipeline maps connector-native objects to canonical\n  entity contracts and records source bindings and lineage.\n- **Adaptive projections**: observed source fields are mapped through governed\n  field definitions; RBAC projections evolve without mutating the physical\n  schema per department.\n- **Audit trail**: Every write logged with source, timestamp, and trace ID.\n- **12 role/department projection configurations**: Customer Success, Sales,\n  Marketing, RevOps, Product Engineering, Finance, Support, Procurement, IT\n  Admin, BizOps, Education and Personal select curated views, KPIs, fields and\n  capabilities.\n- **Industry overlays**: industry context changes vocabulary, fields, KPIs,\n  recommended connectors and projection composition—not storage isolation.\n\n### Entity projections by department\n\nThe table below is a projection catalog. The listed entities remain tenant-level\ncanonical entities and may appear across departments when RBAC permits.\n\n| Department          | Entity Types | Examples                                                                                                          |\n| ------------------- | ------------ | ----------------------------------------------------------------------------------------------------------------- |\n| Customer Success    | 16           | account_master, success_plan, risk_register, engagement_log, renewal, stakeholder_outcome, initiative, capability |\n| Sales               | 12           | deal, opportunity, lead, pipeline_stage, quote, sales_sequence, call_log, competitor_intel                        |\n| Marketing           | 12           | campaign, audience, landing_page, email_campaign, social_post, ab_test, attribution_touchpoint                    |\n| RevOps              | 8            | quota, forecast, territory, comp_plan, revenue_metric, attribution, segment_rule                                  |\n| Product Engineering | 10           | feature, bug, sprint, release, repository, pull_request, deployment, roadmap_item, feedback                       |\n| Finance             | 12           | invoice, payment, expense, budget, revenue_entry, tax_filing, financial_report, vendor, cost_center               |\n| Support             | 8            | ticket, csat, sla_policy, escalation, queue, agent_performance, knowledge_article                                 |\n| IT Admin            | 12           | system, device, user, change_request, vulnerability, backup, certificate, network_device, license                 |\n| BizOps              | 6            | activity, workflow, okr, cross_dept_initiative, ops_metric                                                        |\n| Procurement         | 6            | purchase_order, spend_category, savings_initiative, approval_request, compliance_check                            |\n| Education           | 8            | student, course, assignment, grade, attendance, discussion, learning_objective, intervention                      |\n| Personal            | 4            | calendar_event, bookmark, daily_reflection, note                                                                  |\n\n---\n\n## 2. THE PIPELINE (8-Stage Normalizer)\n\nEvery record from every source passes through the same 8 stages. No shortcuts. No bypasses.\n\n### The 8 stages\n\n| Stage | Name                | What it does                                                               |\n| ----- | ------------------- | -------------------------------------------------------------------------- |\n| S1    | Analyze             | Detect entity type, resolve tenant schema, fingerprint data                |\n| S2    | Classify            | Assign category, priority, sensitivity level                               |\n| S3    | Filter              | Check entity type against tenant schema — reject if not allowed            |\n| S4    | Refine              | Normalize field names, split composite fields, extract cross-reference IDs |\n| S5    | Extract             | Map to canonical schema, keep only priority fields (schema-driven)         |\n| S6    | Validate            | Required field checks, type validation, integrity rules                    |\n| S7    | Sanity              | Anomaly detection, business rule validation (score must be ≥ 70 to pass)   |\n| S7.5  | Identity Resolution | Detect potential cross-source duplicates (never auto-merge)                |\n| S8    | Sectorize           | Route to correct Spine table, write canonical record, enqueue downstream   |\n\n### Pipeline features\n\n- **Retry with backoff**: Each stage retries 3 times with exponential backoff before sending to DLQ\n- **Dead Letter Queue**: Failed messages preserved with full context (stage, error, payload, trace ID)\n- **Idempotency**: Content-hash dedup keys prevent duplicate processing\n- **Version tracking**: Each entity gets a monotonic version number for conflict resolution\n- **Stage-level metrics**: Latency, throughput, and error rate tracked per stage\n- **Schema-driven extraction**: S5 only extracts fields defined in the tenant's schema — no data leakage\n\n---\n\n## 3. ENTITY 360 (Unified Data Surface)\n\nEntity 360 is the single API that assembles the complete picture of any entity. Twin reads ONLY from Entity 360 — never from scattered sources.\n\n### 6 layers assembled in parallel\n\n| Layer         | Source                          | What it contains                                                         |\n| ------------- | ------------------------------- | ------------------------------------------------------------------------ |\n| Truth         | Spine (Spine DB)                | Canonical entity data with freshness indicator (live/recent/stale)       |\n| Context       | Knowledge service               | Emails, documents, meeting notes, conversation summaries (Flow B)        |\n| Signals       | Signals table                   | Active alerts with severity, evidence chain, confidence score            |\n| Memory        | Knowledge consolidated_memories | AI-extracted knowledge: decisions, preferences, insights, rules (Flow C) |\n| Goals         | Goals table                     | Linked goals with progress, status, target dates, health scoring         |\n| Relationships | Entities table                  | Parent/child/related entity graph (account → contacts, etc.)             |\n\n### API\n\n```\nGET  /api/entity360/:id                    — single entity, all layers\nPOST /api/entity360                        — single with layer selection\nPOST /api/entity360/batch                  — multiple entities\nGET  /api/v1/cognitive/twin/360/:id        — entity + twin trigger insights\n```\n\n### Features\n\n- **Parallel fetch**: All 6 layers fetched simultaneously — assembly time < 200ms\n- **Layer selection**: Request only the layers you need (e.g. just truth + signals)\n- **KV cache**: 60-second TTL on Cloudflare KV for hot entities\n- **Freshness scoring**: Truth layer tagged as \"live\" (< 1h), \"recent\" (< 24h), or \"stale\" (> 24h)\n- **Source attribution**: Every data point traces back to its origin system\n- **Progressive hydration**: Profile loads first, context and signals load async\n\n---\n\n## 4. TWIN TRIGGER ENGINE (AI Reasoning)\n\nThe Twin evaluates Entity 360 data against a set of triggers to produce constrained, evidence-backed insights.\n\n### 10 triggers\n\n| Trigger             | Fires when                          | Severity             | Example output                        |\n| ------------------- | ----------------------------------- | -------------------- | ------------------------------------- |\n| health_drop         | Health score drops 15+ points       | Critical             | \"Acme health fell from 82 to 48\"      |\n| renewal_approaching | Renewal within 90/60/30 days        | Critical/High/Medium | \"Renewal in 32 days, health 48\"       |\n| engagement_drop     | No activity for 30+ days            | High/Medium          | \"No activity since March 2\"           |\n| arr_change          | ARR changes 10%+                    | High/Info            | \"ARR dropped 22% ($125K → $97K)\"      |\n| goal_at_risk        | Linked goal status = at_risk        | High                 | \"Goal 'API adoption' at 23% progress\" |\n| support_escalation  | 5+ open support tickets             | Critical/High        | \"8 open tickets, 3 are P1\"            |\n| stale_data          | Entity data older than 24h          | Medium               | \"Last sync: 3 days ago\"               |\n| memory_conflict     | 2+ low-confidence AI decisions      | Medium               | \"Conflicting memories about budget\"   |\n| context_gap         | High-value account, 0 context items | Medium               | \"$125K ARR, no emails or docs linked\" |\n| signal_cluster      | 3+ critical/high signals active     | Critical             | \"5 signals firing simultaneously\"     |\n\n### Guardrails\n\n- **Max 3 insights per entity per day** — prevents alert fatigue\n- **Severity-first sorting** — critical always surfaces before medium\n- **Evidence required** — no insight without at least 1 evidence item from Entity 360\n- **Four-question standard** — every insight answers: what happened, why it matters, what to do, what happens if ignored\n- **Source layer attribution** — every evidence item tagged with origin layer (truth/context/signals/memory/goals)\n- **Confidence scoring** — 0.60 to 0.95 based on evidence strength and source count\n\n---\n\n## 5. THREE DATA PATHS\n\n### Structured — Truth (CRM, billing, support → Spine)\n\n```\nConnector OAuth → Loader (creamy/full/delta) → Pipeline Queue → 8-Stage Normalizer → Spine\n```\n\n- Handles: accounts, contacts, deals, tickets, invoices, subscriptions\n- Sync modes: creamy (30 days), full (all history), delta (changes only), webhook (real-time)\n- All data becomes canonical truth in the Spine\n\n### Unstructured — Context (emails, docs, meetings → Spine + Knowledge)\n\n```\nConnector OAuth → Loader → Pipeline → Spine (metadata) + Knowledge (embeddings)\n```\n\n- Handles: Gmail, Slack, Teams, Notion, Google Drive, Dropbox, OneDrive, Calendly\n- Structured metadata goes to Spine, unstructured content goes to Knowledge for embedding\n- Feeds Entity 360 Context layer\n\n### AI Sessions — Approval-Based Personal Memory (reasoning → Knowledge only, NEVER Spine)\n\n```\nAI Source → D1 Buffer → Triage Bot → Confidence Scoring → Human Approval → Knowledge → Entity 360 Memory\n```\n\n- Handles: MCP, OpenAI, Claude, Moonshot, Grok, Gemini, any AI source\n- AI-generated content NEVER writes to Spine directly\n- Triage bot (Workers AI) extracts entities, sentiment, key facts\n- Auto-approve or HITL review based on flow_c_config rules\n- Only approved, verified knowledge enters the system\n- Rejected content is logged but never stored as fact\n- Approved content feeds Entity 360 Memory layer\n\n---\n\n## 5.1 APPROVAL-BASED PERSONAL MEMORY (No-Hallucination Memory)\n\nThe single most unique capability in IntegrateWise. No other platform has this.\n\n### The Problem\n\nTeams use multiple AIs (Claude, GPT, Grok, Gemini). Each AI:\n\n- Gives different answers to the same question\n- Doesn't remember what you told it last week\n- Hallucinates facts with no way to verify\n- Has no shared context with other AIs on your team\n\n### The Solution\n\nOne verified knowledge base. Every AI reads from it. No AI writes without approval.\n\n### How It Works\n\n```\nANY AI (Claude, GPT, Grok, Gemini, MCP, your own models)\n    │\n    ├── READ: Yes — all AIs read from Entity 360 Memory\n    │         (approved, verified knowledge only)\n    │\n    └── WRITE: Only through the approval gate\n              │\n              ├── AI generates insight/fact/decision\n              ├── Triage Bot extracts entities + scores confidence\n              ├── High confidence + trusted source → prioritized human review\n              ├── Low confidence or new source → review with evidence gaps\n              ├── Approved → enters Knowledge → feeds Entity 360 Memory\n              └── Rejected → logged but never stored as fact\n```\n\n### What Makes It Different\n\n| Approach                           | What it does                                                                            | Problem                                  |\n| ---------------------------------- | --------------------------------------------------------------------------------------- | ---------------------------------------- |\n| RAG (retrieval)                    | Fetches docs before generating                                                          | Still hallucinates — just with context   |\n| Grounding                          | Checks AI output against sources                                                        | Catches hallucinations after they happen |\n| **Approval-Based Personal Memory** | AI output goes through triage → scoring → human approval BEFORE entering knowledge base | Hallucinations never enter the system    |\n\n### Configuration (per tenant)\n\n```typescript\n{\n  trusted_sources: [\"claude\", \"system\"], // affects review priority only\n  min_confidence: 0.8,                   // review-priority threshold\n  max_priority_proposals_per_day: 50,    // rate limit\n  require_entity_link: true,             // must link to an entity\n  notifications: {\n    notify_on_auto_approve: true,\n    notify_on_triage: true\n  }\n}\n```\n\n### Results\n\n- Every AI on the team has the same verified context\n- Knowledge compounds over time — verified, not hallucinated\n- Switch AI providers anytime — the knowledge stays\n- Full audit trail on every piece of knowledge (who approved, when, from which AI)\n- Memory types: decision, preference, insight, action, rule, fact\n\n---\n\n## 6. IDENTITY RESOLUTION (S7.5)\n\nCross-source duplicate detection with human-in-the-loop resolution.\n\n### Detection (automatic, in pipeline)\n\n- Runs after S7 Sanity, before S8 Sectorize\n- Generates signature from identifying fields (email, domain, name, phone)\n- Queries for matches: same tenant + entity type + different source system\n- Supported types: account, contact, lead, ticket, opportunity, people_team\n- Entity ALWAYS written to Spine — detection is non-blocking\n\n### Matching confidence\n\n| Match type    | Confidence | Example                                                                         |\n| ------------- | ---------- | ------------------------------------------------------------------------------- |\n| Email exact   | 0.95       | john@acme.com from Salesforce = john@acme.com from Zendesk                      |\n| Domain + name | 0.80       | acme.com + \"Acme Corp\" from HubSpot = acme.com + \"Acme Corporation\" from Stripe |\n| Name + phone  | 0.75       | \"John Smith\" + +1-555-0123                                                      |\n| Domain only   | 0.50       | acme.com (low confidence, goes to HITL)                                         |\n\n### Resolution (human, via API or UI)\n\n- **Merge**: Combine two records into one canonical entity\n- **Keep Separate**: Mark as not duplicates, suppress future matching for this pair\n- **Defer**: Revisit later\n- Full audit trail on every resolution decision\n\n---\n\n## 7. GOVERN (Approval Gate)\n\nEvery autonomous action requires human approval. No exceptions.\n\n### What Govern gates\n\n- Entity merges (identity resolution)\n- Bulk field overrides\n- Action proposals from Twin\n- Connector disconnects\n- Schema changes\n\n### How it works\n\n1. Twin or system proposes an action\n2. Action created with status \"pending\"\n3. Routed to appropriate approver (workspace admin, CSM, compliance officer)\n4. Approver reviews evidence and approves/rejects with reason\n5. Approved actions execute via the standard write path\n6. Every decision logged to governance audit trail\n\n---\n\n## 8. TRUST LAYER\n\nEvery data point in the system carries provenance.\n\n### What's tracked\n\n- **Source system**: Which connector provided this data (Salesforce, Zendesk, etc.)\n- **Sync timestamp**: When this data was last synced\n- **Confidence score**: 0-1 score based on source reliability and data recency\n- **Freshness**: live (< 1h), recent (< 24h), stale (> 24h)\n- **Evidence chain**: For every Twin insight — which data points triggered it, from which layers\n\n### What's visible in UI\n\n- Source badges on every data field\n- Confidence percentage with color-coded bar\n- Evidence panel on every Twin insight (expandable)\n- \"Why this insight\" explanation with source flow visualization\n- \"Risk if ignored\" warning\n- Data freshness indicator on Entity 360\n\n---\n\n## 9. CONNECTORS (70+ integrations)\n\n### By category\n\n| Category      | Count | Connectors                                                                                 |\n| ------------- | ----- | ------------------------------------------------------------------------------------------ |\n| CRM           | 6     | Salesforce, HubSpot, Pipedrive, Zoho CRM, Freshsales, Close                                |\n| Support       | 9     | Zendesk, Freshdesk, Front, Help Scout, Intercom, Kustomer, WhatsApp Business, Crisp, Drift |\n| Billing       | 6     | Stripe, Chargebee, Paddle, QuickBooks, Xero, FreshBooks                                    |\n| Marketing     | 8     | HubSpot Marketing, Mailchimp, Marketo, Braze, Segment, SendGrid, Customer.io, Klaviyo      |\n| Analytics     | 6     | Google Analytics, Mixpanel, Amplitude, Heap, Tableau, Metabase                             |\n| Project       | 6     | Jira, Asana, Linear, Monday, ClickUp, Trello                                               |\n| Engineering   | 3     | GitHub, GitLab, Bitbucket                                                                  |\n| Commerce      | 3     | Shopify, WooCommerce, BigCommerce                                                          |\n| HR            | 1     | BambooHR                                                                                   |\n| Communication | 7     | Gmail, Outlook, Slack, Teams, Discord, Zoom, Google Calendar                               |\n| Productivity  | 6     | Notion, Google Drive, Dropbox, OneDrive, Airtable, Calendly                                |\n| AI            | 4     | MCP, OpenAI, Claude, Moonshot                                                              |\n| Design        | 1     | Figma                                                                                      |\n\n### Connector features\n\n- OAuth 2.0 / API key / OAuth 1.0 authentication\n- Automatic field mapping to canonical schema\n- Creamy load (30 days), full sync, delta sync, webhook ingestion\n- Rate limit handling with exponential backoff\n- Connector health monitoring (status, last sync, error count)\n- Domain-based filtering in UI (show only relevant connectors for department)\n\n---\n\n## 10. PRODUCT SURFACES\n\n### Account Success (Universal Product)\n\n**Accounts Hub** — Daily operating view for anyone managing accounts\n\n- Works for CSMs, CAs, hotel managers, freelancers, agency owners — anyone with accounts/clients\n- My Day cards: engagements today, tasks due, open risks, upcoming renewals/due dates\n- My KPIs: average health score, total value, account count\n- Health filter: all / healthy / at-risk / critical\n- Account list sorted by health score\n- AI signals section with Twin insights\n- Industry-adaptive: shows ARR for SaaS, invoice status for CAs, booking frequency for hospitality\n\n**Intelligence Center** — Portfolio management for managers and leaders\n\n- 6 KPIs: avg health, total value, at-risk value, upcoming renewals, open risks, AI signals\n- Health distribution bar (healthy / at-risk / critical with percentages)\n- Team performance table: owner name, accounts, avg health, value managed, at-risk count\n- Accounts needing attention (sorted by worst health)\n- Works for CS Directors, CA firm partners, hotel chain managers, school principals\n\n**Strategic View** — Executive dashboard for VP, C-suite, board\n\n- Big 4: total value, retention %, avg health, value renewing in 90d\n- Value by segment/industry horizontal bar chart\n- Initiative portfolio: active / blocked / total\n- At-risk accounts: health < 70 with upcoming renewals/due dates\n\n### Business Ops (Universal Product)\n\n**Ops Cockpit** — Daily operating view for founders and operators\n\n- 6 mini KPIs customized to business type (MRR/sales/revenue, pipeline, clients, deals, tasks, AI signals)\n- AI signals: \"What needs your attention\" section\n- Active deals/clients/projects sorted by value\n- Account/client health sorted by worst first\n- Works for SaaS founders, retail business owners, agency owners, freelancers\n\n**CEO View** — Company-wide dashboard\n\n- Big 4: revenue, pipeline, customers, OKR progress\n- Critical signals section\n- Strategic objectives with progress bars\n\n**COO View** — Operations command center\n\n- 6 ops KPIs: active workflows, initiatives, KPIs tracked, ops metrics, tasks done, ops signals\n- Cross-department initiatives with status badges\n- KPI tracker with progress bars\n\n**CIO/CTO View** — Technology dashboard\n\n- 4 tech KPIs: integrations, active incidents, tech metrics, tech signals\n- Integration landscape table: workflow name, status, execution count\n- Technology signals and metrics\n\n### Cross-Domain Features (all views)\n\n- **Content Router**: Every view lazy-loaded via module registry. 12 domain maps + BizOps cross-domain access.\n- **Progressive Hydration**: B0→B7 bucket system. Views render progressively as data arrives.\n- **Domain Sidebar**: Context-aware navigation that changes based on selected department.\n- **L2 Cognitive Overlay**: Twin insights, evidence panels, decision memory, drift detection — accessible from any view.\n- **Command Palette**: Quick navigation across all modules and domains.\n\n---\n\n## 11. REAL-TIME SYSTEM\n\n### Signal Stream (Durable Objects)\n\n- WebSocket/SSE for live signal delivery\n- Tenant-scoped broadcasting via SignalStreamDO\n- Signal filtering by severity, type, entity_type\n- Recent signals cache (100 max per tenant)\n\n### Presence Tracking\n\n- User online/away/busy status via PresenceDO\n- Cursor position sharing for collaboration\n- Room-based collaboration via RoomDO\n\n### HITL Gate (Durable Object)\n\n- HITLGate DO manages approval workflows\n- Real-time notification when approval is needed\n- Timeout handling for unresolved approvals\n\n---\n\n## 12. PROGRESSIVE HYDRATION (B0 → B7)\n\nThe system progressively activates capabilities as data flows in.\n\n| Bucket | State            | What's available                                         |\n| ------ | ---------------- | -------------------------------------------------------- |\n| B0     | No data          | Empty workspace, onboarding prompts                      |\n| B1     | Schema resolved  | Entity types known, empty views with structure           |\n| B2     | Creamy load done | 30 days of data, basic truth in Spine                    |\n| B3     | Full load done   | Complete historical data, all entity types populated     |\n| B4     | Context linked   | Flow B active — emails, docs, meetings in Entity 360     |\n| B5     | Signals active   | Twin triggers start firing, insights appear              |\n| B6     | Memory active    | Flow C feeding Entity 360, AI knowledge accumulating     |\n| B7     | Full cognitive   | All 6 Entity 360 layers operational, full Twin reasoning |\n\n---\n\n## 13. PLATFORM INFRASTRUCTURE\n\n### Services (21 Cloudflare Workers)\n\n| Service         | Port | Purpose                                                 |\n| --------------- | ---- | ------------------------------------------------------- |\n| Gateway         | 8786 | API routing, auth, CORS, rate limiting                  |\n| Spine-v2        | 8795 | Entity storage, Entity 360 API, Identity Resolution API |\n| Pipeline        | 8794 | Pipeline orchestration                                  |\n| Normalizer      | 8793 | 8-stage processing + S7.5 identity detection            |\n| Knowledge       | 8789 | Context storage, memory consolidation, triage bot       |\n| Think           | 8798 | Twin triggers, SignalEngine, AI reasoning               |\n| Act             | 8780 | Action execution                                        |\n| Govern          | 8787 | Approval workflows, policy enforcement                  |\n| Intelligence    | 8788 | Signal processing, Python AI client                     |\n| Workflow        | 8800 | Real-time signals, Durable Objects, presence            |\n| Connector       | 8785 | Connector management, sync scheduling                   |\n| Tenants         | 8797 | Tenant management, OAuth flows                          |\n| Billing         | 8783 | Subscription management, webhook replay                 |\n| Admin           | 8781 | Admin operations                                        |\n| Agents          | 8782 | Agent orchestration                                     |\n| L2              | 8790 | L2 cognitive insights                                   |\n| Loader          | 8791 | Data extraction from connectors                         |\n| Store           | 8796 | File storage (R2)                                       |\n| MCP Connector   | 8792 | MCP tool server                                         |\n| Webhook Ingress | 8799 | Inbound webhook processing                              |\n| HubSpot Sync    | 8784 | HubSpot-specific sync logic                             |\n\n### Storage\n\n- **Spine DB**: Primary database (PostgreSQL + RLS + Realtime + Auth)\n- **Cloudflare D1**: Edge cache for entity signatures, merge candidates, pipeline state\n- **Cloudflare KV**: Hot entity cache, session state, rate limits, signal cache\n- **Cloudflare R2**: File storage for documents, exports\n- **Cloudflare Queues**: Pipeline queue, knowledge queue, accelerator queue, intelligence queue, signal queue, DLQ\n\n### Security\n\n- Spine DB RLS enforces tenant isolation at database level\n- OAuth 2.0 with PKCE for connector authentication\n- Token encryption for stored credentials\n- Secrets Store for all sensitive configuration\n- Govern gate on all destructive operations\n- Full audit trail on every data change\n\n---\n\n## 14. SYNC ENTITLEMENTS (Plan-Based)\n\n| Capability        | Free   | Starter | Professional | Enterprise |\n| ----------------- | ------ | ------- | ------------ | ---------- |\n| Sync interval     | 24h    | 4h      | 1h           | 15min      |\n| Records per sync  | 1,000  | 5,000   | 25,000       | 100,000    |\n| Records per month | 10,000 | 50,000  | 500,000      | Unlimited  |\n| Historical days   | 30     | 90      | 365          | Unlimited  |\n| Max connectors    | 1      | 3       | 10           | Unlimited  |\n| Delta sync        | Yes    | Yes     | Yes          | Yes        |\n| Full refresh      | No     | Yes     | Yes          | Yes        |\n| Two-way sync      | No     | No      | Yes          | Yes        |\n| Webhooks          | No     | No      | Yes          | Yes        |\n\n---\n\n## 15. WHAT MAKES IT DIFFERENT\n\n| Capability                        | IntegrateWise                                                                              | Gainsight    | Totango      | CDPs                      | Internal dashboards |\n| --------------------------------- | ------------------------------------------------------------------------------------------ | ------------ | ------------ | ------------------------- | ------------------- |\n| Universal (any industry)          | Yes — SaaS, finance, hospitality, SMB, freelancers                                         | CS-only      | CS-only      | Marketing only            | Custom per team     |\n| Unified entity across all sources | Yes (Entity 360)                                                                           | Partial      | Partial      | Marketing only            | No                  |\n| Identity resolution               | S7.5 + HITL                                                                                | Manual       | Manual       | Yes but marketing-focused | No                  |\n| AI with evidence                  | Twin + trust layer                                                                         | Rules only   | Rules only   | No                        | No                  |\n| Approval-Based Personal Memory    | Yes — triage + approval gate, any AI reads verified knowledge, none write without approval | No           | No           | No                        | No                  |\n| Governed actions                  | Govern gate                                                                                | No           | No           | No                        | No                  |\n| Schema-driven (no manual config)  | 150+ types auto-routed                                                                     | Manual setup | Manual setup | Manual                    | Manual              |\n| Edge deployment                   | 300+ Cloudflare PoPs                                                                       | Cloud only   | Cloud only   | Cloud only                | Depends             |\n| Context (emails, docs)            | Unstructured path                                                                          | No           | No           | No                        | No                  |\n| Multi-AI support                  | Any AI reads from same verified knowledge                                                  | No           | No           | Single vendor             | No                  |\n| Multi-market pricing              | ₹999 to $999/mo                                                                            | $2,500/mo+   | $1,200/mo+   | $1,000/mo+                | Engineering cost    |\n| 70+ connectors out of box         | Yes                                                                                        | ~30          | ~20          | Varies                    | 0                   |\n"}