Skip to content

bijux-atlas-dev

bijux-atlas-dev is the maintainer control-plane handbook.

flowchart TD
    Dev[Maintainer handbook] --> Workspace[Workspace]
    Dev --> Automation[Automation]
    Dev --> Governance[Governance]
    Dev --> Delivery[Delivery]
    Dev --> Ownership[Workflow ownership]
    Workspace --> Control[Repository control model]
    Automation --> Control
    Governance --> Control
    Delivery --> Control
    Ownership --> Control

This handbook should let a maintainer move from a repository question to the owning rule, command, or workflow without guesswork. Its job is to explain how the repository is governed as a control plane: which tools initiate change, which rules constrain it, which evidence closes it, and who owns the call.

Scope

Use this handbook for workspace ownership, automation surfaces, governance, delivery lanes, and workflow ownership.

Maintainer Authority Map

  • workspace structure and contributor-facing repository law: docs/bijux-atlas-dev/workspace/*
  • automation behavior and direct control-plane implementation: crates/bijux-atlas-dev/ and make wrappers in makes/
  • governance rules and policy sources: configs/sources/governance/
  • delivery behavior and publication lanes: .github/workflows/, release configs, and related release metadata
  • review routing and template-driven workflow ownership: .github/CODEOWNERS, .github/PULL_REQUEST_TEMPLATE*, and .github/ISSUE_TEMPLATE/

Main Takeaway

bijux-atlas-dev is not background reading. It is the maintained description of how Atlas is changed safely. A good maintainer page should answer four questions quickly: who owns this, what rule applies, what starts it, and what evidence closes it.

Sections