Ahnii!

A strict digest check is supposed to stop old configuration from silently selecting changed generated output. When a reviewed generator changes, that protection can also make a reference fixture fail until its pinned identity is migrated.

This post shows how to repair that failure without weakening the integrity check, using a Waaseyaa reference consumer as the example.

Understand what the digest protects

The reference application selects a generated recipe in YAML:

recipes : - id : published_content version : 1 capability : published_content artifact_digest : cf8f1932dea7f7dc08ccf2cefbf42465d5c2838b1d0e1fbd3cf62a63da580f11

Enter fullscreen mode

Exit fullscreen mode

The digest identifies the reviewed recipe artifact, not just the recipe name and version. If the recipe's generated files or contract change, an older selection should not claim that it still describes the installed output.

That refusal is useful.…