Pin a reproducible decision with lockfiles

Freeze the catalog release and deployment IDs behind an approved decision, then verify whether the assumptions still hold later.

Why pin a decision

“We chose model X” is not reproducible. A useful decision record must identify the exact deployments, the catalog release used to evaluate them, and a content digest that proves the record was not changed.

Create the lockfile

1. Complete the registry, cost, and policy review first.
2. Select the project that owns the decision.
3. Enter one or more deployment public IDs separated by commas.
4. Select Create lockfile. ALLM adds the current catalog release and stores a canonical SHA-256 digest.

{
  "catalog_release_id": "cat_2026_07_22_01",
  "deployment_ids": [
    "dep_openai_gpt_5_1_responses_global",
    "dep_anthropic_claude_sonnet_4_5_messages_global"
  ]
}

Store the evidence

Select Download and commit the JSON file beside the service or configuration it governs. Record the lockfile ID, content digest, policy version, approver, and business context in the pull request or change record.

Verify after drift

1. Return to Lockfiles after a catalog release or before a production release.
2. Select Verify on the saved record.
3. Review the Latest result. If invalid, inspect release drift and missing deployment IDs before approving a new lockfile.

{
  "valid": false,
  "actual_sha256": "6f2e…a104",
  "expected_sha256": "6f2e…a104",
  "locked_catalog_release_id": "cat_2026_07_22_01",
  "current_catalog_release_id": "cat_2026_08_03_01",
  "release_changed": true,
  "missing_deployment_ids": []
}

Interpret verification