Distillation

Date: Sep 8, 2026

• 🟡 (20:20) Assistant reported the likely adjudication outcomes had narrowed to 4 accepts, 3 revisions, and 3 source-level rejections; exact frozen objects and quote substrings for the first 5 records were still being checked because any changed confidence, date, or evidence reference would invalidate an accept.
• 🔴 (20:20) terraform-github-pr-33661 changed Terraform’s license from Mozilla Public License 2.0 (MPL-2.0) to Business Source License 1.1 (BUSL-1.1) across 1,294 changed files; metadata shows merged commit 1f011cbaada5bf9cbddadb58ba7c84b223e99467, with patch selection truncated but no unavailable patches or truncated source text. (meaning Aug 10, 2023)
• 🔴 (20:20) terraform-github-pr-33661 identifies HashiCorp, Inc. as licensor; permits production use except offering the licensed work to third parties on a hosted or embedded basis competitive with HashiCorp products; sets the Change Date to 4 years after publication and the Change License to MPL 2.0; noncompliant use requires purchasing a commercial license or refraining from use. (meaning Aug 10, 2023)
• 🔴 (20:20) terraform-github-pr-34096 updated HCL to v2.19.0 in 2 changed files. Enhancement: ext/dynblock’s dynblock.Expand gained an optional hook allowing callers to veto particular for_each values by returning error diagnostics, with unchanged behavior when unset. Fix: hclsyntax further corrected marked-value handling and refined-value tracking in conditional expressions, building on v2.18.1; it fixes issue #34060 and merged as 493056d828ab0cd17def8e0193f71f4bfe8f9628. (meaning Oct 17, 2023)
• 🔴 (20:20) terraform-github-pr-34103 backported the HCL v2.19.0 update from #34096 into Terraform v1.6 because of label 1.6-backport; it included commit 1f271185986bcb30eb3e19fcae4457b122f43147 and merged as 0c855b0d5e6fe2a9578106f47438fffc4eba3d0e. (meaning Oct 17, 2023)
• 🔴 (20:21) terraform-github-issue-35563, “Terraform crashes on Azure Container Apps,” had a model disagreement: luna_a and terra_advisory classified it as no_event with confidence 0.99, while luna_b classified it as a product control_event affecting Terraform versions below 0.15.0 during backend initialization, also with confidence 0.99.
• 🔴 (20:21) terraform-github-pr-21175 added the development-guide requirement: “All Terraform providers are required to contain a MPL-2.0 open source license.” All 3 model outputs classified it as an effective institutional license change, announced May 1, 2019 and effective May 2, 2019; terra_advisory noted the evidence established the merged guide requirement but not enforcement beyond the guide. (meaning May 2, 2019)
• 🔴 (20:21) Going forward, Habitat installation requires users to accept the Chef EULA; the exact source wording in terraform-github-pr-21345 was “Going forward Habitat installation will require users to accept Chef EULA.” The Terraform Habitat provisioner implemented required accept_license (bool) set to true; terra_advisory bounded the demonstrated enforcement to Terraform Habitat provisioner installations rather than every Habitat installation method. (meaning Aug 5, 2019)
• 🔴 (20:21) terraform-github-pr-21345 announced the Habitat/Chef EULA requirement on May 17, 2019 and merged it on August 5, 2019 at 2019-08-05T16:40:34Z; luna_a and terra_advisory classified it as an effective_institutional_change, while luna_b classified it as a control_event. (meaning Aug 5, 2019)
• 🔴 (20:21) terraform-github-pr-22332 reverted the Habitat license-acceptance changes, removing the accept_license schema and license-acceptance installation behavior from the Terraform Habitat provisioner; the patch also removed Chef license documentation, although luna_a noted no corresponding Chef implementation patch was shown. luna_a’s output was schema-invalid because 2 evidence references were not grounded, while luna_b and terra_advisory returned schema-valid control_event classifications. (meaning Aug 5, 2019)
• 🔴 (20:21) terraform-github-pr-22745 subsequently reinstated the requirement: “Going forward Habitat installation will require users to accept Chef EULA.” Terraform enforcement requires setting accept_license to true, with the error text “Habitat end user license agreement needs to be accepted, set the accept_license argument to true to accept”; the PR merged at 2019-09-09T19:40:20Z. (meaning Sep 9, 2019)
• 🔴 (20:21) For terraform-github-pr-22745, luna_a classified the Chef EULA requirement as an effective_institutional_change with confidence 0.97; terra_advisory did likewise with confidence 0.95, while noting the record proves merged Terraform enforcement but not the effective date of Chef Software’s underlying EULA change. luna_b was schema-invalid due to invalid JSON: Extra data: line 1 column 680 (char 679). (meaning Sep 9, 2019)