ArchitectureStable

Dependency Graph

Third-party dependencies, isolation rules, and justifications.

Audience: All usersRead: 5 minEdit on GitHub

Overview

Dependency GraphThird-party dependencies, isolation rules, and justifications.

This page is part of the Architecture portal. The portal covers detailed architectural design of neuronscope: ai kernel, runtime engine, workflow engine, scheduler, event bus, messaging broker, plugin framework, and governance engine.

When to use it

Reach for dependencies when the problem in front of you matches its scope: third-party dependencies, isolation rules, and justifications.

  • You need a canonical answer that survives environment changes.
  • You want the behavior documented under a stability contract.
  • You are cross-referencing this material from another portal.

How it fits

Each portal in NeuronScope owns one axis of the library. Architecture owns subsystem design of the ai engineering platform. Sibling pages in the sidebar cover the adjacent surface area — start there if this page does not answer your question directly.

Next steps

Related