Skip to content

Release 0.50.24

Choose a tag to compare

@github-actions github-actions released this 05 Nov 12:02
· 4 commits to main since this release

Install

Docker

docker pull ghcr.io/jedwards1230/earmark:0.50.24

Helm

helm install earmark oci://ghcr.io/jedwards1230/charts/earmark --version 0.50.24

Summary

v0.50.24 is a patch release that adds the audio-vote rung to earmark decide. The rung decides held findings from second-ASR pilot votes without calling a model. The release also adds a database migration (19) and Helm chart support for the new configuration.

Features

Audio-vote rung: earmark decide --audio-vote

The new rung uses votes from second-ASR pilot models (produced by earmark asr-pilot vote) to decide findings that are currently held. When every configured pilot model hears the proposed replacement, the finding can be accepted. When every model hears the original text, the finding is rejected. Anything else stays held.

Configuration. Set an audio_vote block in MODELS_FILE with a rule and at least two {model_id, revision} models. For a single run, pass --audio-rule with two or more --audio-model <model_id>@<revision> flags. The flags replace the file block and must be given together. If neither is set, the command exits before connecting to the database.

Usage:

earmark decide --audio-vote [--book X]                          # dry run: writes nothing
earmark decide --audio-vote --yes --limit 2000 --max-accepts 500
earmark decide revert --recipe <audio recipe id>                # undo the rung's decisions
  • A dry run writes nothing, including no recipe row. It previews what --yes would write and accepts --sample, --seed, --json, --limit, --shard, and --max-accepts.
  • --yes writes only applies and rejects, recorded under a separate recipe. Holds are never written, so the should_apply recipe's work list is unchanged.
  • Each written decision stores the votes it relied on in finding_events.detail. The audit tool does not serve this column, so read it with SQL.
  • --audio-vote cannot be combined with --calibrate, --rung0-only, --dump, --human, --endpoint, --model, --policy, or --concurrency.

Suggested rollout: run the dry run first, then a bounded --yes run, spot-check the results in finding_events, and use earmark decide revert if needed.

Improvements

  • Database migration 19 adds a nullable finding_events.detail JSONB column. It has no default and requires no backfill. Commands migrate on connect, so this runs automatically the first time a v0.50.24 binary connects.
  • Helm chart: config.models.audio_vote is validated by values.schema.json. A block with no rule or fewer than two models is rejected. The chart does not enable the block by default. values.yaml includes a commented example with the deployment's pilot pins.

Commits

  • chore(earmark): bump chart version to 0.50.24 (02fd905)
  • feat(decide): audio-vote rung (decide --audio-vote) (#225) (4ae7b3f)

Full Changelog: v0.50.23...v0.50.24