makes

The makes/ tree is the shared command interface for repository operations. It turns recurring work into named, checked-in entrypoints instead of leaving maintainers to reconstruct procedure from workflow YAML or shell history.

A good make surface is traceable. A maintainer should be able to start from a root command, find the owning fragment quickly, and see whether the rule is repository scope, package scope, CI scope, or release scope.

Command Model

flowchart LR
    root["root make target"]
    fragments["make fragments"]
    package["package or ci dispatch"]
    helpers["helper code and scripts"]
    result["operational result"]

    root --> fragments --> package --> helpers --> result

The makes/ tree is useful only when a maintainer can follow a command from the root entrypoint into the fragment that owns it and then into the helper or package surface that actually does the work. This page should make that route easy to picture before anyone starts chasing includes.

Section Pages

• Make System Overview
• Root Entrypoints
• Environment Model
• Repository Layout
• Package Dispatch
• CI Targets
• Package Contracts
• Release Surfaces
• Authoring Rules

Start With

• Open Make System Overview for the layered shape of the command tree.
• Open Root Entrypoints when the question begins at Makefile.
• Open Package Dispatch when a shared target routes into one package or many.
• Open CI Targets or Release Surfaces when the concern is automation-facing.

Proof Path

• Makefile is the top-level entrypoint.
• makes/root.mk, makes/env.mk, and makes/packages.mk assemble the shared tree.
• makes/bijux-py/ and makes/packages/ show the reusable and package-bound parts of the command surface.

Boundary

The make layer documents command routing and shared operational rules. It should not become a second product handbook. If understanding a target requires a deep product explanation, the product package docs still own that explanation.

Design Pressure

If command ownership is hidden behind too many includes or naming shortcuts, the shared interface stops being reviewable. This section has to keep entry targets, fragments, and delegated work visibly aligned.