specific method · filed under software implementation
End-to-end lineage
DAG-based tracking surfaces the lineage of models or artifacts through inputs, runs, and artifacts in both directions.
- source
- 1
- model
- 1
- lab adopt it
- 1
- strongest
- core
How sources treat it
One count per evidence span, weakest treatment to strongest.
core 1
Documented in
Evidence
1 span quoted from the sources, strongest treatment first.
Maintaining a DAG of inputs, runs, and artifacts allows us to surface the complete lineage of any model or artifact in both directions
coresoftware implementationin Model FactoryPoolside
Filed alongside
Other methods under software implementation :: infrastructure service.
Automatic provider failoverCustom placement engineDeepSeek Elastic Compute (DSec)Dependency unificationDurable peer mailboxFresh-clone repository sanitizationHTTP/HTTPS sidecar proxyIn-house batch schedulerIncremental sandbox checkpointing and resumptionLocal container-image cachingModel FactoryMooncakeNeMo GuardrailsNeMo SwitchyardPer-node pooling of initialization actorsRayReplacing short-lived Ray actors with tasksSandbox pause and resumeVendoring external dependenciesWrite-ahead logZ3 SMT solver integration