An example of how Jason uses his agents today. Hermes and Grok Bot are peer interfaces into the same secure context layer: the Obsidian vault as source of truth, GBrain as search. Neither is primary or fallback. Grok Bot is the voice-facing interface. The desks below are the running agents. Everything on this page runs on Jason’s development server, shown on test data only; it is the demonstration harness, not the proposed Milano Bro deployment.
Vault is the curated, human-readable truth (Jason Vault). GBrain is the machine-searchable archive over that corpus. Agents read here; they do not keep a second brain.
Agent runtime and mission-control harness. Equal peer to Grok Bot on the same context layer. Hermes for Mario is proposed on this pattern; that proposal has not been built.
Voice-facing interface. Jason uses Grok Bot because its voice interface is the best available. Same vault and GBrain as Hermes; chat and voice to the desks.
Priorities, routing, side-effect pause.
Granola ops: markets, kitchen, inventory.
MGC schedule, launches, client ops.
Consulting, clients, brand.
Personal and business accounting.
Labs, daily framework, routines.
Esther Miszer / Esther Homeo corpus.
Demo ≠ proposal. This chart is an example of how Jason uses his agents: Jason’s own setup on Jason’s development server, shown on test data only. The proposed design for Mario, an AI model running inside a Milano Bro cloud account on the same context-layer pattern, has not been built, connected, or security-reviewed. It is a proposal for discussion.