Annie is the neighbor who always knows who to ask. She lives next door — not a family member, but deeply wired in. Every query that comes into the Kevin platform gets routed through Annie. She reads the question, picks the right LLM for the job, and retrieves the right knowledge before she hands it off.
Annie doesn't answer questions herself. She's the router — the one who knows that a therapy note goes to the psychology corpus, a firmware question goes to the technical domain, and a legal clause goes to Trixie. She makes the right call, every time, fast.
Annie chooses between local and cloud models based on cost, latency, and what the question needs. Speed when it matters, price when it doesn't.
Every question goes to the domain expert. Psychology notes, firmware docs, legal files — Annie knows where to look.
Annie pulls the relevant knowledge first, so the answer is grounded in something real. Every answer traces back to where it came from.
Need to ask about a specific PDF? Upload it. Ask questions. It's gone when the session ends. No clutter.
When you add a document to a domain, future queries benefit. Build knowledge that compounds.
Annie works from Marco, from your CLI, from any tool that understands her protocol. Same routing everywhere.