bijux-dag-runtime¶

bijux-dag-runtime owns execution-time behavior for DAG runs: planning, scheduler policy, adapter invocation boundaries, artifact writing, replay, and runtime diagnostics.

Use this page when the question is about what happens after a graph has already been accepted as valid.

Responsibility Map¶

Surface	Ownership
execution engine	planning, scheduler behavior, backend invocation, replay semantics
runtime policy	policy evaluation, trace emission, error classification, capability checks
runtime artifacts	manifests, verification, cache lineage, and proof material
boundary	does not own authoritative DAG schema or user-facing CLI routing

Source Layout¶

crates/bijux-dag-runtime/src/runtime_core
crates/bijux-dag-runtime/src/adapters
crates/bijux-dag-runtime/src/backend
crates/bijux-dag-runtime/src/artifacts
crates/bijux-dag-runtime/src/cache
crates/bijux-dag-runtime/src/policy
crates/bijux-dag-runtime/src/replay
crates/bijux-dag-runtime/src/diagnostics

Open Next¶

open the DAG Handbook for the full DAG system map
open bijux-dag-core for graph truth and planning inputs
open bijux-dag-app for command orchestration and response shaping

Code Anchors¶

crates/bijux-dag-runtime/README.md
crates/bijux-dag-runtime/CONTRACT.md
crates/bijux-dag-runtime/src/lib.rs
crates/bijux-dag-runtime/src/policy/evaluator.rs
crates/bijux-dag-runtime/src/replay/verifier.rs

Review Lens¶

runtime policy should stay explicit, testable, and separate from graph definition
artifact and replay rules should be inspectable rather than hidden behind execution helpers
package ownership should remain focused on execution-time behavior only