openregs index

Work with cross-regime index combinations.

Index combinations pin a set of regime releases that were validated together. Regimes release independently, so two separately valid releases are not automatically a consistent pair; a combination is what makes ‘these go together’ a claim somebody can check.

openregs index [-h] <command> ...

openregs index verify

Check that a combination’s pinned releases exist and are in its schema range.

Verify one combination file: it is schema-valid and named after its own file, every release it pins exists, and every release’s declared schema_version falls inside the combination’s spec_schema_range. The eval suite is not re-run and artifact digests are not checked - a release answers for its own bytes, a combination answers for the set.

openregs index verify [-h] [--root <path>] <combination>

Argument
<combination>	the combination file, for example index/combinations/fixture-set.yaml (required)

Option
--root <path>	resolve pinned releases under this directory instead of the checkout