Vulpine as of 2026-11-14: the frontends on your screens and in your rooms; the Rust Voice Gateway, speech recognition, the voice and the optional decision model on a Mac in the house; your agent and its tools beside it
Guided views
Explore this system
Step through curated paths without changing the source diagram.
Beat
Next
ReadyChapter 01 / 01
Guided chapter
Diagram guideExplore this system
Inspecting compiled semantics
E ExportT ThemeS Style0 Reset+ Zoom in- Zoom outEsc Close
Find a node
⌕/
No matching nodes
Semantic passport
Verified source
Authored reach
Route probeChoose a start node
Pick two semantic nodes on the diagram
Choose the source, then the destination. Direction matters.
Semantic lensCompare system roles
Choose up to two semantic kinds. One reveals its real traffic; two compare only direct authored relationships.
Choose a kind to inspect its nodes and touching relationships.
Semantic radar
Building overview
Click nodeDrag to pan
Who owns what
• The gateway owns sessions, turns and speech; it never calls a model itself
• A verb turn is settled by the gateway from its own list; every other turn goes to your agent
• Your agent owns reasoning, model access, tools and MCP servers
Integration seam
• Adapters keep upstream names and credentials; the gateway sees Vulpine's subjects
• roomctl speaks in rooms, homectl streams house events and acts on subjects
• fleetctl checks your hosts; visionctl reads a camera frame
What stays home
• Speech recognition and the voice run on the gateway host
• The gateway listens on loopback; Vulpine Gateway.app uses a socket only your account opens
• Only a turn's text goes to a hosted model, when your agent uses one
Architecture diagram • Built with Archify • Create yours ↗ • Hover to trace • R route • Click to focus • +/− zoom • M radar • [/] views • P play story • T theme • E export