bijux-core

bijux-core is split on purpose. Repository governance, CLI behavior, DAG runtime behavior, and maintainer automation are separate handbooks so each surface stays reviewable and stable.

This landing page is for fast routing by task, not by crate name memory.

Visual Summary

flowchart LR
    question[what do you need to do] --> repo[repository policy and boundaries]
    question --> cli[cli runtime behavior and command semantics]
    question --> dag[dag graph run replay and diff behavior]
    question --> dev[maintainer verification and release operations]

Handbooks

• Repository Handbook
• CLI Handbook
• DAG Handbook
• Maintainer Handbook

Start Here

• Use Repository Handbook when the question crosses CLI/DAG boundaries or touches shared contracts.
• Use CLI Handbook for operator-facing command behavior.
• Use DAG Handbook for graph, run, replay, and artifact semantics.
• Use Maintainer Handbook for maintainer-only automation and release workflow operations.

Task Routing Matrix

If you need to...	Start here	Why
understand repository-wide ownership and release policy	Repository Handbook	it owns cross-program contracts and governance
troubleshoot or change CLI command behavior	CLI Handbook	it owns CLI interfaces, operations, and quality contracts
troubleshoot DAG validate/run/replay/diff behavior	DAG Handbook	it owns DAG architecture, interfaces, and operations policy
run maintainership gates or release workflows	Maintainer Handbook	it owns maintainer command surfaces and governance controls

Navigation Rule

When a question affects more than one handbook, start from Repository Handbook and then follow its cross-links to program-specific pages.