architecture-reference

To map package dependencies and build order in a monorepo, visualize the package dependency graph to identify core, llm-provider, and higher layers, ensuring CI and local builds run in the correct phased sequence.

Kernel phase pipelines and extension points define the architecture's reasoning flow, allowing contributors to extend reasoning or tooling by integrating provider and MCP components according to specific integration rules.

To integrate MCP components with an llm-provider, follow the documented integration patterns and provider streaming rules to safely connect tooling and reasoning layers within the monorepo architecture.

Yes, the architecture reference supports planning safe refactoring by providing a navigable package dependency graph that clarifies which packages depend on core and higher layers to prevent build mistakes.

You need to verify the correct build phase before adding a new package to ensure that CI and local builds execute in the correct dependency order, preventing runtime failures and onboarding friction.