Scope and Non-Goals

Scope discipline keeps DAG claims trustworthy. This page makes explicit what bijux-dag must defend and what it does not promise.

Visual Summary

flowchart TB
    scope["in scope"] --> identity["graph run artifact identity"]
    scope --> classify["replay and diff classification"]
    scope --> evidence["inspectable evidence surfaces"]
    non_goals["non-goals"] --> orchestration["universal orchestration platform"]
    non_goals --> parity["universal backend equivalence"]
    non_goals --> policy["organization-wide compliance replacement"]

In Scope

• DAG model validity and canonical semantics
• deterministic run and artifact evidence surfaces
• replay and diff contract vocabularies (equivalent, drift, incomplete/unknown)
• bounded backend capability semantics and explicit downgrade handling

Non-Goals

• claiming equal behavior across all backends and environments
• masking missing evidence as successful equivalence
• collapsing graph/run/artifact scopes into one generic change signal
• replacing organization security/compliance policy systems

Code Anchors

• crates/bijux-dag-core/src/
• crates/bijux-dag-runtime/src/replay/
• crates/bijux-dag-app/src/routes/diff_routes.rs
• crates/bijux-dag-artifacts/src/integrity/

Next Reads

• Ownership Boundary
• Compatibility Commitments
• Known Limitations