Skip to content

Package Surface

bijux-dev-atlas is the Rust control-plane package that owns repository automation, docs governance, reports, and enforcement.

Package Surface Model

flowchart TD
    Package[Package surface] --> Identity[Public package identity]
    Package --> Binary[Binary or command surface]
    Package --> Docs[Docs and contract surface]
    Package --> Generated[Generated surface]
    Package --> Internal[Internal-only implementation]

    Identity --> Stable[What other parts of the repo may rely on]
    Binary --> Stable
    Docs --> Stable
    Generated --> Stable
    Internal --> Unstable[Not part of stable surface]

This page exists so maintainers do not flatten everything inside bijux-dev-atlas into one support promise. Some parts of the crate are relied on by docs, workflows, and other maintainers; other parts are free to evolve as implementation detail.

Stable Surface Expectations

  • the binary identity bijux-dev-atlas
  • the documented bijux dev atlas maintainer namespace it backs
  • the governed command families recorded in the command-surface registry
  • the generated reports and docs references that other workflows consume

Internal Surface Expectations

  • internal routing details
  • command handler structure
  • private modules and refactors that do not change documented command behavior, report shape, or evidence paths

Those internals still deserve care, but they are not automatically part of the stable maintainer contract unless another authoritative page promotes them into that role.

Repository Anchors

Main Takeaway

The bijux-dev-atlas package is not just another crate in the workspace. It is the maintainer control-plane package, which means its stable binary, docs, reports, and command behavior carry a repository-wide support burden that ordinary internal refactors do not.