System Overview¶
bijux-core is a single Rust workspace that hosts runtime programs, DAG
execution crates, a Python bridge package, and a maintainer control-plane.
Visual Summary¶
flowchart LR
user[user and automation] --> cli[bijux cli program]
user --> dag[bijux dag program]
cli --> runtime[cli runtime crate]
dag --> dag_app[dag app and runtime crates]
runtime --> shared[shared workspace contracts]
dag_app --> shared
maintainer[maintainer workflows] --> dev[bijux-dev control plane]
dev --> shared
System Components¶
crates/bijux-cliowns CLI runtime behaviorcrates/bijux-dag-*owns DAG execution, replay, diff, and artifactscrates/bijux-cli-pythonowns Python packaging and bridge integrationcrates/bijux-devowns maintainer-only diagnostics and governance workflows
Architectural Boundary¶
- runtime behavior belongs to CLI and DAG program crates
- repository policy and release evidence belong to maintainer workflows
- shared workspace policy belongs to root manifests, configs, and make targets
Non-Goals¶
- this page does not define command-by-command CLI behavior
- this page does not redefine DAG runtime semantics already owned by DAG docs
- this page does not replace executable contract and test evidence
Boundary Smells¶
- adding maintainer-only logic into user runtime crates
- changing product behavior through repository scripts without crate-level review
- documenting cross-program policy without linking owning code anchors
Code Anchors¶
Cargo.tomlcrates/bijux-cli/src/lib.rscrates/bijux-dag-app/src/lib.rscrates/bijux-dev/src/lib.rs