Skip to content

Bijux Core

License: Apache-2.0 CI Docs Crates Publish PyPI Publish Release GHCR packages Published packages

bijux-cli bijux-cli bijux-cli

Repository docs bijux-cli docs bijux-cli docs.rs

bijux-core is a deliberately split workspace for command runtime, deterministic DAG execution, and repository control-plane work. The split is the design, not a packaging afterthought. Readers should be able to see where authority changes hands before they start reading source files or workflow logs.

Start here when you need repository-level orientation. The job of this page is to show which handbook branch owns the current question, which package family likely carries the implementation, and which repository-only surfaces sit above the product handbooks.

Start with ownership, not just the crate list. Repository docs explain cross-workspace policy. CLI docs own the bijux command product and Python bridge. DAG docs own graph truth, runtime policy, artifacts, and DAG command orchestration. Maintainer docs own release proof, repository gates, and governance tooling.

Repository

Use the repository handbook when the question crosses package boundaries, release policy, or shared ownership rules.

CLI

Use the CLI handbook for command semantics, runtime behavior, plugin surfaces, REPL behavior, and Python distribution.

DAG

Use the DAG handbook for graph compilation, execution, replay, artifacts, and DAG command workflows.

Maintainer

Use the maintainer handbook for repository diagnostics, evidence collection, release verification, and policy enforcement.

Open the repository handbook Open the CLI handbook Open the DAG handbook Open the maintainer handbook

Visual Summary

flowchart TB
    page["Bijux Core<br/>clarifies: repository handbook | product handbooks | maintainer handbook"]
    classDef page fill:#dbeafe,stroke:#1d4ed8,color:#1e3a8a,stroke-width:2px;
    classDef anchor fill:#ede9fe,stroke:#7c3aed,color:#4c1d95;
    classDef action fill:#fef3c7,stroke:#d97706,color:#7c2d12;
    anchor1["why the workspace is split"]
    anchor2["which handbook branch owns the question"]
    anchor3["which package family carries the implementation"]
    anchor4["which concerns stay at the repository root"]
    anchor1 --> page
    anchor2 --> page
    anchor3 --> page
    anchor4 --> page
    next1["repository handbook"]
    next2["CLI or DAG handbook"]
    next3["maintainer handbook"]
    page --> next1
    page --> next2
    page --> next3
    class page page;
    class anchor1,anchor2,anchor3,anchor4 anchor;
    class next1,next2,next3 action;

Start Here

  • open Repository Handbook when the issue spans CLI, DAG, and maintainer ownership or touches release policy
  • open CLI Handbook for the bijux command product and its Python bridge
  • open DAG Handbook for graph truth, runtime policy, artifacts, replay, and DAG command behavior
  • open Maintainer Handbook for repository gates, diagnostics, docs verification, and release proof

Package Flow

Handbook Package destinations Use it when
Repository Handbook Repository Packages the question is about workspace scope, release policy, or cross-package ownership
CLI Handbook bijux-cli, bijux-cli-python the issue is command behavior, runtime routing, REPL semantics, or Python distribution
DAG Handbook bijux-dag-core, bijux-dag-runtime, bijux-dag-app, bijux-dag-cli, bijux-dag-artifacts, bijux-dag-testkit the issue is graph, execution, replay, artifacts, or DAG command behavior
Maintainer Handbook bijux-dev the issue is repository diagnostics, release proof, or control-plane automation

Documentation Scope

Start from the handbook that owns the question, then use its package tabs when you need the exact implementation boundary. If two handbook branches seem to own the same behavior, treat that as a docs bug and verify the answer from the Repository Handbook.

Purpose

Use this page to get oriented quickly, choose the right handbook branch, and move to the checked-in files that carry the detailed proof.

Stability

Keep this page aligned with the published handbook roots, the current workspace package split, and the repository-only surfaces that actually exist in bijux-core.