bijux-cli¶
bijux-cli is the public Rust runtime behind the bijux executable. It owns
command parsing, normalization, registry lookup, execution flow, plugin-facing
runtime behavior, and the REPL surface.
Use this page when the question is about runtime behavior of the command product itself rather than repository policy or Python distribution.
Responsibility Map¶
| Surface | Ownership |
|---|---|
| command routing | parser, registry, command catalog, and normalization |
| runtime behavior | config, history, memory, install diagnostics, plugins, and REPL state |
| output contract | deterministic help, envelopes, and stream formatting |
| boundary | does not own maintainer control-plane commands or DAG semantics |
Source Layout¶
crates/bijux-cli/src/apicrates/bijux-cli/src/bootstrapcrates/bijux-cli/src/contractscrates/bijux-cli/src/featurescrates/bijux-cli/src/infrastructurecrates/bijux-cli/src/interfacecrates/bijux-cli/src/kernelcrates/bijux-cli/src/routingcrates/bijux-cli/src/shared
Open Next¶
- open the CLI Handbook for architecture, interfaces, operations, and quality guidance
- open the Repository Handbook when a change crosses into DAG, maintainer, or repository governance concerns
- open
bijux-cli-pythonwhen the question is Python packaging, bridge parity, or launcher distribution
Code Anchors¶
crates/bijux-cli/README.mdcrates/bijux-cli/CHANGELOG.mdcrates/bijux-cli/src/bincrates/bijux-cli/tests/integration.rscrates/bijux-cli/tests/routing.rs
Review Lens¶
- runtime semantics should stay deterministic across binary and bridge entrypoints
- public command behavior should be explained in the CLI handbook, not hidden in tests
- maintainer-only concerns should not leak into this package boundary