Skip to main content

Engines

DependencyAtlas has one default product engine and one optional deep-dive engine:

  • DepAtlasSource for source-first structural extraction
  • JET for on-demand compiler-time call evidence

They do not compete for graph identity. DepAtlasSource owns the main snapshot. JET produces a separate cached result view from a selected method node.

What Each Engine Owns​

DepAtlasSource

  • owns the base graph identity
  • defines file/module/method structure
  • lowers JuliaSyntax facts into typed structure and call facts
  • contributes the first layer of call evidence

JET

  • runs only when you explicitly request it from a selected method node
  • is entrypoint-driven rather than repo-structure-driven
  • produces a pure JET result graph instead of mutating the main snapshot

How To Read The Two Views​

Use the main graph when you need:

  • project ownership
  • file/module/method structure
  • source-visible call relationships
  • stable graph navigation

Use a JET view when you need:

  • compiler-time evidence for one selected method
  • a focused entrypoint-driven call graph
  • diagnostics tied to that entrypoint

The useful comparison is not “which engine wins?” but “which question am I asking?”

Missing Evidence Does Not Always Mean “No Relationship”​

Examples:

  • a source-first pass may only produce a dynamic or possible edge
  • a JET view only covers the selected entrypoint and reachable compile-time path

So the useful question is usually:

  • what evidence do I have?
  • what evidence do I not have yet?
  • which view is expected to provide that evidence?

Practical Interpretation Heuristic​

  • Start with the main DepAtlasSource graph for navigation and ownership.
  • Run JET only when a selected method needs compiler-time evidence.
  • Keep the two results semantically separate: main graph for source-owned structure, JET view for focused compiler-time evidence.