One database, not two: vector + graph in a single engine for ontology agents

If you’re building an ontology-driven agent, you’ve almost certainly run into the same architectural pattern: