Ownership Model

Ownership model ensures maintainer automation has explicit boundaries and does not silently absorb product runtime responsibilities.

Visual Summary

flowchart LR
    dev[bijux-dev ownership] --> suites[repo and contract suites]
    dev --> reports[evidence reporting]
    dev --> release[release automation]
    product[cli and dag ownership] --> runtime[product runtime behavior]

Ownership Rules

• bijux-dev owns governance automation and evidence orchestration
• CLI and DAG crates own product runtime behavior and user contracts
• shared policy updates require coordinated documentation across handbooks

Boundary Violations

• maintainer commands changing product behavior semantics
• product crates importing maintainer-only policy logic
• docs claims with no owning code anchor

Code Anchors

• crates/bijux-dev/src/lib.rs
• crates/bijux-dev/src/maintainer/
• crates/bijux-dev/src/suites/

Next Reads

• Change Control
• Contract Governance
• Core Package Ownership