Dashboard › institutional-transition-lab › Distillation
1ee0d3d9-b9c5-4b53-836b-edefadf822bf["lore_tm_v1_6aBj0d6hl4A8Y8Rkzv3ZRRmtBMP4TYMFj9892AbGYFw"]
Date: Sep 8, 2026
effective_institutional_change, event_kind=board_or_steering, announced_on=2025-05-20, and effective_on=2025-05-23; luna_a encoded added TSC rights to set_strategy over technical oversight/direction, approve Contributors becoming Committers, remove Committers, and elect a TSC Chair, plus an added LF Projects own right over Project Trademarks; luna_b encoded TSC rights to approve, remove, appoint representatives, delegate authority to project maintainers, and override those maintainers’ decisions; terra_advisory encoded TSC approve, remove, and override rights. Confidence was respectively 0.96, 0.96, and 0.89; body_patch_relation was respectively patch_supersedes_body, patch_supersedes_body, and consistent.opentofu-github-pr-2953, concerning relocation of governance documents and TSC notes to opentofu/org: luna_a used event_kind=reorganization, announced_on=2025-06-24, effective_on=2025-06-25, body_patch_relation=consistent, confidence 0.70; luna_b used the same dates, kind, and relation, confidence 0.58; terra_advisory used null dates/event kind, body_patch_relation=unclear, confidence 0.42. All had no power changes and warned that the 43-file patch selection was truncated or did not establish an organizational-rights change.opentofu-github-pr-2959, a merged CODEOWNERS update for a new governance team: luna_a scoped CODEOWNERS, event_kind=control_rights, announced_on=2025-06-25, body_patch_relation=unclear, confidence 0.72; luna_b scoped CODEOWNERS and the opentofu-maintainers team, with the same kind/date/relation and confidence 0.86; terra_advisory scoped CODEOWNERS, with the same kind/date/relation and confidence 0.45. All omitted an effective date and power changes because no implementing patch was supplied.opentofu-github-pr-3473: both classified the Databricks state-backend-with-locking RFC as a control_event, event_kind=product, announced 2025-11-05, with no effective date or power changes; luna_a confidence was 0.97, luna_b confidence was 0.98, and terra_advisory=null.opentofu-github-pr-3559: luna_a classified the RELEASE.md support-policy update as no_event, null event kind/dates, body_patch_relation=unclear, confidence 0.70; luna_b classified it as a control_event, event_kind=product, effective 2025-12-09, confidence 0.78; terra_advisory also classified it as a product control_event, announced 2025-12-09, no effective date, body_patch_relation=body_only, confidence 0.68. All had no power changes and noted that policy terms or implementing patches were unavailable.opentofu-github-pr-4018: luna_a and luna_b classified merged official-build detection associated with a forthcoming 32-bit-support warning as a product control_event, announced 2026-04-09, effective 2026-08-11, with confidence 0.90 and 0.84; both noted that the supplied patch showed official-build detection but not the warning implementation. terra_advisory classified the contemplated end of official 32-bit release support as proposal_only, event_kind=control_rights, announced 2026-04-09, no effective date, confidence 0.84, encoding a proposed removal of OpenTofu’s release right for official packages targeting 32-bit CPU architectures.terra_advisory evidence for opentofu-github-pr-4018: “ending official support for 32-bit CPU architectures” and “The maintainers have not discussed this yet, and so we might decide to do something quite different in the end.”opentofu-github-pr-727: luna_a and luna_b classified addition of # SPDX-License-Identifier: MPL-2.0 to compare-release-versions.sh as an effective_institutional_change, event_kind=license, announced 2023-10-14, effective 2023-10-15, confidence 0.98, with an added OpenTofu license right; terra_advisory classified the same edit to .github/scripts/compare-release-versions.sh as no_event, null dates/event kind, confidence 0.99.opentofu-github-pr-823, recording TSC selection of a provider/module registry RFC and core-team priorities without power changes: luna_a announced it on 2023-11-05, confidence 0.94; luna_b announced it on 2023-11-02, confidence 0.95; both used body_patch_relation=patch_only, event_kind=strategy; terra_advisory used body_patch_relation=consistent, confidence 0.90, and noted the strategy decision did not demonstrate a change in organizational authority.control_event codings for opentofu-github-pr-990, the 2023-12-05 TSC summary: luna_a scoped TSC decisions on registry namespace, RFCs, issues, and PRs as event_kind=strategy; luna_b and terra_advisory scoped the unanimous decision to change the default registry namespace to opentofu as event_kind=product. All used announced_on=2023-12-10, body_patch_relation=consistent, no effective date or power changes, with confidence 0.94, 0.88, and 0.91; the latter two noted that documentation recorded the decision but did not show implementation.terraform-github-issue-22468 were no_event, with null scope, dates, event kind, and power changes, body_patch_relation=not_applicable; luna_a confidence was 0.96, luna_b confidence was 0.98, and terra_advisory=null.terraform-github-issue-34139: luna_a classified an Azure access-package-assignment authorization error as a product control_event, scope Terraform Azure access package assignment policy deployment, confidence 0.98; luna_b and terra_advisory classified it as no_event, confidence 0.99. All had null dates, no power changes, and body_patch_relation=not_applicable.terraform-github-issue-35563: luna_a and terra_advisory classified Terraform crashes on Azure Container Apps with versions below 0.15.0 as no_event, confidence 0.99; luna_b classified the backend-initialization crash as a product control_event, scoped to Terraform versions below 0.15.0 on Azure Container Apps, confidence 0.99. All used null dates, no power changes, and body_patch_relation=not_applicable.terraform-github-pr-21175: all three classified the merged development-guide requirement “All Terraform providers are required to contain a MPL-2.0 open source license.” as an effective_institutional_change, event_kind=license, announced 2019-05-01, effective 2019-05-02, with an added license requirement/right targeting all Terraform providers. luna_a, luna_b, and terra_advisory confidence values were 0.94, 0.96, and 0.72; terra_advisory cautioned that the guide did not independently establish enforcement.terraform-github-pr-21345 codings for the initial Chef EULA requirement: luna_a classified it as an effective_institutional_change, announced 2019-05-17, effective 2019-08-05, confidence 0.96, with an added Chef Software license right over Habitat installation; luna_b classified it as a license control_event with the same dates and confidence 0.98; terra_advisory classified it as an effective_institutional_change, effective 2019-08-05, confidence 0.93, with Chef Software’s license right modified for Terraform Habitat provisioner installations.terraform-github-pr-21345: “Going forward Habitat installation will require users to accept [Chef EULA]”; “Going forward Habitat installation will require users to accept Chef EULA.”; // Accept the license; and * accept_license (bool) - (Required) Set to true to accept [Habitat end user license agreement](https://www.chef.io/end-user-license-agreement/). The PR metadata evidence stated "merged": true, "merged_at": "2019-08-05T16:40:34Z".terraform-github-pr-22332 reverted the Habitat license-acceptance requirement on 2019-08-05: luna_a classified this as an effective_institutional_change, event_kind=license, announced/effective 2019-08-05, confidence 0.98, removing the accept_license schema, validation, and installation behavior; luna_b and terra_advisory classified the revert as a license control_event, effective 2019-08-05, confidence 0.96 and 0.98, with no power changes. Evidence included Revert "Habitat License Acceptance changes. ", -\t\t\t"accept_license": &schema.Schema{, and -\t// Accept the license.terraform-github-pr-22745 subsequently restored the Chef EULA acceptance requirement for Habitat installation through Terraform on 2019-09-09, replacing the same-day August revert: luna_a classified it as an effective_institutional_change, event_kind=license, effective 2019-09-09, confidence 0.97, adding Chef Software’s license right with users as target; terra_advisory likewise classified it as effective, announced/effective 2019-09-09, confidence 0.95, encoding users’ license obligation as modified; luna_b=null.terraform-github-pr-22745: “Going forward Habitat installation will require users to accept Chef EULA.”; * accept_license (bool) - (Required) Set to true to accept [Habitat end user license agreement](https://www.chef.io/end-user-license-agreement/); “Habitat end user license agreement needs to be accepted, set the accept_license argument to true to accept”; and "merged_at": "2019-09-09T19:40:20Z".terraform-github-pr-33661: Terraform’s license changed from MPL 2.0 to Business Source License 1.1 as an effective_institutional_change, event_kind=license, announced/effective 2023-08-10, with HashiCorp, Inc. modifying license rights over the Terraform Licensed Work. Confidence was 0.99 for luna_a, 0.98 for luna_b, and 0.94 for terra_advisory; all used body_patch_relation=consistent.terraform-github-pr-33661: licensor HashiCorp, Inc.; users may copy, modify, create derivative works, redistribute, and make non-production use; production use is permitted by the Additional Use Grant only if it does not offer the Licensed Work to third parties on a hosted or embedded basis competitive with HashiCorp products; the Change License is MPL 2.0, after which rights under the Change License apply and the preceding rights terminate. Merge evidence was "merged": true, "merged_at": "2023-08-10T22:58:09Z".terraform-github-pr-34096: luna_a and luna_b classified the HCL dependency update to v2.19.0 as a product control_event, announced 2023-10-16, effective 2023-10-17, body_patch_relation=not_applicable, no power changes, with confidence 0.98 and 0.99; terra_advisory=null.control_event codings for terraform-github-pr-34103, backporting HCL v2.19.0 into Terraform v1.6: all announced it on 2023-10-17 and encoded no power changes; luna_a used effective date 2023-10-17, body_patch_relation=not_applicable, confidence 0.99; luna_b omitted the effective date, used not_applicable, confidence 0.98; terra_advisory used effective date 2023-10-17, body_patch_relation=body_only, confidence 0.87, noting that no implementing patch was supplied.terraform-github-pr-34847: luna_a and luna_b classified Terraform taking control of historical module-source-address shorthand interpretation from go-getter as an effective_institutional_change, event_kind=control_rights, announced/effective 2024-03-14, confidence 0.98 and 0.96; both encoded removal of go-getter’s stewardship/policy right and addition of Terraform’s corresponding right, while noting go-getter remained responsible for actual module installation. terra_advisory classified the merged source-address normalization and dependency-pruning refactor as a product control_event with no power changes, confidence 0.90.terraform-github-pr-34847: “Terraform is now the one responsible for handling the small number of historical special "shorthands"”; “Terraform was historically delegating the entire problem to go-getter”; “Terraform historically accepted as shorthands for module source addresses”; and “We don't use go-getter's own detectors because Terraform needs to be in control of its own source address syntax”.terraform-github-pr-38385: all classified proposed AI-agent governance configuration as proposal_only, event_kind=control_rights, announced 2026-04-15, no effective date, body_patch_relation=consistent; luna_a and luna_b encoded a proposed Terraform set_policy right governing AI coding tools—Claude Code, Cursor, Copilot, Codex, and Gemini—with confidence 0.98; terra_advisory encoded a proposed delegate right allowing those tools to auto-commit after quality gates pass, confidence 0.82. Evidence included “This PR adds governance configs generated from your existing CI pipeline — no manual authoring needed.”, # Governance — terraform, ## Autonomy, - Auto-commit after gates pass, and "merged": false.