bijux-dag-core¶
bijux-dag-core owns the deterministic DAG kernel: graph types, parsing,
validation, canonicalization, topology, identity, parameter resolution, and
planner lowering primitives.
Use this page when the question is about graph truth before runtime side effects begin.
Responsibility Map¶
| Surface | Ownership |
|---|---|
| graph model | nodes, edges, resources, metadata, and canonical graph state |
| compile path | parse, validate, resolve, and build-contract wrappers |
| deterministic analysis | fingerprints, semantics, and topology |
| boundary | no scheduler orchestration, CLI routing, or persistence side effects |
Source Layout¶
crates/bijux-dag-core/src/graphcrates/bijux-dag-core/src/pipelinecrates/bijux-dag-core/src/analysiscrates/bijux-dag-core/src/buildcrates/bijux-dag-core/src/plannercrates/bijux-dag-core/src/contracts
Open Next¶
- open the DAG Handbook for cross-package architecture and operator-facing context
- open
bijux-dag-runtimewhen the question moves from graph truth to execution policy - open the Repository Handbook when the concern crosses into CLI or maintainer policy
Code Anchors¶
crates/bijux-dag-core/README.mdcrates/bijux-dag-core/CONTRACT.mdcrates/bijux-dag-core/src/lib.rscrates/bijux-dag-core/src/pipeline/validate.rscrates/bijux-dag-core/src/planner/planner.rs
Review Lens¶
- graph compilation should remain deterministic and side-effect free
- runtime or CLI concerns should not leak into the kernel layer
- package-local claims should map back to the DAG handbook when they affect the wider stack