Skip to content

Repository Gates

Repository gates ensure CLI, DAG, docs, and maintainer changes are verified with shared entrypoints before merge.

Visual Summary

flowchart TD
    change[proposed change] --> local[local gate run]
    local --> ci[ci gate run]
    ci --> review[review evidence]
    review --> merge[merge decision]

Gate Layers

  • workspace build and test gates
  • program-level contract gates for CLI and DAG
  • docs structure, link, and build gates
  • maintainer suite gates for ownership and policy contracts

Canonical Commands

make test
make dag-test
make docs-check
cargo run -q -p bijux-dev --bin bijux-dev-cli -- quickcheck --format json --no-pretty

Gate Failure Triage

When a gate fails, classify first before retrying:

  1. layout/docs failure
  2. contract/schema failure
  3. runtime/test failure
  4. automation/workflow failure

Classification controls which maintainer commands and handbook pages to use next.

Code Anchors

  • makes/rust.mk
  • makes/dag.mk
  • makes/docs.mk
  • crates/bijux-dev/src/suites/

Next Reads