Data Contracts

DAG data contracts cover graph definitions, execution plans, run traces, artifact indices, and replay/diff classifications.

Visual Summary

flowchart TD
    contracts[Data contracts]
    contracts --> inputs[input models]
    contracts --> plans[plan and execution models]
    contracts --> state[state and trace models]
    contracts --> results[result envelopes]
    contracts --> diagnostics[diagnostic models]

    results --> success[success envelope]
    results --> failure[failure envelope]

Contract Families

• graph model and validation diagnostics
• execution plan and scheduler state representations
• node outcomes, run summaries, and timeline events
• artifact metadata, integrity proofs, and lineage links
• replay/diff classification payloads and reason codes

Code Anchors

• crates/bijux-dag-core/src/graph/model.rs
• crates/bijux-dag-core/src/contracts/error.rs
• crates/bijux-dag-runtime/src/runtime_core/
• crates/bijux-dag-artifacts/src/storage/models.rs
• crates/bijux-dag-app/src/routes/response.rs

Contract Rules

• contract-bearing fields should stay explicit and test-covered
• identity-related field semantics require compatibility review
• classification states must remain machine-parseable

Next Reads

• Artifact Contracts
• Compatibility Commitments
• Invariants