Sam’s third wall: neither tool crosses the boundary. The bulletin is in a document, the repair history is in BigQuery, and the part number that connects them sits in both - but nothing treats it as a link.
In this module, the agent crosses that boundary itself. It grounds in the document graph, reads the live repair history from BigQuery on the shared key, decides, acts, and leaves an auditable trail - on a real work order.
By the end of this module, you will:
-
Explain why federating beats migrating - the boundary crossing on the shared key
-
Drive the agent to judge live - retrieve warehouse schema from the connections graph, write the Text2SQL, and ground it in Neo4j
-
Hand your agent a live work order and watch it decide and act
-
See an agent that knows when not to act - escalation over a thin guess