The cross-module answer engine for enterprise data. Ask one question that spans Vendor, PO, BOM, WorkOrder, SalesOrder, Customer and Revenue — get an answer where every figure came from a graph walk, and the proof comes with it.
walking graph … 5 modules · 240 nodes ──────────────────────────────────────────── ⚠ 3 SalesOrders at risk · $1.2M revenue SO-4471 Acme ships -9d $480K SO-4490 Initech ships -4d $310K SO-4502 Umbrella ships -6d $410K proof: PO-882 → BOM-31 → WO-77 → SO-4471 decision #a91f · grounded · 0 invented
A single question that touches seven modules at once. Where the ERP's own one-table assistant gives up, answeryard starts.
question "which commitments slip?" │ ▼ parse typed GraphQuery, validated ▼ traverse cost-bounded BFS · no hop cap ▼ score heterogeneous GNN · risk/node ▼ narrate plain English · 0 invented │ ▼ answer + proof + Decision#
Traversal depth is a property of the question, not a hardcoded hop count. Patterns declare which edges to follow; the graph and the question pick how deep.
agent ▸ tool answeryard_query { "question": "which POs threaten Q3 revenue?", "app_id": "erp-prod" } ← grounded answer · traversal proof · decision id
MCP-first. Anything reachable in the UI is reachable as an agent tool — call it from neo, Copilot, Agentforce, or your own agent. Answeryard is a tool, not a destination.