Skip to main content

Engine Integrations

DependencyAtlas keeps the default product path small and source-owned. Inference Query adds a separate query-time refinement layer, and 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 View contributes focused compiler-time graph 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 layers are not interchangeable frontends:

  1. DepAtlasSource defines the base graph identity.
  2. Inference Query reads a snapshot and returns query-time semantic refinement without mutating that snapshot.
  3. JET View creates an optional pure-JET view when explicitly requested.

The main graph stays source-owned. Inference Query results are artifacts and overlays, not graph identity. JET View is a focused companion view, not a competing graph-construction pass.

Inference Query​

Inference Query is the query-time semantic layer. Its job is to:

  • answer selected callsite, call edge, method, or expression-range questions
  • normalize provider results into one evidence shape
  • keep provider cost explicit
  • cache query artifacts outside the base snapshot
  • provide the stable API surface for future JET-backed and project-wide inference

The first provider is source_static. It only reads existing DepAtlasSource edge evidence from a snapshot. It does not load the project, run JET, or add new heuristics.

Future providers can be more expensive:

  • jet for selected interactive inference
  • project_overlay for explicit batch inference and coverage metrics

Those providers must be requested explicitly and remain outside the default analysis pipeline.