Dependency Direction

Dependency direction keeps program behavior stable by enforcing which crates may depend on which layers.

Visual Summary

flowchart LR
    cli[bijux-cli] --> core_contracts[workspace contracts]
    dag_app[bijux-dag-app] --> dag_core[bijux-dag-core]
    dag_app --> dag_runtime[bijux-dag-runtime]
    dag_runtime --> dag_artifacts[bijux-dag-artifacts]
    dev[bijux-dev] --> cli
    dev --> dag_app
    py[bijux-cli-python] --> cli

Direction Rules

• product crates must not depend on maintainer-only crates
• maintainer crate may depend on product contracts for verification
• DAG app/runtime/core/artifacts keep DAG-local boundaries explicit
• Python bridge depends on runtime surfaces and does not redefine contracts

Violation Signals

• runtime crate importing maintainer-specific modules
• DAG core importing app-route modules
• duplicate policy logic in multiple binary entrypoints

Code Anchors

• crates/bijux-cli/Cargo.toml
• crates/bijux-dag-app/Cargo.toml
• crates/bijux-dag-runtime/Cargo.toml
• crates/bijux-dev/Cargo.toml

Next Reads

• Maintainer Control Plane
• Testing and Validation
• Change Management