Foundation

The foundation section answers first-order questions about bijux-cli ownership: what it is, what it is not, where it fits in bijux-core, and which principles keep command behavior stable as the repository evolves.

Visual Summary

flowchart TD
    identity["Package identity"] --> boundaries["Ownership boundaries"]
    boundaries --> capability["Capability map"]
    capability --> lifecycle["Lifecycle model"]
    lifecycle --> principles["Change principles"]

What This Section Covers

• package role and runtime responsibility
• explicit non-goals and boundary limits
• repository fit and adjacency to DAG and dev tooling
• shared domain language used across source, tests, and docs
• lifecycle and change rules that reduce command-surface drift

Primary Code Anchors

• crates/bijux-cli/src/lib.rs
• crates/bijux-cli/src/api/mod.rs
• crates/bijux-cli/src/contracts/mod.rs
• crates/bijux-cli/src/routing/model.rs
• crates/bijux-cli/tests/architecture/

Pages In This Section

• Package Overview
• Scope and Non-Goals
• Ownership Boundary
• Repository Fit
• Capability Map
• Domain Language
• Lifecycle Overview
• Dependencies and Adjacencies
• Change Principles