Features Guide

Technical documentation for major T420 features

Version: 2.0 (Consolidated) Last Updated: 2026-01-08 Consolidated From: 6 feature docs (viral engine, agentic workflow, data persistence, relationship UX)

---

Table of Contents

1. Viral Growth Engine

2. Agentic Workflow System

3. Data Persistence Strategy

4. Relationship-First UX

---

1. Viral Growth Engine

Service: services/ViralTriggerEngine.ts

Viral Moments

Each moment is a psychological trigger for inviting others:

First Request (Joy/Relief)

• Trigger: Supplier's first service request arrives

• Emotion: "It works! This is real!"

• CTA: "Invite more fleet customers"

Momentum (Social Proof)

• Trigger: 3rd relationship added

• Emotion: "Others are using this, network is growing"

• CTA: "Invite suppliers in other categories"

Relief (Satisfaction)

• Trigger: Request completed smoothly

• Emotion: "Professional service delivery, no confusion"

• CTA: "Use FleetOS with more customers"

Today View (Active Use)

• Trigger: User returns to dashboard

• Emotion: "Staying organized, tracking everything"

• CTA: "Expand your network"

Implementation

// Track viral event
await ViralTriggerEngine.trackEvent({
  user_id: 'USER_123',
  event_type: 'first_request',
  event_data: { request_id: 'REQ_456' }
});

// Check if moment should fire
const shouldShow = await ViralTriggerEngine.shouldShowMoment(
  'USER_123',
  'momentum'
);

---

2. Agentic Workflow System

Components: components/robo-hub/agentic/*

Multi-Agent Architecture

Approval Agent

• Reviews supplier applications

• Checks credentials

• Approves/rejects with reasoning

Sourcing Agent

• Finds suppliers for requests

• Matches based on category, location, availability

• Suggests best fits

Fraud Agent

• Monitors for suspicious patterns

• Flags unusual requests

• Protects both sides

Supplier Agent

• Assists suppliers with quotes

• Suggests pricing based on market data

• Helps with response templates

Agent Flow

Request arrives
  ↓
Fraud Agent checks
  ↓
Sourcing Agent finds suppliers
  ↓
Notify suppliers
  ↓
Supplier Agent helps with quotes
  ↓
Approval Agent reviews quotes
  ↓
Present to fleet

---

3. Data Persistence Strategy

Storage Layers

1. Supabase (Primary)

• User accounts

• Relationships

• Service requests

• All structured data

2. localStorage (Session)

• UI state (current view, filters)

• Draft messages

• Temporary form data

3. IndexedDB (Planned)

• Offline support

• Message queue

• Cached queries

Sync Strategy

// Write to Supabase immediately
await supabase.from('service_requests').insert(request);

// Update localStorage for instant UI
localStorage.setItem('pending_requests', JSON.stringify([...existing, request]));

// Periodic sync
setInterval(() => {
  syncLocalToRemote();
}, 60000); // Every minute

---

4. Relationship-First UX

Philosophy

Competing with: Email & WhatsApp Must be: AS EASY or easier

Key Principles

1. Zero Signup for Recipients

• Fleet receives request

• Responds inline

• Only provides email if wants tracking link

2. Progressive Disclosure

• Show essential info first

• Advanced features behind "More" buttons

• Never overwhelm

3. Trust Through Facts

• No hype language

• Specific time savings ("Save 2-4 hours/day")

• Real metrics, not promises

4. Calm Infrastructure

• No red urgency badges

• No push notifications (WhatsApp only)

• Professional, reliable tone

UI Patterns

EmptyState: Standard empty state component Card: 4 variants (default, elevated, interactive, outlined) FilterBar: Consistent search/filter/sort Breadcrumb: Clear navigation

---

Related Documentation

• T420 Ecosystem Guide

• Development Guide

• Shared Guide

---

Version: 2.0 (Consolidated) Consolidated From: 6 feature documentation files (4,103 lines) Status: Core features implemented, some in design phase