bijux-canon-dev

bijux-canon-dev is the maintainer package for repository health. It keeps schema drift checks, release guards, supply-chain helpers, docs publication contracts, and repository-wide validation logic in one place outside the end-user product surface.

That boundary matters. Hidden maintainer policy weakens trust quickly, so the package should make repository rules inspectable in helper modules, tests, and explicit integration points.

Package Model

flowchart LR
    helpers["helper modules"]
    gates["quality, security, schema, release gates"]
    tests["maintainer tests"]
    integration["make, workflows, apis"]
    repo["repository health"]

    helpers --> gates --> integration --> repo
    tests --> gates

This page should make bijux-canon-dev feel like a real package with a clear operating role, not just a bin for repository glue. Helper modules define the rules, tests prove them, and checked-in integration points show where those rules actually get enforced.

Package Pages

• Package Overview
• Scope and Non-Goals
• Module Map
• Quality Gates
• Security Gates
• Schema Governance
• Release Support
• SBOM and Supply Chain
• Operating Guidelines

Start With

• Open Package Overview for the shortest statement of what the maintainer package owns.
• Open Module Map when you need the code layout first.
• Open Quality Gates, Security Gates, or Schema Governance when the question is an enforcement rule.
• Open Release Support or SBOM and Supply Chain when the concern is publication or provenance.

Module Roots

• src/bijux_canon_dev/api for schema drift and API freeze helpers
• src/bijux_canon_dev/quality for repository quality checks
• src/bijux_canon_dev/security for audit gates
• src/bijux_canon_dev/release for publication guards and version resolution
• src/bijux_canon_dev/sbom for requirements and SBOM support
• src/bijux_canon_dev/docs for docs publication and badge support

Proof Path

• packages/bijux-canon-dev/src/bijux_canon_dev carries the helper code.
• packages/bijux-canon-dev/tests carries the executable proof.
• apis/, Makefile, and .github/workflows/ show where the helpers are consumed.

Boundary

bijux-canon-dev owns maintainer automation, not product behavior. If a change would alter user-facing ingest, index, reason, agent, or runtime semantics, this section should stop at the integration seam and hand the explanation back to the owning package handbook.

Design Pressure

If repository policy can only be found in workflow logs or shell fragments, the maintainer package is still too hidden. This section has to keep helper code, proof, and integration points visibly tied together.