Skip to main content

Engine Integrations

DependencyAtlas keeps the default product path small and source-owned. JET remains available as an explicit compile-time view when engineers need deeper evidence for one selected method.

DepAtlasSource​

DepAtlasSource is the source-first frontend. Its job is to:

  • parse files with JuliaSyntax
  • lower syntax facts into typed structure and call facts
  • build the canonical base graph identity
  • preserve Julia-specific extension semantics through overload metadata
  • provide the first layer of call evidence

Strengths:

  • stable file/module/method identity
  • direct control over ownership and lowering
  • fast project-wide analysis without requiring compiler-time entrypoints

Limits:

  • call extraction is still intentionally lighter than full semantic resolution
  • some call targets may remain possible or dynamic when source-visible evidence is not enough

JET​

JET contributes focused compiler-time evidence. It is used for:

  • on-demand call graphs from selected method nodes
  • diagnostics and report-based evidence for that entrypoint
  • deeper inspection when the source graph is not precise enough

Strengths:

  • compile-time perspective
  • useful when source-visible evidence is not enough

Limits:

  • entrypoint-driven
  • not a replacement for the source-first graph
  • produces a separate cached view rather than modifying the main snapshot

Evidence Model​

These engines are not interchangeable frontends:

  1. DepAtlasSource defines the base graph identity.
  2. JET creates an optional pure-JET view when explicitly requested.

The main graph stays source-owned. JET is a focused companion view, not a competing graph-construction pass.