Dashboard › institutional-transition-lab › Distillation
ce3b2612-e99b-4419-bb3d-0958bf811eb2["lore_tm_v1_3Gl0CAiT4QlM1MgZGSHgHR204dxp7DEZ8ctKuXLAnao"]
Date: Sep 9, 2026
/tmp/opencode/adjudication-records-final.json, containing 10 records across 827 lines; all records were reviewed by opencode-gpt-5.6-sol-primary.terraform-github-issue-35563 rejects the issue Terraform crashes on Azure Container Apps as no_event with confidence 0.99: it reports a platform-specific technical crash but establishes no governance, authority, rights, or institutional-rule change; graph_edge_revision uses luna_a with no added or removed edges.terraform-github-pr-21175 accepts luna_a: the merged Terraform provider-development guide added an MPL-2.0 requirement for all Terraform providers, coded as an effective_institutional_change and license event titled MPL-2.0 licensing requirement added for Terraform providers, with affected scope Terraform providers, announcement 2019-05-01, effective date 2019-05-02, confidence 0.94, and a power change adding Terraform’s license authority over all Terraform providers within Terraform provider development; evidence does not independently establish enforcement beyond the guide. (meaning May 1–2, 2019)terraform-github-pr-21345 revises the frozen response because the implementation belongs to Terraform rather than Chef Software and the publication-date announcement was omitted: it is coded as an effective_institutional_change and license event titled Terraform Habitat provisioner requires EULA acceptance, announced 2019-05-17, effective 2019-08-05, confidence 0.97, affecting Terraform Habitat provisioner installations. The effective added edge gives actor Terraform the set_terms right over Terraform Habitat provisioner installations for Habitat versions newer than 0.79.0 or latest; the terra_advisory-based graph revision removes the prior edge assigning actor Chef Software a modified license right. (meaning May 17–August 5, 2019)terraform-github-pr-21345 is explicitly ambiguous because its source announces a broader Chef EULA requirement while the supplied implementation establishes enforcement only for Terraform Habitat provisioner installations.terraform-github-pr-22332 revises luna_b: the merged revert removed the required accept_license field, validation, acceptance command, and documentation, effectively reversing Terraform’s provisioner terms. It is coded as an effective_institutional_change and license event titled Revert Terraform Habitat provisioner license-acceptance requirement, announced and effective 2019-08-05, confidence 0.99, with actor Terraform losing the set_terms right over Habitat versions newer than 0.79.0 or latest installed through the Terraform Habitat provisioner. (meaning August 5, 2019)terraform-github-pr-22745 revises terra_advisory because the frozen response incorrectly models users as the authority: it is coded as an effective_institutional_change and license event titled Terraform Habitat provisioner reinstates EULA acceptance requirement, announced and effective 2019-09-09, confidence 0.98, affecting Terraform Habitat provisioner installations. The revised graph adds actor Terraform with an effective set_terms right over Habitat versions newer than 0.79.0 or latest installed through the provisioner and removes the prior edge assigning actor users a modified license right. (meaning September 9, 2019)terraform-github-pr-22745 is explicitly ambiguous because it states Chef Software’s broader EULA requirement but establishes only Terraform provisioner enforcement, not the effective date of the underlying EULA change.terraform-github-pr-33661 accepts luna_b: Terraform’s LICENSE replacement changed the Terraform Licensed Work from MPL 2.0 to Business Source License 1.1. It is coded as an effective_institutional_change and license event titled Terraform license changed from MPL 2.0 to Business Source License 1.1, announced and effective 2023-08-10, confidence 0.98, with actor HashiCorp, Inc. modifying license rights targeting you; the BSL specifies Change License: MPL 2.0. Evidence is bounded because the complete listing has 1,294 changed files while the frozen selection has only 20 patches, though the complete LICENSE replacement directly establishes the change. (meaning August 10, 2023)terraform-github-pr-34096 rejects the merged HCL v2.19.0 update as a non-institutional control_event, event kind product, titled Update HCL to v2.19.0, announced 2023-10-16, effective 2023-10-17, confidence 0.99, with no power changes; no implementing patch was supplied, so file-level details are unverified. graph_edge_revision uses luna_b with no added or removed edges. (meaning October 16–17, 2023)terraform-github-pr-34103 rejects the Terraform v1.6 backport of HCL v2.19.0 as a product-maintenance control_event, titled Backport HCL v2.19.0 into v1.6, announced and effective 2023-10-17, confidence 0.87, with no power changes. Its body_patch_relation is body_only; no implementing patch was supplied, so merged metadata supports completion but not detailed contents. graph_edge_revision uses terra_advisory with no added or removed edges. (meaning October 17, 2023)terraform-github-pr-34847 accepts luna_b: Terraform took responsibility from go-getter for interpreting historical module-source shorthand addresses while go-getter retained responsibility for actual module installation. It is coded as an effective_institutional_change, event kind control_rights, titled Terraform takes control of module source address normalization, announced and effective 2024-03-14, confidence 0.96. Effective set_policy authority over historical shorthand interpretation is removed from go-getter and added to Terraform; the complete listing has 86 changed files while the frozen selection has 16 patches, so no claim covers every changed file. (meaning March 14, 2024)terraform-github-pr-38385 accepts terra_advisory: the closed, unmerged PR is coded as proposal_only, event kind control_rights, titled Add AI agent governance, announced 2026-04-15, with no effective date and confidence 0.82. It proposes actor terraform adding a delegate right for autonomous post-gate commits to AI coding tools (Claude Code, Cursor, Copilot, Codex, Gemini) but establishes neither implementation nor adoption; graph_edge_revision has no added or removed edges. (meaning April 15, 2026)