Glossary · EVOI Proactive Injection

EVOI Proactive Injection.

Memories that volunteer before they're asked.

Direct answer

Expected Value of Information gating decides whether an unrequested memory earns its tokens: inject only when utility × relevance-probability ÷ token-cost clears a threshold. Without a gate, proactive memory is spam, every injection taxes attention. With EVOI, the agent surfaces the past fix exactly when the current intent makes it likely-relevant, and stays silent otherwise. Proactivity with a budget.

In Anvaya

How We Implement It.

01EVOI Proactive InjectionAnvaya's Proactive service scores candidates as u·P(rel|intent)/tokens > τ each turn, memory volunteers under threshold control, measured by injection utility.

Questions

Asked About EVOI Proactive Injection.

Q

Why gate proactive memory?

Every unsolicited token competes with task tokens. EVOI keeps the precision high: speak only when expected value beats cost.

Q

What feeds the relevance estimate?

Inferred session intent (bugfix, feature, refactor…) plus file, symbol, and recency signals, the same 9-signal relevance stack as retrieval.

Q

How is injection quality measured?

Mean injection utility (mind_stats): did injected nodes actually get used? The number should climb as the graph matures.

Run Agents That Fit On Your Laptop.

25.6 MB median RSS. 25 agents ran in parallel on a Core 2 Duo with 4 GB RAM. Hundreds on your machine. Zero cloud required on the Ollama path.

Requires Rust/cargo to build from source. Linux and macOS today, Windows not yet supported. Pre-1.0, public beta. Pricing TBD.