MirevoxGitHub (opens in a new tab)

Module 06 · AI data paths

runnable

Data Lineage

Show where an AI request was meant to go.

View on GitHub (opens in a new tab)

Runnable v0.1 slice available on GitHub — architecture and scope below.

Problem

Once a prompt crosses a gateway, it can be hard to explain which provider, region, model, or internal service handled it. Existing lineage tools cover data estates well, but AI request paths often need a smaller, trace-linked view.

Where it sits

Sits beside Smart Router and records the intended path of AI-bound data. It is an add-on to model traffic, not another LLM or a replacement for a broader data catalog.

Data Lineage is designed to follow requests already passing through Smart Router. Using request and trace IDs, it can show the selected route, referenced provider location, model target, and policy that informed the decision.

This is evidence of routing intent and observed hops, not a blanket residency guarantee. OpenMetadata, Atlan, or another catalog can remain the broader system of record; this module is meant to add the AI request path those systems may not capture directly. Tooling value is the add-on—not a new foundation model.

How it fits

Data Lineage observes the same Smart Router path as Evals: one explains where a request went, while the other records how it scored against evaluation and policy rules. The control plane hub can place both beside the route without turning them into one coupled service.

Capabilities