Skip to content

Automation

bijux-atlas-dev/automation is the section home for this handbook slice.

flowchart TD
    Automation[Automation section] --> Entry[Command entrypoints]
    Automation --> Routing[Command routing]
    Automation --> Generate[Generation and references]
    Automation --> Reports[Reports and evidence]
    Automation --> Extensions[Safe surface changes]
    Entry --> Model[Maintainer execution model]
    Routing --> Model
    Generate --> Model
    Reports --> Model
    Extensions --> Model

Automation here means the governed execution surface of the repository. That includes bijux dev atlas, the direct bijux-dev-atlas binary, thin make wrappers, and the report or evidence families those entrypoints produce.

Control Model

  • bijux dev atlas is the canonical human-facing control-plane surface
  • bijux-dev-atlas is the direct binary surface beneath it
  • make remains a thin convenience wrapper, not the ultimate authority
  • configs, registries, and generated outputs determine whether the automation is behaving correctly

Page Roles

  • concept and control pages: command routing, automation control plane
  • extension workflow pages: adding CLI, HTTP, or contract surfaces
  • evidence and execution reference pages: reports, generated references, subprocess policy, tutorial runs

Pages