Extensibility Model

DAG extensibility centers on adapter boundaries and capability negotiation, not on unrestricted runtime mutation.

Visual Summary

flowchart LR
    request["planned node execution"] --> registry["adapter registry lookup"]
    registry --> capability["capability negotiation"]
    capability --> execute["adapter execution contract"]
    execute --> normalize["normalized runtime outcome"]

Extensibility Surfaces

• adapter SDK and plugin contract descriptors
• backend capability descriptors and negotiation policies
• extension catalog and compatibility issue detection
• simulated-platform quarantined surfaces for non-stable experiments

Code Anchors

• crates/bijux-dag-runtime/src/adapters/sdk.rs
• crates/bijux-dag-runtime/src/adapters/registry.rs
• crates/bijux-dag-runtime/src/backend/capability.rs
• crates/bijux-dag-runtime/src/internal/ext/extension_catalog.rs
• crates/bijux-dag-runtime/src/simulated_platform.rs

Extensibility Constraints

• extensions must not bypass core semantic contracts
• capability downgrade must remain explicit and observable
• unstable platform simulations must stay out of stable root behavior

Next Reads

• Artifact Contracts
• Security and Safety
• Known Limitations