Change Control

Change control governs how maintainer automation evolves without destabilizing release and verification workflows.

Visual Summary

flowchart TD
    request[change request] --> classify[classify risk and ownership]
    classify --> implement[implement in owning module]
    implement --> verify[verify with suites]
    verify --> publish[document and publish]

Change Control Rules

• classify changes by affected command family and policy impact
• keep command behavior and docs updated together
• require explicit evidence for compatibility-sensitive changes
• track temporary exceptions with expiry and owner

Review Checklist

• owning module is clear
• tests cover affected pathways
• docs and links updated
• risk notes updated when needed

Code Anchors

• crates/bijux-dev/src/commands/mod.rs
• crates/bijux-dev/src/suites/mod.rs
• crates/bijux-dev/src/policy/mod.rs

Next Reads

• Contract Governance
• Dependency Governance
• Core Change Management