Meeting Resources

Kevin Platform

Simple explanations through full technical deep-dives. Start anywhere — the first three cards are all you need.

What Is Kevin?

Three ideas. That's all.
01

A family of agents, each with one job

Kevin is 14 AI agents — Walt orchestrates, Mona watches, Max runs hardware, Vera remembers, and so on. Every agent owns exactly one responsibility. No overlap, no confusion.

02

They share a real-time data bus

Every agent publishes and subscribes on a shared message bus. When something happens — a sensor fires, a command arrives, a model outputs — every relevant agent knows immediately. No polling. No delays.

03

You give one command. It routes itself.

Send a message to any entry point — BLE, MQTT, HTTP, serial. The routing layer figures out which agents need to act. You don't manage agent-to-agent wiring. Kevin does.

The Family

14 agents — click any video to play
Orchestrator
Walt
Makes the plan and delegates every step.
Observability
Mona
Fleet-wide visibility. Knows when anything breaks.
Infrastructure
Kevin
Core platform — the shared bus everyone rides.
Memory
Vera
Persistent knowledge base. She remembers everything.
Research
Norm
Nightly knowledge refresh. Finds what's new.
Hardware
Max
ESP32 firmware. Runs on the actual device.
Keystore
Hank
Reactive key-value store. Every key is subscribable.
Dashboard
Chip
Fleet UI. Real-time charts, live device data.
Routing Layer
Lattice
Connects Kevin to the outside world.
Viewport
Marco
Ops dashboard. Bus widgets, library, live metrics.
Auth & Permissions
Grant
Token model, namespace scopes, entitlements.
Agent Bridge
Annie
Routes LLM queries to the right model and domain.
Tensor Core
RAT
Recursive Associative Tensor. Finds the hidden pattern.
Family Elder
Rick
Self-improving process. The loop that made Kevin possible.

Platform Diagrams

Tap any diagram to expand
Kevin Family
The Kevin Family
All 14 agents at a glance
Deployment
Deployment Topology
Where everything lives — VPS + local
Firmware
Firmware — Max
ESP32-S3 HAL → Mx → App layers
MQTT
The Message Bus
MQTT topics, publishers, subscribers
Hank
Hank — Reactive Keystore
Write + subscribe paths
Dashboard
Chip — Fleet Dashboard
React + ECharts + MQTT + InfluxDB
Knowledge
Knowledge Engine
RAG router · ChromaDB · Vera · Norm
Products
Customer Products
NuTruCalc · VIAI · ask.viai.club
Websites
Websites Layer
DNS → Caddy → backend routing
▶
System Data Flows — Animated
Marco → Daemon → Carousel → Worker → Dashboard
▶
Firmware Data Flows — Animated
Max (ESP32-S3) — Boot, Tasks, Telemetry
▶
End-to-End Data Flows — Animated
Device → MQTT → Daemon → Carousel → Worker → Result

Listen & Watch

AI-generated explainers — add via media_pipeline.py add

No explainers yet — run python tools/marco/media_pipeline.py add <file> --topic "..." to add the first one.

Architecture

Detailed reference is private — request access
Architecture Reference (private) 27 documents · request access via contact