Module compatibility 

The compatibility axes beyond the payload schema, each evaluated into a precondition with a requirement.

The seam settles engine-against-payload through payload_schema. Four axes remain, and each one has stranded someone: the engine floor a bundle names where the schema is too coarse, the generator a committed artifact needs at its pin, the manager a pin move would go through, and the forge floor the landed files rest on, plus the intermediate release a landing must pass through. The facts land in the plan’s release.compatibility section; the policy lands in the preconditions.

Structs

Evaluated

What the evaluation produces.

Inputs

Everything the evaluation reads.

Constants

PIN_MANAGER_DECISION

The decision id for a pin move through a manager the target does not wire.

Functions

evaluate

Evaluate every axis.

generator_for

The generator a technology’s committed artifact needs, as versions.toml names it, and the artifact it regenerates.