Knowledge Base Export

{
  "metadata": {
    "title": "Alphiniti Knowledge Base",
    "version": "1.0",
    "lastUpdated": "March 2026",
    "description": "Comprehensive guide for support teams and end-users navigating the Alphiniti integrated platform"
  },
  "sections": [
    {
      "id": "quick-start",
      "title": "Quick Start",
      "icon": "🚀",
      "items": [
        {
          "title": "What is Alphiniti?",
          "audience": "enduser",
          "content": "Alphiniti is an integrated platform connecting five specialized applications to manage different aspects of your life: Path (life planning), HealthFlow (health records), Continuum (care continuity), Vitalis (wellness), and Money (financial management). Your data flows seamlessly between these apps through our 'hub & spoke' system."
        },
        {
          "title": "System Overview",
          "audience": "technical",
          "content": "Alphiniti uses a hub-and-spoke architecture where a central Hub database coordinates data across five spokes (Path, HealthFlow, Continuum, Vitalis, Money). The Sync Engine manages bidirectional synchronization, and a Reconciliation Service ensures data consistency. Real-time and scheduled sync modes are supported with automatic conflict resolution using 'newest wins' strategy."
        }
      ]
    },
    {
      "id": "architecture",
      "title": "System Architecture",
      "icon": "🏗️",
      "items": [
        {
          "title": "Hub & Spoke Model",
          "audience": "technical",
          "content": "The Hub is the central database storing authoritative data. Five Spokes (Path, HealthFlow, Continuum, Vitalis, Money) connect to the Hub. Data flow: User makes change in spoke → recorded in Hub → broadcast to all other spokes → reconciliation verification. Bidirectional sync allows data to flow Hub→Spoke (push) and Spoke→Hub (pull)."
        },
        {
          "title": "Sync Engine",
          "audience": "technical",
          "content": "Detects changes via polling/webhooks, validates data integrity, manages retry logic with exponential backoff (1s→2s→4s...→daily), and logs all transactions. On detection, changes are queued for broadcast with automatic retries on failure. Success rate target: >99%."
        },
        {
          "title": "Reconciliation Service",
          "audience": "technical",
          "content": "Runs every 6 hours automatically to verify data consistency. Compares checksums between hub and each spoke, identifies field-level discrepancies, triggers automatic re-syncs for mismatched records. Target: 0 discrepancies. Alert if >0.1% of records mismatch."
        }
      ]
    },
    {
      "id": "spokes",
      "title": "The Five Spokes",
      "icon": "🌐",
      "items": [
        {
          "title": "🗺️ Path (Life Planning)",
          "audience": "both",
          "content": "Purpose: Life planning, legacy planning, estate management. Features: Create life plans, document legacy wishes, manage digital estate, timeline tracking. Data synced: User profiles, life plans, legacy documents, care preferences. Support tip: Check last sync timestamp in sync status if data doesn't appear elsewhere."
        },
        {
          "title": "🏥 HealthFlow (Health Records)",
          "audience": "both",
          "content": "Purpose: Health records aggregation and care coordination. Features: Centralized health records, provider connections, lab results, care team communication. Data synced: Health metrics, medical history, provider access logs, care alerts. Known issue: Wearable integration can take 5-15 minutes to sync."
        },
        {
          "title": "🔗 Continuum (Care Transitions)",
          "audience": "both",
          "content": "Purpose: Care transitions and continuity management. Features: Transition planning, care coordinator tools, follow-up tracking, family updates. Data synced: Care plans, transition schedules, follow-up tasks, notifications. Technical note: Most frequent sync cycles due to time-sensitive nature."
        },
        {
          "title": "💚 Vitalis (Wellness)",
          "audience": "both",
          "content": "Purpose: Wellness tracking, health goals, preventive health. Features: Daily wellness tracking, health goals, wellness recommendations, habit tracking. Data synced: Wellness metrics, goal progress, activity logs, health insights."
        },
        {
          "title": "💰 Money (Financial)",
          "audience": "both",
          "content": "Purpose: Financial management and estate planning. Features: Financial accounts, net worth tracking, estate financial planning, expense categorization. Data synced: Account balances, transactions, financial goals, estate valuations. Security: End-to-end encrypted."
        }
      ]
    },
    {
      "id": "sync-management",
      "title": "Data Synchronization",
      "icon": "🔄",
      "items": [
        {
          "title": "How Sync Works",
          "audience": "both",
          "content": "5-step process: (1) Detection - system monitors for changes, (2) Staging - changes queued, (3) Broadcasting - Hub sends to spokes, (4) Delivery - spokes process updates, (5) Reconciliation - system verifies consistency. Typical time: <5 seconds for real-time sync."
        },
        {
          "title": "User Sync Settings",
          "audience": "enduser",
          "content": "Configure per app: Frequency (Real-time/Hourly/Daily/Weekly), Direction (Bidirectional/Push only/Pull only), Data types (enable/disable User Profile, Health Records, Life Plan, Financial Data, Care Alerts, Notifications). Use 'Sync Now' button to force immediate sync."
        },
        {
          "title": "Sync Status Indicators",
          "audience": "both",
          "content": "🟢 Healthy = Normal syncing, no action needed. 🟡 Degraded = Minor delays, monitor situation. 🔴 Offline = Spoke unavailable, contact support. Check via admin dashboard under Network Status."
        },
        {
          "title": "Technical Metrics",
          "audience": "technical",
          "content": "Throughput: Target 5-50/min normal (alert >1000/min). Success Rate: Target >99% (alert <95%). Latency: Target <5s (alert >30s). Reconciliation Gap: Target 0% (alert >0.1%). Monitor via Admin Hub → Analytics → Sync Metrics."
        }
      ]
    },
    {
      "id": "troubleshooting",
      "title": "Common Issues & Troubleshooting",
      "icon": "🔧",
      "items": [
        {
          "title": "Data Not Syncing to Another App",
          "audience": "both",
          "content": "User symptom: Updated info in Path but not showing in HealthFlow. Steps: (1) Check sync enabled in both apps, (2) Verify internet connection, (3) Review last sync timestamp, (4) Wait 30 seconds for real-time sync or click 'Sync Now', (5) Refresh the app. If still missing after 5 min, escalate. Technical: Check SyncHistory table for failed broadcasts, review SyncQueue for pending items."
        },
        {
          "title": "Sync Success Rate Below 80%",
          "audience": "technical",
          "content": "Impact: Frequent data mismatches. Diagnosis: (1) Identify failing spoke, (2) Review SyncHistory error logs, (3) Verify spoke API endpoint responds, (4) Check authentication tokens. Solution: Restart spoke, force reconciliation, review recent API changes. If persists >30 min, page DevOps."
        },
        {
          "title": "Duplicate Data After Sync",
          "audience": "both",
          "content": "Cause: Conflict resolution during bidirectional sync. Prevention: Set consistent timestamps, use push-only if one direction is primary, run reconciliation after bulk imports. Resolution: Manual reconciliation task, re-sync from authoritative source, or run deduplication script. Contact support if unsure which is authoritative."
        },
        {
          "title": "High Latency (>2 seconds)",
          "audience": "technical",
          "content": "Diagnosis: Check spoke throughput (<5ms/record target), database query performance, network connectivity, Hub CPU/memory. Solution: Implement caching, batch smaller syncs, schedule heavy ops off-peak, add read replicas. Escalate to backend team if persists."
        },
        {
          "title": "Spoke Goes Offline",
          "audience": "technical",
          "content": "Immediate actions: (1) Check spoke API health endpoint, (2) Verify network connectivity, (3) Check for recent deployments, (4) Review auth token validity. System response: Auto-queues syncs in SyncQueue table, retries exponentially for 24 hours, escalates after 24 hours. Check SyncFailureAlert table for logged issues."
        }
      ]
    },
    {
      "id": "faq",
      "title": "Frequently Asked Questions",
      "icon": "❓",
      "items": [
        {
          "title": "Will my data be lost if one app goes down? (End-User)",
          "audience": "enduser",
          "content": "No. Your data is stored safely in the Hub. All apps can access it when back online. We guarantee 99.9% data protection. Spokes act as local caches; the Hub is the source of truth."
        },
        {
          "title": "How long does it take for changes to sync? (End-User)",
          "audience": "enduser",
          "content": "Usually instantly with real-time sync. If you enable hourly sync, changes sync within 60 minutes. You can always click 'Sync Now' for immediate sync from your app settings."
        },
        {
          "title": "Can I disable sync for apps I don't use? (End-User)",
          "audience": "enduser",
          "content": "Yes! You can disable sync for any app. Only enable what you need. Your privacy settings are respected across all apps."
        },
        {
          "title": "What if two apps show different information? (End-User)",
          "audience": "enduser",
          "content": "The most recent change wins automatically. If unsure, update the correct app and it will sync to others within seconds. Our reconciliation system ensures consistency."
        },
        {
          "title": "How do I manually trigger a sync? (Technical)",
          "audience": "technical",
          "content": "Admin Dashboard → Network Status → Select spoke → Click 'Sync Now'. Use force sync only for troubleshooting. Normal sync is automatic and handles queuing/retries."
        },
        {
          "title": "What does 'newest wins' mean? (Technical)",
          "audience": "technical",
          "content": "If the same field is updated in two spokes simultaneously, the most recent update (by timestamp) is kept across all systems. Prevents data loss but overwrites the earlier change."
        },
        {
          "title": "How often should reconciliation run? (Technical)",
          "audience": "technical",
          "content": "Automatically every 6 hours. For critical data issues, manually run from Admin Hub. Expected discrepancies: <0.1% of records."
        },
        {
          "title": "What's the maximum throughput? (Technical)",
          "audience": "technical",
          "content": "Current capacity: 10,000 records/minute across all spokes. Alert if sustained throughput >1000/min on single spoke."
        }
      ]
    }
  ]
}